https://wiki.massivecraft.com/index.php?title=Staff:Codex&feed=atom&action=historyStaff:Codex - Revision history2024-03-19T01:56:44ZRevision history for this page on the wikiMediaWiki 1.38.1https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=37340&oldid=prevQgmk: /* Rule Two: Voice Communication and Centralization */2022-02-14T20:36:34Z<p><span dir="auto"><span class="autocomment">Rule Two: Voice Communication and Centralization</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 20:36, 14 February 2022</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l22">Line 22:</td>
<td colspan="2" class="diff-lineno">Line 22:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Staff is also afforded several social Discords where communication between Staff members is strongly encouraged. Even if a Staff member is not in the same department as another, they are still encouraged to communicate with one another to avoid silo-forming in our organization, and to encourage cross-department communication which is essential to providing better implemented services to all players. For example, Lore benefits from having the backup of Game staff during event hosting so they can focus on the actual lore, while Quest benefits from World staff members building their quest locations to the highest quality possible for the best experience possible. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Staff is also afforded several social Discords where communication between Staff members is strongly encouraged. Even if a Staff member is not in the same department as another, they are still encouraged to communicate with one another to avoid silo-forming in our organization, and to encourage cross-department communication which is essential to providing better implemented services to all players. For example, Lore benefits from having the backup of Game staff during event hosting so they can focus on the actual lore, while Quest benefits from World staff members building their quest locations to the highest quality possible for the best experience possible. </div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must be in possession of a microphone and be at least <del style="font-weight: bold; text-decoration: none;">16 </del>years old. No other verification of age is required beyond a provision of a birthday.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must be in possession of a microphone and be at least <ins style="font-weight: bold; text-decoration: none;">18 </ins>years old. No other verification of age is required beyond a provision of a birthday.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must be able to communicate over voice on a moment’s notice, unless special circumstances get in the way of this.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must be able to communicate over voice on a moment’s notice, unless special circumstances get in the way of this.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Voice Chat is always superior to written chat. If a dispute becomes heated or cannot be expressed properly in text chat, Staff members should request each other on Voice Chat so the outcome may be more positive.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Voice Chat is always superior to written chat. If a dispute becomes heated or cannot be expressed properly in text chat, Staff members should request each other on Voice Chat so the outcome may be more positive.</div></td></tr>
</table>Qgmkhttps://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=29865&oldid=prevCS Birb: Derpadillo - Now Direction 22021-01-03T21:28:56Z<p>Derpadillo - Now Direction 2</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:28, 3 January 2021</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l66">Line 66:</td>
<td colspan="2" class="diff-lineno">Line 66:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid-shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a "collection department" that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by LumosJared <del style="font-weight: bold; text-decoration: none;">and </del>CS_Birb in Direction Rank 2. <del style="font-weight: bold; text-decoration: none;">Derpadillo is Direction Rank 1 and </del>TheComputerGeek is a Direction Aspirant. Within Direction, MonMarty and LumosJared have HR training and are the contacts for any related services. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision-making powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to some of the actions of his teammates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid-shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a "collection department" that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by LumosJared<ins style="font-weight: bold; text-decoration: none;">, </ins>CS_Birb <ins style="font-weight: bold; text-decoration: none;">& Derpadillo </ins>in Direction Rank 2. TheComputerGeek is a Direction Aspirant. Within Direction, MonMarty and LumosJared have HR training and are the contacts for any related services. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision-making powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to some of the actions of his teammates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Aspirants, Rank1, Rank2, and Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher-ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. Efficiency is crucial in a Meritocracy.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Aspirants, Rank1, Rank2, and Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher-ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. Efficiency is crucial in a Meritocracy.</div></td></tr>
</table>CS Birbhttps://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=29166&oldid=prevJared4242: /* Rule Seven: Hierarchy and Direction */2020-10-20T19:56:49Z<p><span dir="auto"><span class="autocomment">Rule Seven: Hierarchy and Direction</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:56, 20 October 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l66">Line 66:</td>
<td colspan="2" class="diff-lineno">Line 66:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid-shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a "collection department" that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by LumosJared and CS_Birb in Direction Rank 2. Derpadillo <del style="font-weight: bold; text-decoration: none;">and TheComputerGeek2 are </del>Direction Rank 1. Within Direction, MonMarty and LumosJared have HR training and are the contacts for any related services. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision-making powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to some of the actions of his teammates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid-shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a "collection department" that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by LumosJared and CS_Birb in Direction Rank 2. Derpadillo <ins style="font-weight: bold; text-decoration: none;">is </ins>Direction Rank 1 <ins style="font-weight: bold; text-decoration: none;">and TheComputerGeek is a Direction Aspirant</ins>. Within Direction, MonMarty and LumosJared have HR training and are the contacts for any related services. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision-making powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to some of the actions of his teammates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Aspirants, Rank1, Rank2, and Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher-ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. Efficiency is crucial in a Meritocracy.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Aspirants, Rank1, Rank2, and Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher-ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. Efficiency is crucial in a Meritocracy.</div></td></tr>
</table>Jared4242https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=27719&oldid=prevJared4242: /* Rule Seven: Hierarchy and Direction */2020-07-24T20:26:40Z<p><span dir="auto"><span class="autocomment">Rule Seven: Hierarchy and Direction</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 20:26, 24 July 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l66">Line 66:</td>
<td colspan="2" class="diff-lineno">Line 66:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a "collection department" that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by LumosJared and CS_Birb in Direction Rank 2. <del style="font-weight: bold; text-decoration: none;">Delgadillo </del>and TheComputerGeek2 are Direction Rank 1. Within Direction, MonMarty and LumosJared have HR training and are the contacts for any related services. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision-<del style="font-weight: bold; text-decoration: none;">taking </del>powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to some of the actions of his teammates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid<ins style="font-weight: bold; text-decoration: none;">-</ins>shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a "collection department" that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by LumosJared and CS_Birb in Direction Rank 2. <ins style="font-weight: bold; text-decoration: none;">Derpadillo </ins>and TheComputerGeek2 are Direction Rank 1. Within Direction, MonMarty and LumosJared have HR training and are the contacts for any related services. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision-<ins style="font-weight: bold; text-decoration: none;">making </ins>powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to some of the actions of his teammates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Aspirants, Rank1, Rank2, and Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher-ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. Efficiency is crucial in a Meritocracy.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Aspirants, Rank1, Rank2, and Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher-ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. Efficiency is crucial in a Meritocracy.</div></td></tr>
</table>Jared4242https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=27718&oldid=prevJared4242 at 20:26, 24 July 20202020-07-24T20:26:08Z<p></p>
<a href="//wiki.massivecraft.com/index.php?title=Staff:Codex&diff=27718&oldid=23113">Show changes</a>Jared4242https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=23113&oldid=prevJared4242: /* Rule Eight: Anti-Corruption Minimalism */2019-06-04T03:12:25Z<p><span dir="auto"><span class="autocomment">Rule Eight: Anti-Corruption Minimalism</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 03:12, 4 June 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l89">Line 89:</td>
<td colspan="2" class="diff-lineno">Line 89:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff members are encouraged to search each other’s logs, even if they trust the individual. This does not mean every private conversation is no longer private, but occasional peeks are encouraged with keywords or commands.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff members are encouraged to search each other’s logs, even if they trust the individual. This does not mean every private conversation is no longer private, but occasional peeks are encouraged with keywords or commands.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must report suspicion of corruption violations to Direction. Additionally, Staff members must do everything within their capacity to halt or otherwise prevent another Staff member from engaging in corrupt behavior or undo any corrupt actions that a staff member has taken, by for example destroying spawned items.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must report suspicion of corruption violations to Direction. Additionally, Staff members must do everything within their capacity to halt or otherwise prevent another Staff member from engaging in corrupt behavior or undo any corrupt actions that a staff member has taken, by for example destroying spawned items.</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must feel trusted and safe in Staff-only channels. Therefore, leaking any information or personal statements from any Staff channel (including but not limited to <del style="font-weight: bold; text-decoration: none;">Skype</del>, Discord<del style="font-weight: bold; text-decoration: none;">, Teamspeak</del>, Server Channels, and Forums) is grounds for immediate dismissal from Staff.This includes screenshots, copy/pasting, and repetition of any information shared within official channels.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*Staff members must feel trusted and safe in Staff-only channels. Therefore, leaking any information or personal statements from any Staff channel (including but not limited to , Discord, Server Channels, and Forums) is grounds for immediate dismissal from Staff.This includes screenshots, copy/pasting, and repetition of any information shared within official channels.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff confidentiality also covers the private information of staff members and players, including but not limited to identities, protected status, IP addresses, emails, player reports, ban appeals and more. Furthermore, hidden threads on the forum must never have their information spread among players.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff confidentiality also covers the private information of staff members and players, including but not limited to identities, protected status, IP addresses, emails, player reports, ban appeals and more. Furthermore, hidden threads on the forum must never have their information spread among players.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*In-Development matters must never be discussed with players unless the green light was given specifically by a department leader or Director. If in doubt, staff members must ask their department leaders.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*In-Development matters must never be discussed with players unless the green light was given specifically by a department leader or Director. If in doubt, staff members must ask their department leaders.</div></td></tr>
</table>Jared4242https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=23112&oldid=prevJared4242 at 03:12, 4 June 20192019-06-04T03:12:00Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 03:12, 4 June 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l33">Line 33:</td>
<td colspan="2" class="diff-lineno">Line 33:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Furthermore, when Staff member witness something similar occuring in the direction of Staff members, the individual who in question is not present, they are required to encourage a positive dialogue. Players are certainly allowed to express their feelings about staff projects, but Staff should be aware to ensure this does not take a toxic charge. When a player is criticism a Staff member’s work, take note of their method of conveyance. If they say “I don’t like this project, it makes me feel anxious and that sucks”, this is fine. If however they say “I don’t like this project, XYZ is just a shitty staff member”, or if the ridicule against a staff member becomes purely cyber-bullying in nature (for example attacking a staff member based on appearance, workload, sexuality, gender, or other such), then Staff members are expected to defend the honor of the Staff member in question and in the very least request that the players cease their degradation of the reputation of the Staff member. Further action can be taken to correct their views by arguing against their misconceptions, or to report the occurrence to Direction, though neither of these are legally required within Staff. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Furthermore, when Staff member witness something similar occuring in the direction of Staff members, the individual who in question is not present, they are required to encourage a positive dialogue. Players are certainly allowed to express their feelings about staff projects, but Staff should be aware to ensure this does not take a toxic charge. When a player is criticism a Staff member’s work, take note of their method of conveyance. If they say “I don’t like this project, it makes me feel anxious and that sucks”, this is fine. If however they say “I don’t like this project, XYZ is just a shitty staff member”, or if the ridicule against a staff member becomes purely cyber-bullying in nature (for example attacking a staff member based on appearance, workload, sexuality, gender, or other such), then Staff members are expected to defend the honor of the Staff member in question and in the very least request that the players cease their degradation of the reputation of the Staff member. Further action can be taken to correct their views by arguing against their misconceptions, or to report the occurrence to Direction, though neither of these are legally required within Staff. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*You should do whatever you can to ensure Massive’s <del style="font-weight: bold; text-decoration: none;">50</del>+ Staff members represent a united front, and not an internally divided group of people with their own ambitions and plans, even if this would be a reflection of reality.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*You should do whatever you can to ensure Massive’s <ins style="font-weight: bold; text-decoration: none;">70</ins>+ Staff members represent a united front, and not an internally divided group of people with their own ambitions and plans, even if this would be a reflection of reality.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff should sacrifice what liberties in full freedom of speech they have in public, and console themselves with the fact that they have endless access from the bottom to the top to argue their points with Staff, and to affect how the server is managed beyond what any normal player could. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Staff should sacrifice what liberties in full freedom of speech they have in public, and console themselves with the fact that they have endless access from the bottom to the top to argue their points with Staff, and to affect how the server is managed beyond what any normal player could. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A Staff member should never be in the situation where they hear that a Discord or Faction talked badly about them in your presence, and you just let it happen while sitting there silently. This is very hurtful.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*A Staff member should never be in the situation where they hear that a Discord or Faction talked badly about them in your presence, and you just let it happen while sitting there silently. This is very hurtful.</div></td></tr>
</table>Jared4242https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=22696&oldid=prevCS Birb: /* Rule Seven: Hierarchy and Direction */2019-04-04T01:24:40Z<p><span dir="auto"><span class="autocomment">Rule Seven: Hierarchy and Direction</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 01:24, 4 April 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l66">Line 66:</td>
<td colspan="2" class="diff-lineno">Line 66:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a collection department that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by Direction Rank2 LumosJared <del style="font-weight: bold; text-decoration: none;">and </del>SpunSugar<del style="font-weight: bold; text-decoration: none;">. They in turn are followed by Rank1 </del>CS_Birb and TheComputerGeek2. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision taking powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to the actions of his team mates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a collection department that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by Direction Rank2<ins style="font-weight: bold; text-decoration: none;">; </ins>LumosJared<ins style="font-weight: bold; text-decoration: none;">, </ins>SpunSugar<ins style="font-weight: bold; text-decoration: none;">, </ins>CS_Birb and TheComputerGeek2. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision taking powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to the actions of his team mates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Rank1, Rank2, Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Rank1, Rank2, Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. </div></td></tr>
<tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l76">Line 76:</td>
<td colspan="2" class="diff-lineno">Line 76:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Any Staff member experiencing a dispute with another staff member must report this to Direction. Staff should attempt to not let a situation degrade to where a working relationship reaches a point of inactivity, even if the dispute has already been resolved. It is possible that a dispute may at some point flare up again and not result in a positive outcome, and it is helpful if HR and Direction is aware of the dispute ahead of time to handle it.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*Any Staff member experiencing a dispute with another staff member must report this to Direction. Staff should attempt to not let a situation degrade to where a working relationship reaches a point of inactivity, even if the dispute has already been resolved. It is possible that a dispute may at some point flare up again and not result in a positive outcome, and it is helpful if HR and Direction is aware of the dispute ahead of time to handle it.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*All communication to Direction, when specified, is 100% confidential and may only be discussed among Direction. Further confidentiality may be requested and granted on request. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*All communication to Direction, when specified, is 100% confidential and may only be discussed among Direction. Further confidentiality may be requested and granted on request. </div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>*For the sake of Central Authority. The highest owner of the Server always retains the capacity to act as the final say and decider in any and all matters when no clear conclusion can be made by team members, or when a person lower on the hierarchy is accused of misconduct, and is beyond reproach of their equals in rank. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*For the sake of Central Authority. The highest owner of the Server always retains the capacity to act as the final say and decider in any and all matters when no clear conclusion can be made by team members, or when a person lower on the hierarchy is accused of misconduct, and is beyond reproach of their equals in rank.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Eight: Anti-Corruption Minimalism==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Eight: Anti-Corruption Minimalism==</div></td></tr>
</table>CS Birbhttps://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=21969&oldid=prevJared4242: /* Rule Two: Voice Communication and Centralization */2019-01-11T02:14:46Z<p><span dir="auto"><span class="autocomment">Rule Two: Voice Communication and Centralization</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:14, 11 January 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l19">Line 19:</td>
<td colspan="2" class="diff-lineno">Line 19:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Being able to use Voice Chat is essential, in fact it is a requirement to even be allowed to apply for Staff. Voice Chat offers great advantages in a team based environment, including but not limited to actually making discussions far less aggressive and in your face, because you get instant vocal feedback, and also making it easier to personify a Staff member and put a voice to the name, thus humanize your team members. Voice Communication is so crucial, that it is required for every Staff member to participate in a Staff Meeting at least once per calendar month, unless special circumstances or specific permission due to time zones or working hours is given. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Being able to use Voice Chat is essential, in fact it is a requirement to even be allowed to apply for Staff. Voice Chat offers great advantages in a team based environment, including but not limited to actually making discussions far less aggressive and in your face, because you get instant vocal feedback, and also making it easier to personify a Staff member and put a voice to the name, thus humanize your team members. Voice Communication is so crucial, that it is required for every Staff member to participate in a Staff Meeting at least once per calendar month, unless special circumstances or specific permission due to time zones or working hours is given. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Furthermore, we maintain a <del style="font-weight: bold; text-decoration: none;">Skype and </del>Discord system<del style="font-weight: bold; text-decoration: none;">. We are currently still in the process of transitioning from Skype to Discord, especially with impending Skype updates making the program less suitable for large group cohesion. Skype is currently still used to provide the most important alerts, while most departments have started moving over to Discord instead</del>. It is as such crucial that any staff member have access to <del style="font-weight: bold; text-decoration: none;">both</del>, and log onto <del style="font-weight: bold; text-decoration: none;">both </del>at least once every 2 days unless circumstances make this difficult or impossible. Failing to take note of notifications issued to all staff through these mediums are no excuse to failing to comply, or making mistakes out of ignorance. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Furthermore, we maintain a Discord system. It is as such crucial that any staff member have access to <ins style="font-weight: bold; text-decoration: none;">Discord</ins>, and log onto <ins style="font-weight: bold; text-decoration: none;">it </ins>at least once every 2 days unless circumstances make this difficult or impossible. Failing to take note of notifications issued to all staff through these mediums are no excuse to failing to comply, or making mistakes out of ignorance. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Staff is also afforded several social Discords where communication between Staff members is strongly encouraged. Even if a Staff member is not in the same department as another, they are still encouraged to communicate with one another to avoid silo-forming in our organization, and to encourage cross-department communication which is essential to providing better implemented services to all players. For example, Lore benefits from having the backup of Game staff during event hosting so they can focus on the actual lore, while Quest benefits from World staff members building their quest locations to the highest quality possible for the best experience possible. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Staff is also afforded several social Discords where communication between Staff members is strongly encouraged. Even if a Staff member is not in the same department as another, they are still encouraged to communicate with one another to avoid silo-forming in our organization, and to encourage cross-department communication which is essential to providing better implemented services to all players. For example, Lore benefits from having the backup of Game staff during event hosting so they can focus on the actual lore, while Quest benefits from World staff members building their quest locations to the highest quality possible for the best experience possible. </div></td></tr>
</table>Jared4242https://wiki.massivecraft.com/index.php?title=Staff:Codex&diff=21614&oldid=prevCS Birb at 21:04, 4 November 20182018-11-04T21:04:23Z<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 21:04, 4 November 2018</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l66">Line 66:</td>
<td colspan="2" class="diff-lineno">Line 66:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>==Rule Seven: Hierarchy and Direction==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a collection department that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by Direction Rank2 LumosJared and SpunSugar. They in turn are followed by Rank1 CS_Birb and <del style="font-weight: bold; text-decoration: none;">CnocBride</del>. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision taking powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to the actions of his team mates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>MassiveCraft Staff has a pyramid shaped hierarchy that sometimes, when the situation calls for it, can function like a flat hierarchy structure. In most cases, MassiveCraft is ran from the top down by Direction Staff. Direction Staff is not really a functional department of its own, but more of a collection department that takes exceptional leaders from other departments. Unofficially, the server is centrally owned by MonMarty, but often more in practice, direct control is delegated among the Directors of MassiveCraft. MonMarty is Direction Rank3, followed by Direction Rank2 LumosJared and SpunSugar. They in turn are followed by Rank1 CS_Birb and <ins style="font-weight: bold; text-decoration: none;">TheComputerGeek2</ins>. The owner does not take a direct CEO approach, but rather delegates tasks to different specialized departments, creating a flat hierarchy. Direction runs the server with a Hierarchical consensus where some department members have executive decision taking powers that exceed the owner’s on a local level. It is important for both players and Staff members to take note of this, because running to a different person when you don’t like the decision made by another doesn’t work on MassiveCraft. Furthermore, if you do not like the decision made by an Admin, running to the owner to get that decision overturned is going to be equally ineffective since the owner has voluntarily surrendered the right to object to the actions of his team mates. Only in special circumstances should a higher up be convinced that another team member did something out of the books, can action be taken by superiors. </div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Rank1, Rank2, Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. </div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>On a local level, Rank1, Rank2, Rank3 can all have equal arguing power within their departments, including leaders and even the owner(s). Within Staff, discussions are among equals when it concerns a healthy debate to create a better end product. At some point however, higher ups may end a debate by stating that a consensus has been reached in their eyes, and that those who continue to argue it should accept it and move along. This is not them calling the rank card, but rather ensuring that the hierarchy remains functional and doesn’t get slowed down by endless debates as is likely to happen in a completely flat structure. </div></td></tr>
</table>CS Birb