Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rule 11 update. #41

Merged
merged 5 commits into from
Feb 2, 2024
Merged

Conversation

ClairionCM
Copy link
Contributor

@ClairionCM ClairionCM commented Jan 25, 2024

This is a draft for some Rule 11 changes. Its here for management to look at for easy comparison and shouldnt be merged yet.

The main changes are:

  • Improves the wording and sentence flow of the malicious compliance description (It was real bad)
  • Removes the mention of Rule 3 in malicious compliance
  • Removes malicious compliance being determined by staff/management (ALL rules are determined by staff/management)
  • Improves survivor synth wording to make sure non USCM synths aren't explicitly bound by ML (Unless otherwise stated in the WL documentation)

  • Removes the double mention of 5 people being required for a mutiny
  • Allows roles that are bound by ML to stay neutral in mutinies, not just synths
  • Changes a mention of "Mutinies" to "Regular Mutinies"
  • Improves wording around surrendering and such and (hopefully) makes it a bit more clear
  • Makes it more clear that the examples of mutiny reasons are examples

  • COMPLETELY REWRITES evacuation mutinies
  • Adds a description to evacuation mutinies
  • Removes the distinction between groundside evacuation mutinies and shipside evac mutinies (multiple reasons but mainly to reduce confusion)
  • Improves some wording in the evacuation mutinies section
  • Allows Synths to participate in evacuation mutinies

@ClairionCM ClairionCM marked this pull request as draft January 25, 2024 04:12
@ClairionCM ClairionCM changed the title !!DO NOT MERGE YET!! Draft Rule 11 update. Rule 11 update. Jan 25, 2024
rules.md Outdated Show resolved Hide resolved
rules.md Outdated
Comment on lines 474 to 475
- Malicious Compliance is using IC Military Law to impose excessive punishments, make an arrest on a technicality of someone non-disruptive who is acting in good faith or causing intentional delays in the jailing and appealing process.
- Malicious Compliance does not apply where IC or OOC provocation is present. (For example: following and taunting/threatening a player, engaging in mundane but disruptive actions and continuing when asked or told to stop, etc)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OOC provocation isn't explained in this, and may be misinterpreted.

ClairionCM and others added 3 commits February 1, 2024 16:51
Co-authored-by: forest2001 <41653574+realforest2001@users.noreply.github.com>
@ClairionCM ClairionCM marked this pull request as ready for review February 2, 2024 20:03
@realforest2001 realforest2001 merged commit 1c7162f into cmss13-devs:main Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants