Change to Binding Genre Document section
The following change to the bylaws is proposed. The reason being that there are many pc's who hold positions that should be known by a large section of characters currently in play. Much of this information has been left out of tribal, clan, and other relevant packets, or has been outdated and not updated. This prop would allow that PC specific information to be updated as needed, to keep the genre documents current, without forcing the document to go vote.
While this may not play a major role in the vampire genre, in the changing breeds genre, tribal positions and regional positions are commonly known, either by the tribe in question or the nation as a whole depending on the position. Also, in the Garou Nation, much of the pertinent information about these PC's can change, such as advancing in rank, deed names and titles. Also, with PC death or successful challenge for these positions, those holding them may change completely.
This prop would allow for more of that important information to be placed in future genre documents, with the understanding that it could easily be updated to remain current, so long as it was only PC specific information that was being changed.
I understand that this could be handled as a line item change to the existing documents, however, as has been seen in the recent past, these small changes will often be objected to, in an attempt to force the whole document to vote in hopes of overturning prior changes that some members of council may have issue with...
This prop, if passed, should work to streamline and keep up to date the PC specific information that is in current and future genre packets and other documents, and hopefully include more PC specific information in the future to help solidify the games as a whole as they begin to have easy access to PC relevant information, even if it is from half a world away.
CM Chicago New Moon Rising
iii. Genre Coordinators must pass before Council any plot, enforced policy,
R&U named characters, or 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.
1. If no opposition is voiced during the week of discussion, the proposal
is considered passed and enforceable. Once passed these are
considered binding to all chronicles and a chronicles refusal to
adhere is grounds for OWBN disciplinary measures. Opposition must
be in regards to the content of the proposal and must give those
reasons why the objection is voiced. This is to allow Coordinator's
the opportunity to respond and/or make changes/remove the
proposal and its contents.
i. exception to above - Player Character (PC) specific information, such as but not limited to PC's holding regional positions or PC's important enough to have been included in genre documents (ie tribal packets, clan packets, status packets ect.) may be updated by notification to council, should the PC specific information change during the duration that the document is current. Adding or removing player characters and their respective information from genre documents is expressly NOT covered by this clause, and should be handled through the normal council approval processes.
Seconded by Susanville