WormRP:Community Code: Difference between revisions
(Created page with "<div class="noautonum" style="float:left; padding: 1em;">__TOC__</div> Our Community Code covers all the edge cases and procedural issues not covered by our main WormRP:Rul...") |
m (add motion text) |
||
| Line 8: | Line 8: | ||
(note: this is under construction --[[User:Keira|keira 💀]] 11:37, 9 March 2020 (UTC)) | (note: this is under construction --[[User:Keira|keira 💀]] 11:37, 9 March 2020 (UTC)) | ||
== References == | |||
{{reflist|refs= | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/549454249243967499|name=19-001|text=All "secret" approvals must be cleared by both mods. If a mod wants to do a secret approval one of the approvers, chosen by the community rep, fills the role of the second stamp.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/552663105994489875|name=19-002|text=Staff cannot change users names without their permission, unless the name is inappropriate. Staff cannot change the room names for factions without the faction's permission, unless it is inappropriate}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/564508603759722505|name=19-003|text=Institute a temporary cap on Tinkers to encourage people to play other types of capes. Every player may play a maximum of one Tinker, or one pseudo-tinker. Anyone who currently plays more than one such character or has a character in approvals by Monday the 8th, April 2019 will be grandfathered in. This cap may be rescinded at a future date.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/572259259941912596|name=19-004|text=Case 53s must have their altered biology connected with their power, the more closely connected the better. It is strongly encouraged to write to some detail who they were before becoming a Case 53, or to otherwise put extra effort into describing their personality. As always, low effort or setting inappropriate characters may be denied.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/582799056808706049|name=19-005|text=Information from Ward that would cause a significant retcon to capabilities of parahumans or of ways to handle parahumans in Earth Kaf will not be auto-implemented. They will be discussed as a staff.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/590759135667027978|name=19-006|text=A 100% voting participation being mandatory is very slow, particularly if people are going to be out of town or unable to use the internet for some reason.<br />In the interest of efficiency, once a motion has been discussed and brought to vote, a quorum of 2/3 can make any vote official. A one business day waiting period is to be observed to give staff members a chance to vote.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/590759372586745857|name=19-007|text=to alert @Staff when new agenda items are proposed.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/592216875589435444|name=19-008|text=Equipment is only useable in threads that are posted after that equipment is approved. If a thread is a GM run event the GM may allow story specific equipment to be used in that event, even if that equipment was posted after the event.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/593288714092806144|name=19-009|text=As the last step for character or (applicable) lore posts, the submitter must upload their character/lore/equipment to the wiki.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/593295162097270815|name=19-010|text=Instead of imposing a hard character limit we ask players that if they aren't playing someone to work with staff to come to a conclusion to their arcs.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/627167798895968286|name=19-011|text=Only people with the @PRT tag can roleplay PRT. If you have something the PRT is doing (or not doing!), @ them first. Clarify this with a rule in the sidebar. No more "oh the PRT didn't do this thing for seemingly no reason whatsoever"}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/633875332461494335|name=19-012|text=Amend the Community Representative position to include a one year term. Terms begin on the 20th of September. Elections will be conducted with a suitably secure system that will be chosen by the staff at the time. Nominations will be conducted over 2 days from the announcement of elections. Members are free to nominate themselves or decline nominations from another member, a valid candidate must have accepted their nominations. Once the staff have compiled a list of valid candidates, voting will be open for 5 days. Results will be posted and implemented within 2 days of the end of elections.}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/657056927536381954|name=19-013|text=Future Ward/Protectorate members must be able to pass psychological evaluations}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/657057086890442753|name=19-014|text=Breakers need to have consequences for long term usage}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/657057227017945089|name=19-015|text=If a player wants to change/update a character. They should list what changes occurred and how they're different from the original sheet. This is so we don't have to go back and forth for review. Minor thing}} | |||
{{Motion|https://canary.discordapp.com/channels/118981144464195584/491100793164922890/684679140309467139|name=20-001|text=withholding or omitting known information (either by not keeping your public info on the wiki updated, or not using #ashton_news) is a form of metagaming and should be avoided.}} | |||
{{Motion|https://docs.google.com/document/d/1slkIBbIBu9NcgbJBbeBj_94boWRDOKcIHdsBtI0LzFw/edit|name=18-008|time=2018-09-25|text=If your cape gets knocked up, they're sidelined until the kid pops out. C53s can be fertile but all NSFW rules apply.}} | |||
{{Motion|https://docs.google.com/document/d/1slkIBbIBu9NcgbJBbeBj_94boWRDOKcIHdsBtI0LzFw/edit|name=18-009|time=2018-09-25|text=Remove the mandatory pairs rule from Protectorate heroes. The Wards will still pair up.}} | |||
{{Motion|https://docs.google.com/document/d/1slkIBbIBu9NcgbJBbeBj_94boWRDOKcIHdsBtI0LzFw/edit|name=18-010|time=2018-09-25|text=If your cape gets knocked up, they're sidelined until the kid pops out. C53s can be fertile but all NSFW rules apply.}} | |||
{{Motion|https://docs.google.com/document/d/1slkIBbIBu9NcgbJBbeBj_94boWRDOKcIHdsBtI0LzFw/edit|name=18-011|time=2018-09-25|text=Secondary "backstory/lore" approvals running concurrently with balance approvals on characters, just to make sure no blithering fuckwits sneak in something that breaks canon in their backstory.}} | |||
{{Motion|https://docs.google.com/document/d/1slkIBbIBu9NcgbJBbeBj_94boWRDOKcIHdsBtI0LzFw/edit|name=18-012|time=2018-09-25|text=Use the votes of the community rep(s) as tie breakers in votes.}} | |||
{{Motion|https://docs.google.com/document/d/1slkIBbIBu9NcgbJBbeBj_94boWRDOKcIHdsBtI0LzFw/edit|name=18-013|time=2018-09-25|text=Allow the community rep to initiate a vote process to remove staff from office. The vote will be from the sub at large (public ballot to prevent alt accounts and double-voting), and a simple majority will remove the member from office.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-001|time=2018-09-19|text=Allow nickname changes by everyone, with per-user punitive action taken upon abuse. Note: Do try to keep your reddit name in parenthesis, thank you.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-002|time=2018-09-19|text=Prominent community members and staff may be granted a single personal role in their choice of title and color, provided it does not violate other rules in place.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-003|time=2018-09-19|text=No hard caps, but approvers are allowed to consider your cast of characters when approving characters they feel are outside the norm, and take this into account for the approval of that character. Note: This replaces the prior rule limiting the number of case 53 characters a player could have.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-004|time=2018-09-19|text=Allow prioritization for initial characters, especially in the case of new players.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-005|time=2018-09-19|text=Allow a process in which reputable community members are given license to place a temporary hold on a character or lore approval, provided they bring specific grievances about the feasibility of something. Approval staff will discuss the issues with each other, the nitpicker, and the petitioner as needed to resolve the situation, and research as needed. Abuse of this system will be handled as needed.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-006|time=2018-09-19|text=Any 1 person can approve lore, but they have to wait 24h before giving the page the official approval in that time, any other lore person/staff person can 'veto' if they feel there's a big issue then there's a vote within 24h, simple majority.}} | |||
{{Motion|https://docs.google.com/document/d/1w2m1bLMaX7n707NSOp28BumI9DoLT-eTqh1U-dWZNvA/edit|name=18-007|time=2018-09-19|text=All old world lore is to be considered non canon unless reapproved.}} | |||
<!-- insert new motions above this line --> | |||
<!-- {{Motion|LINK TO CHANGELOG MESSAGE|name=MOTION NUMBER IN YY-NNN FORMAT|text=TEXT OF PASSED MOTION}} --> | |||
}} | |||
Revision as of 12:25, 9 March 2020
Our Community Code covers all the edge cases and procedural issues not covered by our main Ground Rules. Most of the rules herein aren't something the average member will need to worry about or ever come across, but some (in particular the rules regarding character limits) come up pretty often.
As with the Ground Rules, if you would like to see a rule added, changed, or amended, talk to the staff, in particular your Community Rep.
(note: this is under construction --keira 💀 11:37, 9 March 2020 (UTC))
References
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
Cite error: <ref> tag defined in <references> has group attribute "" which does not appear in prior text.
<ref> tag defined in <references> has group attribute "" which does not appear in prior text.