[PROPOSAL][AMENDED] Consolidation/Cleanup of Character Resurrection Bylaws

Open Votes

Proposal Type: Bylaw Revision
Opened: 29-Oct-2015 11:55PM EDT
Closing: 05-Nov-2015 11:55PM EST


SUMMARY
The Bylaws concerning Character Resurrection are currently split between the Character Bylaws (older text) and the R&U Bylaws (the appropriate governing rarity for all R&U). Tampa proposes consolidating the two so that all of the definitions governing Character Resurrection are in one place, and clear. 
 
This proposal has been revised based on all the feedback, thanks everyone! Also, a section was added to specify that Coord-propped rezz's are done so as part of a Coord's powers and as such, must go to Council as an Auto-pass prop. That should sufficiently close the loophole issue that so many CMs raised.
 
This proposal requires a Second in order to go to vote (which it got from Los Lagos).
 
Quite a bit of text was simply copy/pasted to the relevant location in the R&U Bylaws. The RED AND BOLDED text (in the "To" section) below is either new, or significantly altered. The black text is current/existing.
 
= FROM =
 
R&U BYLAWS
3.F. RARE: Includes characters of small groups and bloodlines. Characters of a power level where free inter-game interaction could become a concern. Characters of types considered fringe to a main genre. PC: Simple Majority Vote; NPC: Notification to Coordinator
 

i. Character Resurrection

1. Reference Character Regulation Bylaw, Section 6.B, for the specific administrative process of this rare and unique event.
 
CHARACTER BYLAWS
3.B.i.4. Dead - The character has been killed or otherwise destroyed and is no longer eligible to be played without a Character Resurrection (Section 6.B.)
 
6.B. Character Resurrection

i. Definition and Process

1. The resurrection of a character is considered a Rare and Unique event and as such must be approved by Council.

2. Resurrections are defined as circumstances where plot is written from the point at which a scene is left off and the forward events are scripted to allow the character to return to life after they went through something that had caused them to reach final death or to become unplayable.

3. If there is a dispute on whether a situation is a resurrection or not, the Head Coordinator shall arbitrate although their decision may be appealed to the Council.

 

ii. Rewriting the scene

1. A vote is not required to return a character to play by re-writing the death scene as long as:
a. The same HST is in continuous charge of the character's chronicle.
b. Less than 6 months since the death have passed.
c. After that time, or if there has been a change of HST, then the STs must bring it to Council as a resurrection.

 

2. If a character dies in their own home chronicle, or the visiting chronicle has granted the home chronicle full license to go back and change the scene, the scene is re-written by the Storytellers.

a. If a character dies while visiting another chronicle and the death is contested the characters home chronicle must contest the scene with the Storytellers who had jurisdiction at time of death in order to make arrangements with them to rewrite the scene.
I. If the scene is rewritten as per the agreement of both chronicles, then a vote is not needed because a resurrection did not occur.
II. The request to contest a character death can be initiated anywhere from the night/scene in question to 6 months later.
III. A mediator may be requested at any point during the negotiations.

 

3. If the character's death is not resolved to the satisfaction of all parties within 6 months of the initial protest then the matter should be taken to the Head Coordinator. The Head Coordinator shall process and propose the Resurrection and/or scene rewrite and give his or her input into the matter.

 
= TO =
 
R&U BYLAWS
3.F. RARE: Includes characters of small groups and bloodlines. Characters of a power level where free inter-game interaction could become a concern. Characters of types considered fringe to a main genre. PC: Simple Majority Vote; NPC: Notification to Coordinator
 
i. Character Resurrection
1. Resurrections are defined as circumstances where plot is written from the point at which a scene is left off and the forward events are scripted to allow the character to return to life after they went through something that had caused them to reach final death or to become unplayable.
 
a. Only under all of the following conditions are Resurrections NOT considered an R&U event:
i. The same HST is in continuous charge of the character's Chronicle
ii. Less than 6 months has passed since the out-of-character date of the death scene
iii. The death occurred in the character's home-Chronicle; or, if the character death occurred in a Chronicle other than the character's home-Chronicle, the visiting Chronicle has granted permission to the home-Chronicle to re-write or change the death scene
 

2. If there is a dispute whether a situation is a resurrection or not, the Head Coordinator shall arbitrate

a. The parties may appeal any decision to the OWbN Council with a vote, as normal
 
3. Once defined as Dead, a character may not be changed from PC to NPC in order to lower the restriction-level of its Resurrection
 

4. Coordinators proposing NPC character resurrections must do so as part of their Coordinator duties, specified in the Coordinator Bylaws, Section 3.C.iii.

 

 
CHARACTER BYLAWS
3.B.i.4. Dead - The character has been killed or otherwise destroyed and is no longer eligible to be played without a Character Resurrection (R&U Bylaws, Section 3.F.i.)
 
6.B. Character Resurrection

i. A Dead character returning to life (through plot-events, the re-writing of a death scene, or any other method where the Dead character returns to game-play) may be considered a Rare and Unique event; see the R&U Bylaws, Section 3.F.i.

 
COORDINATOR BYLAWS
3.C.iii. Genre Coordinators must pass before Council any plot, R&U bylaw revision, R&U named characters, Coordinator-NPC Character Resurrections, territory requests, in character enforced policy, or in character binding edict they wish to use which they can reasonably expect to affect multiple chronicles and these proposals need not be seconded, but go immediately into discussion.
 
Thank you,
 
- Brian Orlando

 

  CM & HST: Tampa Bay by Night

File / Document: No file attachments for this vote.
Ballot Options
Yes
No
Abstain