Event Participant Rules - Adex-8x/mmr-patches GitHub Wiki

Most standard MysteryMail shenanigans apply!

  • A scene may have more than one participant registered for it, but no participant may register for more than one scene.
  • All participants of a given scene cannot edit scenes not assigned to them; participants must edit their assigned scene at minimum for their submission to be accepted. No unrelated files in the ROM's SCRIPT/ directory may be added, modified, or deleted. For example:
    • Participants who register for Scene 4 may not edit any file in the SCRIPT/ directory aside from SCRIPT/MYSTERY/04.ssa and SCRIPT/MYSTERY/04.ssb.
    • No participant may edit SCRIPT/COMMON/ehlo.ssb or SCRIPT/COMMON/unionall.ssb under any circumstances (though anyone may freely view them).
  • Prior to the event's final patch release, the only discussion of the MMR ROM's contents may take place:
    • Within the #scene-discussion channel visible during each participant's turn.
    • With an event organizer in private.
  • No participant-written code (this includes scripting opcodes) may make an attempt to exit Ground Mode. For example, participants may not enter:
    • The Top Menu
    • Dungeon Mode
  • No participant-written code may intentionally cause a softlock or a crash.
  • No NSFW material is permitted whatsoever.

Given that MysteryMail Rehearsal is a test event, there are two important rules that do not apply to it, compared to MysteryMail 5 - Backwards Chaos:

  • The MM5-specific rule "References (including characters and plot points) to MM1-MM4 are strictly prohibited" does NOT apply to MMR!
    • As a consequence of this rule's removal, however, MMR is not canon to MysteryMail as a whole.
    • Yes, this means you can add Marcus.
  • The standard MM rule "No going completely off-topic; your scene must make an attempt to continue the prior scene" does NOT apply to MMR!
    • In short, anything goes! You can have a scene that completely abandons everything the prior scene sets up.

Finally, this event's main purpose is to test Decoy, a Discord bot that will investigate submitted patches. Decoy will automatically reject certain changes made to the MMR ROM; please see the Patch Submission section of Decoy's Overview page for an extensive list.