From fd2f362acf55bf69b0f31b293849ff93ae68bff1 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:00:42 -0800 Subject: [PATCH 01/34] Update and rename spawn-town-tor.md to spawn-town-vr.md + Edits to text --- other/spawn-town-tor.md | 45 ------------------------ other/spawn-town-vr.md | 77 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 77 insertions(+), 45 deletions(-) delete mode 100644 other/spawn-town-tor.md create mode 100644 other/spawn-town-vr.md diff --git a/other/spawn-town-tor.md b/other/spawn-town-tor.md deleted file mode 100644 index 8e843ec..0000000 --- a/other/spawn-town-tor.md +++ /dev/null @@ -1,45 +0,0 @@ -# Spawn Town terms of reference - -## Spawn Town Principles - -1\. Spawn Town should: -* be free and easy to use -* provide equal opportunities for all players -* provide a service to the community -* be easily navigable -* provide a good first impression. - -## Spawn Town Committee - -### Purpose -2\. The Spawn Town Committee is responsible for upholding the principles of Spawn Town. - -### Structure -3\. The Committee consists of a small number of dedicated players chosen by Staff. - -4\. The Committee members should be representative of the users of Spawn Town. - -5\. The Committee members should be no higher than the rank of Trusted. - -### Powers - - -6\. The Committee has the power to set and enforce the following in order to uphold the principles of Spawn Town: -* Restrictions on where players are allowed to build. -* Area-specific restrictions on the purpose of builds (e.g. shops only). -* Periods of inactivity beyond which a build may be removed. -* Build height restrictions. -* Restrictions on which items shops are allowed to sell. -* Restrictions on the price at which shops are allowed to sell items. - -7\. The Committee can also make determinations outside of the rules listed in 6 with Staff consent. - -8\. In cases where existing builds conflict with a new Committee determination, the determination should give the players a reasonable amount of time to comply or grant them an exception. - -9\. All Committee decisions require either: - -    a) the unanimous consent of all committee members; or - -    b) the consent of at least two committee members, no dissenting views within 24 hours, and staff approval. - -10\. Staff have the power to veto a Committee decision if they do not believe it is consistent with the principles of Spawn Town. diff --git a/other/spawn-town-vr.md b/other/spawn-town-vr.md new file mode 100644 index 0000000..5ec4300 --- /dev/null +++ b/other/spawn-town-vr.md @@ -0,0 +1,77 @@ +# Spawn Town Values, Outline, and Regulations + +## Spawn Town Values + +1\. Spawn Town should: +* be free and easy to use +* provide equal opportunities for all players +* provide a service to the community +* be easily navigable +* provide a good first impression. + +## Spawn Town Committee + +### Outline +2\. The Spawn Town Committee is a group of staff members who have taken on the duty of maintaining and creating new Spawn Town standards. + +3\. The Committee consists of all staff members, however is an optional duty and consists of mostly trusted members. + +### Powers + +4\. The Committee has the power to set and enforce the following in order to uphold the principles of Spawn Town: +* Restrictions on where players are allowed to build. +* Area-specific restrictions on the purpose of builds (e.g. shops only). +* Periods of inactivity beyond which a build may be removed. +* Build height restrictions. +* Restrictions on which items shops are allowed to sell. +* Restrictions on the price at which shops are allowed to sell items. + +5\. The Committee can also make determinations outside of the rules listed in 6 with Admin consent + +6\. In cases where existing builds conflict with a new Committee determination, the determination should give the players a reasonable amount of time to comply or grant them an exception. + +7\. All new Committee regulations and interpretations require either: + +    a) the unanimous consent of all active Committee members; or + +    b) the consent of at least two committee members and no objections within 24 hours. + +8\. Members of the Committee are allowed to repeal a regulation or decision with a 6 or more member backing, and no more than 4 opposing. This ratio can be adjusted based on activity. + +9\. It is thought that when a new map comes to Froobworld, the Committee is to reevaluate its purpose and adjust/restructure as is needed. + +## Spawn Town Regulations + +1\. The first 2 rows are reserved for shops. Any non-shop builds must be made outside the first 2 rows. Non-shop builds within the first 2 rows will be removed by the spawn committee after a 2 weeks notice. + +2\. Do not build outside your plot border. Any blocks outside borders will be removed without notice. Furthermore, do not change the plot border except for reasonable doorways. + +3\. Shops must comply with lag restrictions. Shops that do not comply will be removed. Restrictions per plot are: + +    - 0 powered beacons + +    - 2 glow signs + +    - 6 banners + +    - 15 item frames + +    - No chests (barrels only) + +4\. Stay within build height limits. Shops that go outside the set limits will be removed by the spawn committee after a 2 week notice. The first row of plots is allowed 25 blocks, and each subsequent row is allowed +10 more as distance from spawn increases. There are no limits to how low you can go! + +5\. Inactive shops will be removed by the spawn committee. If a shop has been inactive for 2 weeks, the owner will get a 2 weeks notice via the in-game mail system. If there's no signs of activity after those 2 weeks, the shop will be removed. + +6\. Shops must be built within 2 weeks of claiming the plot. If a shop is not built by that time, the claim will be removed and the plot will be reset for the next person. + +7\. Prices cannot go under the set minimum prices. Shops that do go under these prices will be closed by the spawn committee until the owner fixes their prices. These prices can be found here: [Minimum-Prices](https://froobworld.com/wiki/Minimum_prices) + +8\. Only one shop per person/organization is allowed. This means you can't profit from or help with the upkeep of multiple shops. Organizations can't claim multiple plots as one for each member if they will actively help with the upkeep of the shops. + +9\. Use common sense when interpreting these rules. Any loopholes will not be appreciated and will cause a reaction from the spawn committee. + +10\. For every broken rule/removed shop, a player has 1 more chance, where they must rebuild one plot-row back. If rules are broken again, they will not be allowed to have a shop in Spawn Town. + +11\. All shops must have a clear sign displaying who owns the shop. + +If you have questions, please ask us in our [Discord](https://discord.gg/Zg3U2yErSe) server! From e5b276884af5d92bd367a3deeabff8387fd52cf6 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:03:27 -0800 Subject: [PATCH 02/34] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e7fa94f..f23b49b 100644 --- a/README.md +++ b/README.md @@ -9,4 +9,4 @@ * [Staff inactivity policy](staff-policies/staff-inactivity-policy) ### Other -* [Spawn Town terms of reference](other/spawn-town-tor) +* [Spawn Town Values and Regulations](other/spawn-town-vr) From 92d67e28ff5a5c6ec16a3e73875066134eb43376 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:04:35 -0800 Subject: [PATCH 03/34] Delete staff-policies/staff-inactivity-policy.md Integrated into respective policy pages --- staff-policies/staff-inactivity-policy.md | 17 ----------------- 1 file changed, 17 deletions(-) delete mode 100644 staff-policies/staff-inactivity-policy.md diff --git a/staff-policies/staff-inactivity-policy.md b/staff-policies/staff-inactivity-policy.md deleted file mode 100644 index 9d74294..0000000 --- a/staff-policies/staff-inactivity-policy.md +++ /dev/null @@ -1,17 +0,0 @@ -# Staff inactivity policy - -## Trusted and Staff - -1\. Users in the Trusted and Staff role must remain active on the server in order to keep their role. - -2\. Users who have not been active for a period of six months may be removed from their roles without consultation. - -3\. Users who have lost their role due to inactivity must go through the standard process to get the role back. - -## Admins - -4\. Users in the Admin role may be removed from their position if they are inactive for an extended period of time without any indication of returning. - -5\. It will be up to the other admins to agree on when an inactive user is removed from the Admin role. - -6\. If possible, the other admins should always try to make contact with the inactive user. \ No newline at end of file From 5c50e5b903837ef3798e20540cea6f7f0b189320 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:13:05 -0800 Subject: [PATCH 04/34] Update admin-appointment-process.md --- staff-policies/admin-appointment-process.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/staff-policies/admin-appointment-process.md b/staff-policies/admin-appointment-process.md index dc68db5..d233a74 100644 --- a/staff-policies/admin-appointment-process.md +++ b/staff-policies/admin-appointment-process.md @@ -2,14 +2,24 @@ 1\. In order to be eligible for consideration of the Admin role a player must: -    a) have joined the server at least three years ago; and ++ have joined the server at least three years ago; and -    b) have been active on the server as a Staff member over the last two years; and ++ have been active on the server as a Staff member over the last two years; and -    c) be of extremely good standing in the community. ++ be of extremely good standing in the community. 2\. Only froobynooby can nominate a player for the Admin role. 3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role. 4\. If there is total agreement amongst the admins the player may be made Admin. + +# Admin removal process + +1\. An admin may be removed from the role if one of the following occurs: + ++ The admin has been inactive for an extended period of time with no indication of returning. + - If possible, other admins should always try to contact the inactive user ++ The admin has violated Froobworld's policies. + +2\. Removal of an admin should be determined unanymously by all other admins From f90b0c6aaf57e790f0aded4646b8ebbbc81b8af8 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:18:13 -0800 Subject: [PATCH 05/34] Update staff-appointment-process.md --- staff-policies/staff-appointment-process.md | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/staff-policies/staff-appointment-process.md b/staff-policies/staff-appointment-process.md index 3c99217..dafa103 100644 --- a/staff-policies/staff-appointment-process.md +++ b/staff-policies/staff-appointment-process.md @@ -2,16 +2,26 @@ 1\. In order to be eligible for consideration of the Staff role a player must: -    a) have joined the server at least six months ago; and ++ have joined the server at least six months ago; and -    b) have been active on the server as a Trusted member over the last two months; and ++ have been active on the server as a Trusted member over the last two months; and -    c) be of very good standing in the community. ++ be of very good standing in the community. 2\. Any admin can nominate an eligible player for the Staff role. -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role. +3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role and existing staff members are usually consulted to bring a consensus. 4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. -5\. If there is total agreement amongst the admins the player may be made Staff. +5\. If there is total agreement amongst the admins the player may be invited to the staff team + +# Staff removal process + +1\. A staff member may be removed from the role if one of the following occurs: + ++ The staff member has been inactive on the server for longer than 6 months + ++ The staff member has violated Froobworld's policies. + +2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. From 9438f470027329103c58bc31969ace842ad3be44 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:20:15 -0800 Subject: [PATCH 06/34] Update staff-appointment-process.md --- staff-policies/staff-appointment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/staff-policies/staff-appointment-process.md b/staff-policies/staff-appointment-process.md index dafa103..d220468 100644 --- a/staff-policies/staff-appointment-process.md +++ b/staff-policies/staff-appointment-process.md @@ -10,7 +10,7 @@ 2\. Any admin can nominate an eligible player for the Staff role. -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role and existing staff members are usually consulted to bring a consensus. +3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members are usually consulted to bring a consensus. 4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. From adceb14ea5d1e7583e5ae3eeaaf510515319db97 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:20:43 -0800 Subject: [PATCH 07/34] Update trusted-appointment-process.md --- staff-policies/trusted-appointment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/staff-policies/trusted-appointment-process.md b/staff-policies/trusted-appointment-process.md index dca5aed..28f8be3 100644 --- a/staff-policies/trusted-appointment-process.md +++ b/staff-policies/trusted-appointment-process.md @@ -12,7 +12,7 @@     c) be of good standing in the community. -2\. Any staff member can nominate an eligible player for the Trusted role. +2\. Any staff member can nominate an eligible player for the Trusted role with existing Trusted members usually being consulted to bring a consensus. 3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role. From 2146d36d9a07ed44348c64a4017e3838e1b5a1c6 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:20:56 -0800 Subject: [PATCH 08/34] Update staff-appointment-process.md --- staff-policies/staff-appointment-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/staff-policies/staff-appointment-process.md b/staff-policies/staff-appointment-process.md index d220468..4cce1ae 100644 --- a/staff-policies/staff-appointment-process.md +++ b/staff-policies/staff-appointment-process.md @@ -10,7 +10,7 @@ 2\. Any admin can nominate an eligible player for the Staff role. -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members are usually consulted to bring a consensus. +3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. 4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. From 2349f594bc10adcb537f7895d9b14d2224481e55 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:22:16 -0800 Subject: [PATCH 09/34] Update trusted-appointment-process.md --- staff-policies/trusted-appointment-process.md | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/staff-policies/trusted-appointment-process.md b/staff-policies/trusted-appointment-process.md index 28f8be3..29008d9 100644 --- a/staff-policies/trusted-appointment-process.md +++ b/staff-policies/trusted-appointment-process.md @@ -6,16 +6,26 @@ 1\. In order to be eligible for consideration of the Trusted role a player must: -    a) have joined the server at least two months ago; and ++ have joined the server at least two months ago; and -    b) have been active on the server over the last month; and ++ have been active on the server over the last month; and -    c) be of good standing in the community. ++ be of good standing in the community. 2\. Any staff member can nominate an eligible player for the Trusted role with existing Trusted members usually being consulted to bring a consensus. -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role. +3\. It will be up to the admins and staff to make a judgement on the nominated player's fitness for the role. 4\. Although there is no set limit to the number of Trusted, if it is thought the number of Trusted is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. 5\. If there is general agreeance amongst the admins the player may be made Trusted. + +# Trusted removal process + +1\. A Trusted member may be removed from the role if one of the following occurs: + ++ The Trusted member has been inactive on the server for longer than 6 months + ++ The Trusted member has violated Froobworld's policies. + +2\. Removal of a Trusted member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. From a8fc96c4b35b1eb18837bb59596e9d13aad13b7f Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:23:46 -0800 Subject: [PATCH 10/34] Update trusted-appointment-process.md --- staff-policies/trusted-appointment-process.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/staff-policies/trusted-appointment-process.md b/staff-policies/trusted-appointment-process.md index 29008d9..2083dbf 100644 --- a/staff-policies/trusted-appointment-process.md +++ b/staff-policies/trusted-appointment-process.md @@ -10,7 +10,9 @@ + have been active on the server over the last month; and -+ be of good standing in the community. ++ be of good standing in the community; and + ++ have at least 4 days of active playtime. (data collected from [plan.froobworld.com](https://plan.froobworld.com/server/Server%201/players)) 2\. Any staff member can nominate an eligible player for the Trusted role with existing Trusted members usually being consulted to bring a consensus. From 14bd84a63094c35ee7871bc613c3e3563a3b33e4 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:24:24 -0800 Subject: [PATCH 11/34] Create staff-policies --- staff-policies/staff-policies | 1 + 1 file changed, 1 insertion(+) create mode 100644 staff-policies/staff-policies diff --git a/staff-policies/staff-policies b/staff-policies/staff-policies new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/staff-policies/staff-policies @@ -0,0 +1 @@ + From 8254c0e3703c4b7171480fc404c1826d7766a1a3 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:25:35 -0800 Subject: [PATCH 12/34] Update staff-policies --- staff-policies/staff-policies | 2 ++ 1 file changed, 2 insertions(+) diff --git a/staff-policies/staff-policies b/staff-policies/staff-policies index 8b13789..6f86f38 100644 --- a/staff-policies/staff-policies +++ b/staff-policies/staff-policies @@ -1 +1,3 @@ +# Staff Polices +1\. This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. From 2dc3cd747a137152d133c58c5db8c7cc3e58ce36 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:31:03 -0800 Subject: [PATCH 13/34] Update staff-policies --- staff-policies/staff-policies | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/staff-policies/staff-policies b/staff-policies/staff-policies index 6f86f38..b357a42 100644 --- a/staff-policies/staff-policies +++ b/staff-policies/staff-policies @@ -1,3 +1,15 @@ # Staff Polices -1\. This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. +This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. This is clarafication to Froobworld's Rules and Punishments to specify staff actions. + +## Demotion + +The demotion of a staff member, as stated in all appointment policies, is to happen because of one of the following: + ++ Inactivity + _Admins: An extended period of time with no indication of returning + _Staff and Trusted: a 6 month period + ++ Violation of Froobworld Policies + + From eed14cba52d9c18b19e0a7c3ad0fd053faad47e1 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:33:05 -0800 Subject: [PATCH 14/34] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f23b49b..d1a7162 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ * [Trusted appointment process](staff-policies/trusted-appointment-process) * [Staff appointment process](staff-policies/staff-appointment-process) * [Admin appointment process](staff-policies/admin-appointment-process) -* [Staff inactivity policy](staff-policies/staff-inactivity-policy) +* [Staff Guidelines](staff-policies/staff-inactivity-policy) ### Other * [Spawn Town Values and Regulations](other/spawn-town-vr) From 3eb88139453fd6e20a4b9e3275cfdb1e5827edc0 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:34:45 -0800 Subject: [PATCH 15/34] Update and rename staff-policies to staff-guidelines --- staff-policies/{staff-policies => staff-guidelines} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename staff-policies/{staff-policies => staff-guidelines} (100%) diff --git a/staff-policies/staff-policies b/staff-policies/staff-guidelines similarity index 100% rename from staff-policies/staff-policies rename to staff-policies/staff-guidelines From 4932b0565652230b8752f0bf1ebaa16948654938 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:35:08 -0800 Subject: [PATCH 16/34] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d1a7162..a9982e7 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ * [Trusted appointment process](staff-policies/trusted-appointment-process) * [Staff appointment process](staff-policies/staff-appointment-process) * [Admin appointment process](staff-policies/admin-appointment-process) -* [Staff Guidelines](staff-policies/staff-inactivity-policy) +* [Staff Guidelines](staff-policies/staff-guidelines) ### Other * [Spawn Town Values and Regulations](other/spawn-town-vr) From 428c176c2a28a962574716d4874bfd610817b2ce Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:36:22 -0800 Subject: [PATCH 17/34] Update README.md --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a9982e7..4875c75 100644 --- a/README.md +++ b/README.md @@ -3,10 +3,10 @@ * [Rules and punishments](rules-and-punishments/rules-and-punishments) ### Staff policies -* [Trusted appointment process](staff-policies/trusted-appointment-process) -* [Staff appointment process](staff-policies/staff-appointment-process) -* [Admin appointment process](staff-policies/admin-appointment-process) -* [Staff Guidelines](staff-policies/staff-guidelines) +* [Trusted appointment process](staff-policies/trusted-appointment-process.md) +* [Staff appointment process](staff-policies/staff-appointment-process.md) +* [Admin appointment process](staff-policies/admin-appointment-process.md) +* [Staff Guidelines](staff-policies/staff-guidelines.md) ### Other -* [Spawn Town Values and Regulations](other/spawn-town-vr) +* [Spawn Town Values and Regulations](other/spawn-town-vr.md) From b0fb3bb9319e31ad01746da7526a8b2a5fe2ef99 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:45:15 -0800 Subject: [PATCH 18/34] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4875c75..5fb39bc 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ * [Trusted appointment process](staff-policies/trusted-appointment-process.md) * [Staff appointment process](staff-policies/staff-appointment-process.md) * [Admin appointment process](staff-policies/admin-appointment-process.md) -* [Staff Guidelines](staff-policies/staff-guidelines.md) +* [Staff Guidelines](staff-policies/staff-guidelines) ### Other * [Spawn Town Values and Regulations](other/spawn-town-vr.md) From 51ffaaa3a25ce47188209d445c822662b2886185 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:47:10 -0800 Subject: [PATCH 19/34] Update staff-guidelines --- staff-policies/staff-guidelines | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/staff-policies/staff-guidelines b/staff-policies/staff-guidelines index b357a42..2b5df25 100644 --- a/staff-policies/staff-guidelines +++ b/staff-policies/staff-guidelines @@ -7,9 +7,10 @@ This is a collection of policies to be followed by staff members (Admins, Staff, The demotion of a staff member, as stated in all appointment policies, is to happen because of one of the following: + Inactivity - _Admins: An extended period of time with no indication of returning - _Staff and Trusted: a 6 month period + - Admins: An extended period of time with no indication of returning + - Staff and Trusted: a 6 month period -+ Violation of Froobworld Policies ++ A clear violation of Froobworld Policies + - As the upholders of rules on Froobworld, staff members should follow all rules strictly. Violations should be reported to higher staff members or equals. From 365eea565baad7b3f8a1e9b60ef67c05c8517b5e Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:49:13 -0800 Subject: [PATCH 20/34] Delete staff-policies/staff-guidelines --- staff-policies/staff-guidelines | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 staff-policies/staff-guidelines diff --git a/staff-policies/staff-guidelines b/staff-policies/staff-guidelines deleted file mode 100644 index 2b5df25..0000000 --- a/staff-policies/staff-guidelines +++ /dev/null @@ -1,16 +0,0 @@ -# Staff Polices - -This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. This is clarafication to Froobworld's Rules and Punishments to specify staff actions. - -## Demotion - -The demotion of a staff member, as stated in all appointment policies, is to happen because of one of the following: - -+ Inactivity - - Admins: An extended period of time with no indication of returning - - Staff and Trusted: a 6 month period - -+ A clear violation of Froobworld Policies - - As the upholders of rules on Froobworld, staff members should follow all rules strictly. Violations should be reported to higher staff members or equals. - - From c9b97fe9b8080c01fd9dd9ac4ca45e7b899bc49e Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:49:30 -0800 Subject: [PATCH 21/34] Add files via upload From 02b1ead9b3bb651dd67a8d122a1a59594da6f8ce Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:50:20 -0800 Subject: [PATCH 22/34] Add files via upload --- staff-policies/staff-guidelines.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 staff-policies/staff-guidelines.md diff --git a/staff-policies/staff-guidelines.md b/staff-policies/staff-guidelines.md new file mode 100644 index 0000000..4cce1ae --- /dev/null +++ b/staff-policies/staff-guidelines.md @@ -0,0 +1,27 @@ +# Staff appointment process + +1\. In order to be eligible for consideration of the Staff role a player must: + ++ have joined the server at least six months ago; and + ++ have been active on the server as a Trusted member over the last two months; and + ++ be of very good standing in the community. + +2\. Any admin can nominate an eligible player for the Staff role. + +3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. + +4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. + +5\. If there is total agreement amongst the admins the player may be invited to the staff team + +# Staff removal process + +1\. A staff member may be removed from the role if one of the following occurs: + ++ The staff member has been inactive on the server for longer than 6 months + ++ The staff member has violated Froobworld's policies. + +2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. From 9401347d438940fd3cbd5baa7e91bad4bcbfdb48 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:50:46 -0800 Subject: [PATCH 23/34] Update staff-guidelines.md --- staff-policies/staff-guidelines.md | 31 +++++++++--------------------- 1 file changed, 9 insertions(+), 22 deletions(-) diff --git a/staff-policies/staff-guidelines.md b/staff-policies/staff-guidelines.md index 4cce1ae..d135c66 100644 --- a/staff-policies/staff-guidelines.md +++ b/staff-policies/staff-guidelines.md @@ -1,27 +1,14 @@ -# Staff appointment process +# Staff Polices -1\. In order to be eligible for consideration of the Staff role a player must: +This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. This is clarafication to Froobworld's Rules and Punishments to specify staff actions. -+ have joined the server at least six months ago; and +## Demotion -+ have been active on the server as a Trusted member over the last two months; and +The demotion of a staff member, as stated in all appointment policies, is to happen because of one of the following: -+ be of very good standing in the community. ++ Inactivity + - Admins: An extended period of time with no indication of returning + - Staff and Trusted: a 6 month period -2\. Any admin can nominate an eligible player for the Staff role. - -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. - -4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. - -5\. If there is total agreement amongst the admins the player may be invited to the staff team - -# Staff removal process - -1\. A staff member may be removed from the role if one of the following occurs: - -+ The staff member has been inactive on the server for longer than 6 months - -+ The staff member has violated Froobworld's policies. - -2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. ++ A clear violation of Froobworld Policies + - As the upholders of rules on Froobworld, staff members should follow all rules strictly. Violations should be reported to higher staff members or equals. From 66b61108dc1d0c2dd4de7aed886da54bc0ef59b9 Mon Sep 17 00:00:00 2001 From: jaron Date: Thu, 6 Mar 2025 18:51:00 -0800 Subject: [PATCH 24/34] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5fb39bc..4875c75 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ * [Trusted appointment process](staff-policies/trusted-appointment-process.md) * [Staff appointment process](staff-policies/staff-appointment-process.md) * [Admin appointment process](staff-policies/admin-appointment-process.md) -* [Staff Guidelines](staff-policies/staff-guidelines) +* [Staff Guidelines](staff-policies/staff-guidelines.md) ### Other * [Spawn Town Values and Regulations](other/spawn-town-vr.md) From a97142089d57503eb8b5dbc3440fe2444968fa77 Mon Sep 17 00:00:00 2001 From: jaron Date: Fri, 7 Mar 2025 21:12:36 -0800 Subject: [PATCH 25/34] Update staff-guidelines.md --- staff-policies/staff-guidelines.md | 28 ++++++++++++++++++++++++++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git a/staff-policies/staff-guidelines.md b/staff-policies/staff-guidelines.md index d135c66..8a7e4a5 100644 --- a/staff-policies/staff-guidelines.md +++ b/staff-policies/staff-guidelines.md @@ -1,6 +1,6 @@ # Staff Polices -This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. This is clarafication to Froobworld's Rules and Punishments to specify staff actions. +This is a collection of policies to be followed by staff members (Admins, Staff, and Trusted) on Froobworld. This is a clarification of Froobworld's Rules and Punishments to specify staff actions. ## Demotion @@ -8,7 +8,31 @@ The demotion of a staff member, as stated in all appointment policies, is to hap + Inactivity - Admins: An extended period of time with no indication of returning - - Staff and Trusted: a 6 month period + - Staff and Trusted: a 6-month period + A clear violation of Froobworld Policies - As the upholders of rules on Froobworld, staff members should follow all rules strictly. Violations should be reported to higher staff members or equals. + +## Internal Relations + +It is thought that, while somewhat separate in duties, the Froobworld staff team is to work together cohesively to keep our community functional. In this way, everyone is considered an equal, with all opinions being valued the same. + +The following will not be tolerated between members of staff or between staff and players: + ++ Pressuring others to make decisions + - Every staff member has their own voice, and this should never be undermined or altered by those in positions viewed to be higher. + ++ Pestering other members about past mistakes + - Mistakes are common and a part of learning. In now way should a staff member repremand another staff member for clearly unintentional mistakes. + ++ Dismissing other's opinions + - Every staff member contributes equally to the conversation, belittling this value should never occur. + ++ Responding to other's success with resentment + - Every staff member contributes equally to Froobworld, and each one is celebrated as a volunteer working towards making their community a better place. In moments of other's success, it is not okay for negativity to be spread in response. + +## External Relations + +It is thought that the Froobworld staff team is to be an extension of the players, made up by players. As a result, transparency should be used as much as possible to inform players about decisions that are affecting the community they have dedicated time to. + +For this reason, the following are to take place as stated: From 22f907e1285f1b87bcf8e61e4d6201bcd660e7fc Mon Sep 17 00:00:00 2001 From: jaron Date: Sat, 8 Mar 2025 16:49:12 -0800 Subject: [PATCH 26/34] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4875c75..3cd7f19 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ ## Index -### Rules and punishments +### Player policies * [Rules and punishments](rules-and-punishments/rules-and-punishments) ### Staff policies From eced2e6b1cf1c67b8c1a04dca33f5db289303ae7 Mon Sep 17 00:00:00 2001 From: jaron Date: Sat, 8 Mar 2025 16:50:33 -0800 Subject: [PATCH 27/34] Add files via upload --- rules-and-punishments/player-feedback.md | 27 ++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 rules-and-punishments/player-feedback.md diff --git a/rules-and-punishments/player-feedback.md b/rules-and-punishments/player-feedback.md new file mode 100644 index 0000000..4cce1ae --- /dev/null +++ b/rules-and-punishments/player-feedback.md @@ -0,0 +1,27 @@ +# Staff appointment process + +1\. In order to be eligible for consideration of the Staff role a player must: + ++ have joined the server at least six months ago; and + ++ have been active on the server as a Trusted member over the last two months; and + ++ be of very good standing in the community. + +2\. Any admin can nominate an eligible player for the Staff role. + +3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. + +4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. + +5\. If there is total agreement amongst the admins the player may be invited to the staff team + +# Staff removal process + +1\. A staff member may be removed from the role if one of the following occurs: + ++ The staff member has been inactive on the server for longer than 6 months + ++ The staff member has violated Froobworld's policies. + +2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. From 831829615343fa5b25211c28af0b300630267dba Mon Sep 17 00:00:00 2001 From: jaron Date: Sat, 8 Mar 2025 16:58:39 -0800 Subject: [PATCH 28/34] Update player-feedback.md --- rules-and-punishments/player-feedback.md | 28 ++++++------------------ 1 file changed, 7 insertions(+), 21 deletions(-) diff --git a/rules-and-punishments/player-feedback.md b/rules-and-punishments/player-feedback.md index 4cce1ae..68819ee 100644 --- a/rules-and-punishments/player-feedback.md +++ b/rules-and-punishments/player-feedback.md @@ -1,27 +1,13 @@ -# Staff appointment process +# Player Feedback -1\. In order to be eligible for consideration of the Staff role a player must: +In order to promote transparency between staff and players, it is encouraged that players use our [Player Contact Form](https://docs.google.com/forms/d/e/1FAIpQLScwLHIxw4l0wYWD70ZZ2zC_o56QElSNO-dqsfbhCyTcgupvEw/viewform) to submit suggestions, concerns and criticism. -+ have joined the server at least six months ago; and +When carrying out review of your suggestions, concerns and criticisms, the following will happen: -+ have been active on the server as a Trusted member over the last two months; and ++ Your message will be sent directly to the admin team, where it will be reviewed quickly. -+ be of very good standing in the community. ++ After review, we will evalute your message and make corrections as needed to our structure and system. -2\. Any admin can nominate an eligible player for the Staff role. ++ Once changes are made, you will recieve a response via email (which you provide on the form). -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. - -4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. - -5\. If there is total agreement amongst the admins the player may be invited to the staff team - -# Staff removal process - -1\. A staff member may be removed from the role if one of the following occurs: - -+ The staff member has been inactive on the server for longer than 6 months - -+ The staff member has violated Froobworld's policies. - -2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. +Thank you to those who use the feedback system, each message is greatly appreciated. From 30f801667fb478216a39e1b9ebe05b933e7e2228 Mon Sep 17 00:00:00 2001 From: jaron Date: Sat, 8 Mar 2025 17:03:38 -0800 Subject: [PATCH 29/34] Update staff-guidelines.md --- staff-policies/staff-guidelines.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/staff-policies/staff-guidelines.md b/staff-policies/staff-guidelines.md index 8a7e4a5..2fb5603 100644 --- a/staff-policies/staff-guidelines.md +++ b/staff-policies/staff-guidelines.md @@ -36,3 +36,8 @@ The following will not be tolerated between members of staff or between staff an It is thought that the Froobworld staff team is to be an extension of the players, made up by players. As a result, transparency should be used as much as possible to inform players about decisions that are affecting the community they have dedicated time to. For this reason, the following are to take place as stated: + ++ The player contact form is to be reviewed and the messages taken seriously (with moderation). + - For more information on our contact form, visit the [Player feedback](rules-and-punishments\player-feedback.md) page for more information. + ++ Large decisions and future changes should be decided based on player feedback, whether directly or in-directly. From 990a3ddebf3134f354e8c7cedb54e0d76a25c112 Mon Sep 17 00:00:00 2001 From: jaron Date: Sat, 8 Mar 2025 17:04:44 -0800 Subject: [PATCH 30/34] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3cd7f19..f482cd4 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,7 @@ ## Index ### Player policies -* [Rules and punishments](rules-and-punishments/rules-and-punishments) +* [Rules and punishments](rules-and-punishments/rules-and-punishments.md) +* [Player feedback](rules-and-punishments/player-feedback.md) ### Staff policies * [Trusted appointment process](staff-policies/trusted-appointment-process.md) From 47768465b2598f34890393cb664ad470d073bb7c Mon Sep 17 00:00:00 2001 From: jaron Date: Mon, 5 May 2025 16:43:27 -0700 Subject: [PATCH 31/34] Add files via upload --- staff-policies/deputies.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 staff-policies/deputies.md diff --git a/staff-policies/deputies.md b/staff-policies/deputies.md new file mode 100644 index 0000000..4cce1ae --- /dev/null +++ b/staff-policies/deputies.md @@ -0,0 +1,27 @@ +# Staff appointment process + +1\. In order to be eligible for consideration of the Staff role a player must: + ++ have joined the server at least six months ago; and + ++ have been active on the server as a Trusted member over the last two months; and + ++ be of very good standing in the community. + +2\. Any admin can nominate an eligible player for the Staff role. + +3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. + +4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. + +5\. If there is total agreement amongst the admins the player may be invited to the staff team + +# Staff removal process + +1\. A staff member may be removed from the role if one of the following occurs: + ++ The staff member has been inactive on the server for longer than 6 months + ++ The staff member has violated Froobworld's policies. + +2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. From 75e357d770d44146ef8c8333955ef9729c67507d Mon Sep 17 00:00:00 2001 From: jaron Date: Mon, 5 May 2025 16:50:13 -0700 Subject: [PATCH 32/34] Update deputies.md --- staff-policies/deputies.md | 27 ++++++++++----------------- 1 file changed, 10 insertions(+), 17 deletions(-) diff --git a/staff-policies/deputies.md b/staff-policies/deputies.md index 4cce1ae..a76fa63 100644 --- a/staff-policies/deputies.md +++ b/staff-policies/deputies.md @@ -1,27 +1,20 @@ -# Staff appointment process +# Deputies -1\. In order to be eligible for consideration of the Staff role a player must: +A deputy is a staff member who has been selected to obtain temporary access to commands of a the staff level above them. Staff can deputize a player in which case they take on the responsiblility of said player. -+ have joined the server at least six months ago; and +1\. Staff Deputies will be appointed if they are as follows: -+ have been active on the server as a Trusted member over the last two months; and ++ Shown responsibility with current powers. -+ be of very good standing in the community. ++ Shown they can handle difficult situations in a positive way. -2\. Any admin can nominate an eligible player for the Staff role. +2\. Admin Deputies will be appointed if they are as follows: -3\. It will be up to the admins to make a judgement on the nominated player's fitness for the role with existing staff members usually being consulted to bring a consensus. ++ Shown responsibility with current powers. -4\. Although there is no set limit to the number of Staff, if it is thought the number of Staff is becoming excessively large the admins should reserve new appointments to only the most exceptional nominations. ++ Shown they can handle difficult situations in a positive way. -5\. If there is total agreement amongst the admins the player may be invited to the staff team +3\. The length of a deputy depends on who deputized them, but will likely last multiple weeks. This is a way for Admins to judge the responsiblity of future Staff and Admin candidates. -# Staff removal process +4\. Deputies must adhere to all Froobworld policies along with other staff members. -1\. A staff member may be removed from the role if one of the following occurs: - -+ The staff member has been inactive on the server for longer than 6 months - -+ The staff member has violated Froobworld's policies. - -2\. Removal of a staff member can take place without consultation. Players who lose their role due to inactivity must go through the standard process of getting it back. From ba2f091ef898b05385106d99e0b583c35c32e2cd Mon Sep 17 00:00:00 2001 From: jaron Date: Mon, 5 May 2025 16:51:13 -0700 Subject: [PATCH 33/34] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index f482cd4..db5e838 100644 --- a/README.md +++ b/README.md @@ -7,6 +7,7 @@ * [Trusted appointment process](staff-policies/trusted-appointment-process.md) * [Staff appointment process](staff-policies/staff-appointment-process.md) * [Admin appointment process](staff-policies/admin-appointment-process.md) +* [Staff Deputies](staff-policies/deputies.md) * [Staff Guidelines](staff-policies/staff-guidelines.md) ### Other From a9efb3e334abefbe67afd47ea392cc1c14fe0b85 Mon Sep 17 00:00:00 2001 From: jaron Date: Mon, 5 May 2025 17:41:58 -0700 Subject: [PATCH 34/34] Update rules-and-punishments.md added table --- .../rules-and-punishments.md | 114 ++++++++---------- 1 file changed, 51 insertions(+), 63 deletions(-) diff --git a/rules-and-punishments/rules-and-punishments.md b/rules-and-punishments/rules-and-punishments.md index 4d40512..eebefbc 100644 --- a/rules-and-punishments/rules-and-punishments.md +++ b/rules-and-punishments/rules-and-punishments.md @@ -6,98 +6,86 @@ 2\. As a general rule, staff members should be lenient. In most cases, a private warning sufficient in the first instance. -## Repeat offences - -3\. When a player has repeatedly and consistently gone against the rules, subsequent offences should no longer be considered as minor. - -## Griefing +## Punishment Guide + +_3\. This is a general staff guide, issue punishments at **your discretion**_ + + + + + + + + + + + + + + + + + + + + + + +
Punishment TypeAction (sequentially, with discretion)
Minor 🟢<1 day mute/jail, <3 day mute/join, <5 day mute/jail, moves to a moderate 🟠 punishment, procede likewise
Moderate 🟠<5 day mute/jail, 7 day mute/jail, <2 week temporary ban, moves to a major 🔴 punishment, procede likewise
Major 🔴<2 week temporary ban, < 1 month temporary ban, permanent ban, moves to a major 🟣 punishment, procede likewise
Severe 🟣permanent ban, exile (contact an admin)
+ + +## Griefing 4\. It is against the rules to grief another player. This includes, but is not limited to, knowingly: -* causing damage to someone else's property -* hampering someone else's enjoyment of the game -* limiting someone else's progress through the game -* killing someone else's animals without their permission -* intentionally and purposely causing the server to lag -* trolling. - -5\. Griefing can be punished by a temporary or permanent ban. - -6\. In cases where the griefing is minor in the opinion of the staff member, a private warning is sufficient. - -7\. In cases where the griefing is major in the opinion of the staff member and the staff member believes the player has no intention to follow the server's rules in the future, a permanent ban should be issued. +* causing damage to someone else's property 🔴 +* hampering someone else's enjoyment of the game 🟣 +* limiting someone else's progress through the game 🔴 +* killing someone else's animals without their permission 🟣 +* intentionally and purposely causing the server to lag 🟣 +* trolling. 🔴 -8\. A one to two week temporary ban is sufficient in most other cases. The staff member has discretion if they believe a shorter or longer ban is appropriate. ## Stealing, luring and scamming 9\. It is against the rules to steal from, lure or scam another player. This includes, but is not limited to: -* taking items from someone else's chests -* taking someone's items after they die -* having someone teleport to you in the hope they lose their items -* purposely giving someone a bad deal by withholding information (e.g. selling a mending book with curse of binding). +* taking items from someone else's chests 🟠 +* taking someone's items after they die 🟠 +* having someone teleport to you in the hope they lose their items 🔴 +* purposely giving someone a bad deal by withholding information (e.g. selling a mending book with curse of binding). 🟠 -10\. Stealing, luring and theft can be punished by a temporary or permanent ban. - -11\. In cases where the offence is minor in the opinion of the staff member, or the player and the victim are able to reconcile, a private warning is sufficient. - -12\. In cases where the offence is major in the opinion of the staff member and the staff member believes the player has no intention to follow the server's rules in the future, a permanent ban should be issued. - -13\. A one to two week temporary ban is sufficient in most other cases. The staff member has discretion if they believe a shorter or longer ban is appropriate. ## Cheats and exploits 14\. It is against the rules to use cheats or exploit glitches and game design flaws. This includes, but is not limited to: -* duping -* x-ray mods, texture packs or glitches -* mods and texture packs that significantly reduce lava fog (for finding ores) -* auto-mining/auto-building mods -* any mod that provides a significant advantage over other players. +* duping 🟣 +* x-ray mods, texture packs or glitches 🟠 +* mods and texture packs that significantly reduce lava fog (for finding ores) 🟠 +* auto-mining/auto-building mods 🔴 +* any mod that provides a significant advantage over other players. **_staff discretion_** -15\. For the purpose of this section, and despite 14, the following are not cheats or exploits: +14.5\. For the purpose of this section, and despite 14, the following are not cheats or exploits: * accessing and using the nether ceiling * minimap mods * autoclickers. -16\. Cheating and exploiting can be punished by a temporary or permanent ban. - -17\. In cases where the offence is minor in the opinion of the staff member, a private warning is sufficient. - -18\. In cases where the offence is major in the opinion of the staff member and the staff member believes the player has no intention to follow the server's rules in the future, a permanent ban should be issued. - -19\. A one to two week temporary ban is sufficient in most other cases. The staff member has discretion if they believe a shorter or longer ban is appropriate. ## Disrespectful behaviour 20\. It is against the rules to be disrespectful towards other people. This includes, but is not limited to: -* making derogatory remarks about a person or group of persons based on their personal beliefs or attributes. - -21\. Disrespectful behaviour can be punished by a mute or permanent ban. - -22\. In cases where the offence is minor in the opinion of the staff member, a private warning is sufficient. -23\. In the case where the offence is major in the opinion of the staff member and the staff member believes the player has no intention to follow the server's rules in the future, a permanent ban should be issued. +* making derogatory remarks about a person or group of persons based on their personal beliefs or attributes. 🔴 +* general distruption or rudeness 🟢 -24\. A one to two day mute is sufficient in most other cases. The staff member has discretion if they believe a shorter or longer mute is appropriate. ## Profanity -25\. It is against the rules to use profanity on the server, whether that be in chat, on signs, in books, in item names, or any other medium. +25\. It is against the rules to use profanity on the server, whether that be in chat, on signs, in books, in item names, or any other medium. 🟢 -26\. Use of profanity can be punished by a mute. - -27\. In cases where the offence is minor in the opinion of the staff member, a private warning is sufficient. - -28\. A 10 to 60 minute mute is sufficient in most other cases. The staff member has discretion if they believe a short or longer mute is appropriate. ## Advertising 29\. It is against the rules to use the server as a medium for advertising. 30\. A player should be considered to be advertising only if they are consistently or expressely using the server to make better known to other players a link, server or other service that is uncalled-for in the given context or generates financial benefits for that player. This includes, but is not limited to: -* directing other players to affiliate links -* joining the server expressly to direct players to a different server or link -* in contexts uncalled-for, linking players to a non-FroobWorld related Discord server. +* directing other players to affiliate links 🟢 +* joining the server expressly to direct players to a different server or link 🟠 +* in contexts uncalled-for, linking players to a non-FroobWorld related Discord server. 🟠 31\. For the avoidance of doubt, the following examples should not be considered advertising: * where context calls for it, providing another player a recommendation for a product they are not affiliated with * inviting a friend to play on another server. -32\. Advertising can be punished by a mute. - -33\. In cases where the offence is minor in the opinion of the staff member, a private warning is sufficient. - -34\. A 10 to 60 minute mute is sufficient in most other cases. The staff member has discretion if they believe a shorter or longer mute is appropriate.