User:Nashoid/code

Title 1. Community Conduct

Outside venues

Rule 14 states that behavior outside WormRP can result in bans from this community. Players are expected to avoid the following non-exhaustive list of actions:

• Harassment
• Doxxing
• Espousement of hateful or bigoted beliefs
• Ban evasion
• Hacking

Title 2. Gameplay Conduct

Metagaming by omission

Users are responsible for ensuring their characters' public actions are disclosed via the proper out-of-character channels. This includes updating the proper sections of the Wiki, and using the proper discord channels to notify staff and the public of any relevant changes.

In addition, users are responsible for notifying the @PRT tag for any issues relevant to them. (For example, if a Ward hasn't gone to school for a month, or a villain is robbing the PRT gift shop.)

Roleplaying Pregnant Characters

Unless otherwise approved by the staff, roleplaying any pregnant PCs is forbidden.

Policies for Heroic organizations

Roleplaying as the PRT

Only players with the @PRT tag can roleplay the PRT (Parahuman Response Team). Requests to be added to this group of authorized players can be made by contacting the Setting Team.

Patrols with Wards

Wards are required to patrol in pairs, either with each other or with an adult hero.

Well-being of Protectorate heroes

Protectorate members (including Wards) must be able to pass PRT psychological evaluations.

Team size limits

The Protectorate and Wards are limited to a combined total of twenty (20) members. Additional members may join (or return to active status from NPC) only upon an existing member leaving the roster.

Exceptions may be waivered with unanimous consent of the Lore team and the Protectorate Captain's player.

Title 3. Approvals

Queue prioritization

New players are given priority in the approval queue.

Limits on number of characters

While there is no hard cap on the number of active characters a member may play, approvers can deny additional characters to those with an excessively large roster. Note, however, there are some caps on types of characters, as outlined below:

1. Players may have a maximum of one active Tinker or pseudo-Tinker.
2. Players may have a maximum of one active Trump.
3. Players are allowed a total of two capes collectively from the following categories
   1. Multi-triggers/Cluster-triggers
   2. Meshed-triggers (Case 70), Parallel-triggers (Menja/Fenja-style), or similarly "twinned" capes

General limitations

Low effort or setting-inappropriate characters may be denied.

Breaker limitations

Breakers need to have consequences for long term usage.

Secret approvals

While normally not encouraged by staff, secret approvals (as in, a character or equipment that is not publicly viewable) can be made in certain situations. For example, a GM running an arc may wish to keep their NPCs secret, or a player may have a character whose power is especially vulnerable to unintentional meta-gaming.

In order to have a secret approval done, the author must petition the Administrators, who will go over the character with them in private. A secret approval cannot be made without the approval of both Administrators.

In the event an Administrator wishes to do a secret approval, or another conflict of interest is present, the Community Rep will be asked to choose Approvers as replacements.

Character reworks

Sometimes maintaining a fun atmosphere on the server can require changes be made to a previously-approved character. In this case, if a majority of Approval Team support a rework (with the Community Representative acting as a tiebreaker), a rework will be required if the character is to continue in the setting. A randomly selected member of the pro-rework approvers will spearhead the rework process.

Reworks can be expected to operate similarly to an approval process, with the Approver working with the author to resolve all outstanding issues.

Lore approval process

Lore approvals occur in a similar fashion to Character approvals, however a 24-hour waiting period is in place for other staff to place a hold on the approval process to discuss issues with the submission. After this discussion a vote will take place with the majority answer determining the status of the lore post.

In practice, this period may be significantly less if all Lore Approvers are around to have a quick discussion.

Once edits have been made and the Approver has signed off, the member must submit the edited post to the Wiki if applicable.