Amendment to Coordinator Bylaws 3.C.ii: Clan Coordinators and Disciplines

Status message

Displaying output for plurality voting

Open Votes

Proposal Type: Bylaw Revision
Opened: 07-Nov-2008 12:00AM EST
Closing: 06-Nov-2008 1:00AM EST


-----Inline Attachment Follows-----
I propose the following amendment to Coordinator Bylaw 3.C.ii
This proposal was updated to close the loophole wherein GNC could be misinterpreted, as well as imposing a time limitation upon this Coordinator Power so as to prevent subsequent Coordinators (in most cases) from reversing the decision of a previous Coordinator in their genre to not kill the character.
You will note, to allay some confusion, that the placing of this Bylaw was intentional so that it cannot be one of the powers that are extended to a Subcoord. Only the actual Coordinator may exercise this power.

Current Bylaw

ii) To this end, Genre Coordinators have the following powers:
(1) They may create and portray, or delegate the portrayal of, NPCs as appropriate to their
position.
(a) Delegated NPCs, however briefly portrayed, must be included in reports to
Council outlined in the Administrative Bylaws, Section 8.D.iv.
(b) Council may remove any of these NPCs with a majority vote, at which time the
Coordinator will be permitted to script a suitable IC disappearance.
(c) Delegated NPCs requested by STs for use in a particular chronicle are primarily
subject to the authority of those STs but may be removed at any time by the Coordinator.
(d) Coordinator NPCs cannot be used in any Chronicle without the permission of the
Coordinator, his/her delegate, and the local STs.
(e) Coordinator NPCs become subject to local ST authority when they appear in
person in a chronicle, but the Coordinator or his or her delegate shall remain free to refuse
to take any action if it introduces a vital inconsistency of character or a breach in global
genre in the Coordinator or delegate's opinion.
(i) If STs feel they require an action, which the Coordinator has refused,
they may appeal the matter to Council, whose decision shall be final.
(ii) If the Coordinator feels the St(s) of a chronicle have tampered with, or
hampered, the actions of a Coordinator office NPC in such a way that prevents the
Coordinator from enforcing their area of Genre, they may address Council for official
Disciplinary action to be taken against said ST(s) or the Chronicle as a whole.
(f) Coordinator NPCs are subject to Administrative Bylaws Section 1.D constraint
except where otherwise noted in the bylaws.
(g) Coordinator NPCs that fall under an R&U category must be passed as normally
for that category through Council.
(2) Cast a tie-breaking vote on R&U characters they coordinate.
(3) Genre Coordinators may collect information on clan/sect/species activities (or in the case
of the Justicar Coordinators, on matters which have been brought IC to the Justicar's attention) from
the STs or other Coordinators, who shall not misrepresent such information.
(a) Failure to provide necessary information to a Coordinator or intentional
misrepresentation of information shall be brought before Council and considered
appropriate grounds for punitive measures.
(4) They may request permission of the appropriate STs to take any actions directly through
clan NPCs towards PCs.
(a) The appropriate STs shall be deemed to be the STs with OWBN jurisdiction over
the PC at the time and chronicle at which the action is to occur.
(b) If the action is foreseeable in advance, permission should also be sought from
the PC's home chronicle STs for any direct interaction via NPCs.
(i) Permission is not required for indirect interaction (wherein the words,
requests, desires, etc. of NPCs are carried to PCs by another PC), only for direct
interaction (wherein a PC personally interacts with, or is affected personally by,
NPCs without the intermediary of other PCs).
(c) If permission is granted, they may take those actions.
(d) If permission is not granted, the Coordinator may take their case before Council.
Council's rulings will be binding to the Coordinator and the chronicle(s) in question.
(e) If Head Storytellers make agreements with Coordinators concerning PCs, those
agreements shall be binding on both the Coordinator and the chronicle, regardless
of who holds the Coordinator position or the ST positions (though agreements may
be altered if both STs and Coordinators agree).
(f) Failure to keep such agreements shall be brought before Council and considered
appropriate grounds for punitive measures.
(5) Advise Coordinators and STs on ways to leverage R&U related backgrounds and
plotlines on a global level, if desired.
(a) For example: in the Midwest, it's quite possible that various PCs in Kenosha,
Milwaukee and Green Bay all have a 5-pt. Mentor who is a Samedi. Instead of having 3-5
7th generation Samedi, it would make sense for the various Mentors to be combined into a
single NPC, and used as a plot device at ST discretion.
(6) They may delegate any of the above powers to one or more Sub-Coordinators, who
they will hold responsibility over.
(a) They may remove these Sub-Coordinators at will, and Council may remove
these Sub-Coordinators with a majority vote.
(b) Coordinators are responsible for all disputed issues that are brought before

Amended Bylaw

ii) To this end, Genre Coordinators have the following powers:
(1) They may create and portray, or delegate the portrayal of, NPCs as appropriate to their
position.
(a) Delegated NPCs, however briefly portrayed, must be included in reports to
Council outlined in the Administrative Bylaws, Section 8.D.iv.
(b) Council may remove any of these NPCs with a majority vote, at which time the
Coordinator will be permitted to script a suitable IC disappearance.
(c) Delegated NPCs requested by STs for use in a particular chronicle are primarily
subject to the authority of those STs but may be removed at any time by the Coordinator.
(d) Coordinator NPCs cannot be used in any Chronicle without the permission of the
Coordinator, his/her delegate, and the local STs.
(e) Coordinator NPCs become subject to local ST authority when they appear in
person in a chronicle, but the Coordinator or his or her delegate shall remain free to refuse
to take any action if it introduces a vital inconsistency of character or a breach in global
genre in the Coordinator or delegate's opinion.
(i) If STs feel they require an action, which the Coordinator has refused,
they may appeal the matter to Council, whose decision shall be final.
(ii) If the Coordinator feels the St(s) of a chronicle have tampered with, or
hampered, the actions of a Coordinator office NPC in such a way that prevents the
Coordinator from enforcing their area of Genre, they may address Council for official
Disciplinary action to be taken against said ST(s) or the Chronicle as a whole.
(f) Coordinator NPCs are subject to Administrative Bylaws Section 1.D constraint
except where otherwise noted in the bylaws.
(g) Coordinator NPCs that fall under an R&U category must be passed as normally
for that category through Council.
(2) Cast a tie-breaking vote on R&U characters they coordinate.
(3) Genre Coordinators may collect information on clan/sect/species activities (or in the case
of the Justicar Coordinators, on matters which have been brought IC to the Justicar's attention) from
the STs or other Coordinators, who shall not misrepresent such information.
(a) Failure to provide necessary information to a Coordinator or intentional
misrepresentation of information shall be brought before Council and considered
appropriate grounds for punitive measures.
(4) They may request permission of the appropriate STs to take any actions directly through
clan NPCs towards PCs.
(a) The appropriate STs shall be deemed to be the STs with OWBN jurisdiction over
the PC at the time and chronicle at which the action is to occur.
(b) If the action is foreseeable in advance, permission should also be sought from
the PC's home chronicle STs for any direct interaction via NPCs.
(i) Permission is not required for indirect interaction (wherein the words,
requests, desires, etc. of NPCs are carried to PCs by another PC), only for direct
interaction (wherein a PC personally interacts with, or is affected personally by,
NPCs without the intermediary of other PCs).
(c) If permission is granted, they may take those actions.
(d) If permission is not granted, the Coordinator may take their case before Council.
Council's rulings will be binding to the Coordinator and the chronicle(s) in question.
(e) If Head Storytellers make agreements with Coordinators concerning PCs, those
agreements shall be binding on both the Coordinator and the chronicle, regardless
of who holds the Coordinator position or the ST positions (though agreements may
be altered if both STs and Coordinators agree).
(f) Failure to keep such agreements shall be brought before Council and considered
appropriate grounds for punitive measures.
(5) Advise Coordinators and STs on ways to leverage R&U related backgrounds and
plotlines on a global level, if desired.
(a) For example: in the Midwest, it's quite possible that various PCs in Kenosha,
Milwaukee and Green Bay all have a 5-pt. Mentor who is a Samedi. Instead of having 3-5
7th generation Samedi, it would make sense for the various Mentors to be combined into a
single NPC, and used as a plot device at ST discretion.
(6) They may delegate any of the above powers to one or more Sub-Coordinators, who
they will hold responsibility over.
(a) They may remove these Sub-Coordinators at will, and Council may remove
these Sub-Coordinators with a majority vote.
(b) Coordinators are responsible for all disputed issues that are brought before
(7)Coordinators shall have the power to administratively murder any player-character or non-player-character found, in-character, to have a discipline outside of being a member of the clan/sect/group/faction in which it would be considered "legal" for them to have it. Each Coordinator shall have oversight of the disciplines listed next to their respective clans below.
Should a PC or NPC be reported by a player-character, in-character, to a Coordinator-level NPC about possessing said power, the Coordinator must contact the Storyteller staff of the player who reported the discipline and the player who possesses the discipline, as well as a member of the Executive Team. If the Coordinator, the relevant Storytellers, and the Executive Team member all agree that the in-character knowledge exists, then the Coordinator may administratively murder the PC or NPC in possession of the discipline in question. Such a murder is considered final and the character may not be portrayed again without first receiving a Resurrection vote on Council.
Once it is verfied by the Coord, the STs involved, and a member of the Executive Team that the knowledge of the discpline was passed to a Coord NPC in-character, the Coordinator must exercise this right to murder the PC or NPC within 3 months. Once that time expires, if the PC or NPC still lives, the same Coordinator office cannot exercise this power again on that character without finding in-character evidence of a new discipline on their list or continued use of the one for which the character was previously brought to their attention for.
ASSAMITE: Quietus, Dur-an-ki, Daimoinon
BRUJAH: Temporis, Obtenebration, Vissicitude, Mytheceria, Valeran, Koldunic Sorcery, Sanguinus
FOLLOWES OF SET: Serpentis, Setite Sorcery, Bardo
GANGREL: Protean, Ambobwe, Ogham, Spiritus, Rune Magic
GIOVANNI: Western Necromancy, Thanatosis, Deimos, Mortis
LASOMBRA: Obtenebration, Mytherceria
MALKAVIAN: Dementation, Obtenebration, Vissicitude, Mytheceria, Valeran, Koldunic Sorcery, Sanguinus
NOSFERATU: Obtenebration, Vissicitude, Mytheceria, Valeran, Koldunic Sorcery, Sanguinus
RAVNOS: Chimerstry
TOREADOR: Melpomineee, Obtenebration, Vissicitude, Mytheceria, Valeran, Koldunic Sorcery, Sanguinus
TREMERE: Hermetic Thautmaturgy, Visceratika, Obeah, Obtenebration, Vissicitude, Mytheceria, Valeran, Koldunic Sorcery, Sanguinus
TZIMISCE: Vissicitude, Koldunic Sorcery, Sanguinus
VENTRUE: Obtenebration, Vissicitude, Mytheceria, Valeran, Koldunic Sorcery, Sanguinus

--
Brad Klinger
HST, Crusade of Ashes

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