[OWBN-Council] [PROPOSAL] Removal of the Ventrue Lineage Reference Guide

by Jenn Louise

December 12th, 2012

2 comments

Now it's the Assamite Clan's turn. [PROPOSAL] Change to Rare & Unusual Bylaws Section 3.D.1

by Jenn Louise

December 12th, 2012

Per the Coordinator Bylaws 3Ciii. "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" the Assamite Coordinator proposes a change to the R&U Bylaws moving the creation of any new Assamite Player Characters of the Sorcerer Caste from unregulated to Coordinator Approval.

The following changes to the R&U Bylaws will occur:

- The item "Assamite Sorcerers" will be added to 3.D.1.

- The item "Sabbat Assamite Viziers and Sorcerers" shall be changed to "Sabbat Assamite Viziers"

Reasoning:

This has been a long time coming.  It's something that's been bandied about by the Assamite staff for years.  The fact of the matter is that the Sorcerers outnumber the other castes, when per the printed material they are supposed to be rather small in number comparitively, particularly in the Schism when measured against the Viziers.  

The Sorcerer caste was also never intended to compete with the Tremere as the Camarilla's pre-eminent blood magicians.  While they absolutely should present an alternative to having to deal with the treacherous Warlocks, their numbers shouldn't be anywhere close to being able to counter them in most, or even very many, geographical areas.

Additionally the Sorcerers were to take much more of a support role in the clan rather than the front-line replacements for the Warrior caste that they often become in OWBN.  I see too many concepts such as "battle-mage" or "I kill Sabbat", concepts which would be far better served as Warriors, that are instead created as Sorcerers so that the player can do everything a Warrior does but also have magic.  That flies directly in the face of Assamite genre and makes an entire caste relatively pointless.  Concepts such as these tell me that the player doesn't really understand the Sorcerer's role within the clan and probably hasn't put much research into either the genre or Dur-An-Ki.

As Assamite Coordinator I hope to bring the caste closer in line with the numbers they are supposed to represent and to also ensure that all future characters enter play with a clear understanding of the genre as well as the quasi-religious magic that is Dur-An-Ki, something that I rarely see roleplayed.

Against my better judgement, we will ofcourse allow Grandfathering with this proposal.  :-)

-Brad

18 comments

A new Wraith Coordinator has been appointed.

by Jenn Louise

December 12th, 2012

Ladies and Gentlemen,

0 comments

New R&U: Additions to R&U bylaw regarding Nosferatu Coordinator approvals.

by Jenn Louise

December 12th, 2012

This auto-passed.

~ Jenn, CM, KoNY

[PROPOSAL] Additions to R&U bylaw regarding Nosferatu Coordinator Approvals

Pursuant to Coordinator Bylaw 3.C.iii, the Nosferatu Coordinator proposes that the current R&U Listing for Coordinator Approval be amended to include the following items:

Nosferatu Lore 3+ for a non-Nosferatu

SchreckNET Lore of any level for a non-Nosferatu
Warrens Lore of any level for a non-Nosferatu
Animal Magnetism for a non-Nosferatu
Blood Apocrypha for a non-Nosferatu
Feral Imbuing for a non-Nosferatu
These are all items that have been listed in the Nosferatu packet since at least 2009 as Coordinator approval.  When changes were made last year to how such things are handled via the bylaws, these items were not added by the previous Coordinator.  I am now proposing their addition to ensure these Nosferatu related items are regulated properly.  There will be no grandfathering of these items, however, anyone PC who currently has them, should this pass, can speak to me, along with their STs, about retaining the item.  I have no interest in stripping things from a player's sheet if they can show me a reasonable justification.
Two further items that are in the current packet, Mortal Terror and Iron Facade, are not being requested to be added to the Coordinator approval listing in the R&U bylaws, as I do not think they should be Nosferatu only combos.  They are Archon & Templar combos, and nothing in the writeup suggests they should be relegated to Nosferatu only status.  They will be removed from the next revision of the Nosferatu genre packet.

Cthulhu Fhtagn,
-Sooper

Nosferatu Coordinator

0 comments

Open Vote: Code of Conduct Vote for email list moderation.

by Jenn Louise

December 10th, 2012

I'm voting against this P.o.S. This is a B.S. attempt to add moderation methods to our Organization's Bylaws. We do not need to presently make rules in our rules to moderate people who are being assholes: just do it. This doesn't change much of anything and bloats our bylaws.

~ Jenn, CM KoNY

[Proposal] Code of Conduct [Amended]

Per Administrative Bylaw 3.v:

v. Administrative Bylaw Changes

1. Administrative Coordinators may pass before Council any changes to the administrative bylaws, as long as said changes directly affect their position. These proposals need not be seconded, but go immediately into discussion.

a. If no opposition is voiced during the week of discussion, the bylaw is considered passed and enforceable. Once passed these bylaws are considered binding to all chronicles (as with any other bylaw) and a chronicles refusal to adhere to said bylaw 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, Linsey "Echo" Guertin, acting as AHC and on behalf of the Executive Team, propose the following changes and additions to Administrative Bylaw 9, Section B, which currently reads:

B. The section was removed 9/23/08. Reference Coordinator Duties 3.A.vi for the Web Coordinator position.

The changes proposed are as follows, in blue and bolded for ease of reading.

Removed all wording currently in section B. This note was from 2008, and everyone should be clear by now that the Web Coordinator’s duties are located in the description of the position.

 B. Code of Conduct for the Council, Storyteller, and Coordinator List-Servers

1. Please remain considerate, professional, and act with civility towards others.
2. If you are determined to be acting in violation, simply apologize and amend your behavior(s). The Executive Team will determine if you are in violation of the Code of Conduct.
3. If you persist in the behavior(s) after being warned to stop, you will be placed on moderation for up to one week. Moderated posts will be screened by the Executive Team for continued violations before being shared.

                                         a.    Council Members placed on moderation that are attempting to post items related to their duties, such as seconding or objecting to proposals, may have their posts edited to remove any violations to the Code of Conduct before the item is shared with Council.

                                       b.    The Executive Team will not use moderation or the Code of Conduct as a means of silencing debate or discussion related to the official duties of Council Members, Storytellers, or Coordinators.

                                      c.    Should no further violations occur, moderation will end within 24 hours.

4.   In addition to moderation, official disciplinary actions may be proposed  for the Code of Conduct violation, or  for continued violations of the Code of Conduct,  including any occurring during moderation.

Should this proposal pass, I would also ask that it be added to the Unofficial Council packet/guide to council located on the website.

-Echo

AHC

2 comments

Open Vote: Ventrue Lore Restriction modification for Ventrue PCs.

by Jenn Louise

December 10th, 2012

I abstained. I don't know that this really critically pertains to Sabbat PCs as much as it does Cam PCs. If there is a strong objection one way or another, let me know ASAP and I'll change our vote.

~ Jenn, KoNY CM

[PROPOSAL] Changes to the R&U Bylaws for Ventrue Lore

Dear Council,

Ventrue Lore 4 is currently Coord Approval for both Ventrue and non-Ventrue. I would like to change this. So, while the restriction will stay in-place for non-Ventrue, Ventrue characters will be able to purchase level 4 without having to wait on the Coordinator to hear their case.

While I do recognize the need to ensure that the most guarded levels of Lore are restricted, I feel that the Coordinator's office is an unnecessary roadblock for this level of Ventrue Lore, and that Lore at level 4 for Ventrue characters can be effectively managed at a Chronicle-level.
I would also like to take advantage of the new Sub-Section G of the R&U Bylaws which was specifically created in order to Notify the Coordinator whenever an important purchase or in-game event occurred, such as the purchase of Lore at level 4. I feel that, with this notification in place, my team and I can be informed of a Ventrue's purchase of level 4, and be aware that they might be approaching us in the future for that next level.
With this in mind, I propose the following changes to section 3 of the Rare and Unusual Bylaws of One World by Night:
Change the existing Ventrue Lore 4+ restriction in 3.D.1. to "Ventrue Lore 4 for Non-Ventrue "and add an entry for "Ventrue Lore 5+." I would also like to add "Ventrue Lore 4 for Ventrue" to sub-section 3.G.i. A summary of the changes is as follows:

FROM:
3. Guidelines for determining R&U Category
 D. Coordinator Approval

1. PC: Appropriate Coordinator Approval and Logged with Archivist, NPC: Appropriate Coordinator Approval and Logged with Archivist. (Reference Section 5, “Appropriate Coordinators for R&U”)

- Ventrue Lore 4+

TO:
3. Guidelines for determining R&U Category
 D. Coordinator Approval

1. PC: Appropriate Coordinator Approval and Logged with Archivist, NPC: Appropriate Coordinator Approval and Logged with Archivist. (Reference Section 5, “Appropriate Coordinators for R&U”)

- Ventrue Lore 4 for Non-Ventrue

- Ventrue Lore 5+

G. Coordinator Notify

i. PC: Notification to Coordinator and logged with Archivist, NPC: Notification to Coordinator and logged with Archivist.

- Ventrue Lore 4 for Ventrue

Thank you,
- Brian Orlando
  Ventrue Coordinator

3 comments

Closed Vote: Baseline for EXP Costs.

by Jenn Louise

November 30th, 2012

This vote falls into the category of "Duh" and "Things people should already know" but when the books list an EXP cost, that's what it costs. (Example: You can't suddenly decide that an out of clan advanced only costs you 2 exp when it costs 10.) 

It's an example of more crap filling up the Bylaws needlessly due to irresponsible STs that lack the ability to say no. Please, if you ever become an ST, don't be that guy that lets your players do things that make us make Bylaws like this. Thanks.

[Proposal] Baseline of XP Understanding

As CM of Dayton: Dying Embers, I hereby propose the following bylaw be added to Character Regulation Bylaw 2 "Experience Points" to be numbered as Bylaw 2.F:

F. The standard XP costs from Laws of the Night (3rd Edition) and other published Revised/3rd Edition White Wolf books and material with listed MET XP costs (including the Sabbat Guide, Anarch Guide, Stroyteller's Guide, Clanbooks, etc.) are to be considered the baseline for OWBN. Reasonable variations due to house rules or regional preferences (such as rules regarding Influences) are permissible, but must be noted in a game's house rules.

*************************

Reasoning: We have never actually defined what XP means as an organization -- we define the currency and how it can be spent, but never what those transactions should cost. This really does not change anything, but simply defines for the record that games should be following XP costs as defined in our generally accepted rulebooks, and if they differ from that, to explain exactly how. After looking at the organizational rules of groups like ours, it is a common bylaw to include, and one I feel we should emulate.

~Joseph Schuster
CM Dayton: Dying Embers

Panders Playground seconds this.

Mark Cherry
Interim CM for PPG

2 comments

Closed Vote: For those that care, a minor revision to the Alastor Bylaw.

by Jenn Louise

November 30th, 2012

[Proposal] Ventrue Justicar and Alastor Bylaw Change

Per the Alastors section of the Character Bylaws, Lucinde is under the sole control of the Ventrue Coord.  This conflicts with more recent bylaws, and probably should be removed.

Because of this, I Lawrence Jacob Siebert, CM of Always Comes Evening, San Francisco, CA do hereby propose the following:

Change Character Bylaws 14. i from

Alastors

Alastors are a category of Archon, and therefore report to a specific clan. All Alastors shall be under the joint controlled of the Clan Coordinator of the clan they report to and the Camarilla Coordinator. The single exception to this rule is Lucinde, Ventrue Justicar. As such, Lucinde is under the single control of the Ventrue Coordinator. Any other exceptions in the future are subject to a Genre Proposal as detailed in the Coordinators Bylaws section 3.C.iii

to

Alastors are a category of Archon, and therefore report to a specific clan. All Alastors shall be under the joint control of the Clan Coordinator of the clan they report to and the Camarilla Coordinator. Any future exceptions are subject to a Genre Proposal as detailed in the Coordinators Bylaws section 3.C.iii

Check out these blurbs from the relevant Coords!

"I like this."Rojir, Camarilla Coordinator

"Looks good to me, boss!"Brian, Ventrue Coordinator

Jacob Siebert

0 comments

Active Vote: Tremere Characters (PCs and NPCs) to Coordinator Approval

by Jenn Louise

November 30th, 2012

[Proposal] R&U Change: Tremere Characters

Per the Coordinator Bylaws 3Ciii. "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" the TremereCoordinator proposes a change to the R&U Bylaws moving the creation of any new Tremere Player Characters or Non-Player Characters from unregulated to Coordinator Approval.

The following changes to the R&U Bylaws will occur:
- The item "Tremere characters" will be added to 3D1.
I don't propose this change lightly, as myself and my predecessors have avoided this step in the past to minimize the amount of bureaucracy present in our Clan. In the past months, however, the sheer number of problems associated with rampant Tremere alts, unregulated childer creation, NPCs that appear whole-cloth without any history or backstory, and the fact that we are the largest PC group in the organization, has convinced me that this is a necessary step.
ICly, the Council of Seven shall decree that seeking the creation of a new childe shall require the permission of the Pyramid. OOCly, I shall be assigning a subcoordinator to review potential PCs and coordinate with myself and the STs to make approvals a smooth process. 
Obviously grandfathering is assumed in this change. I will be working with the Archivist to create a 30-day census for grandfathered PCs and NPCs. The information required will be PC Name, Character Name,and Chronicle. 

-Alex R.Tremere Coordinator

14 comments

Gangrel Special Elections: Brendan Ammerman

by Jenn Louise

November 27th, 2012

FYI, Brendan Ammerman is running unopposed to fill the slot for Gangrel Coordinator.

[PROPOSAL] 2012 Gangrel Coordinator Special Election
Pursuant to Administrative ByLaw 4.C:Special Elections

Should any Coordinator position become unfilled during a term, a special election must be held.
The Head Coordinator may appoint someone to fill the position until the special election is completed.
The appointee will be treated as an Elected Coordinator, except that the appointee will only serve until the Special Election is complete.
The Head Coordinator will announce the Special Election on the Council, ST, and OWBN-OOC mailing lists and will accept applications for fourteen (14) days.
The vote will then proceed following the bylaws in Administrative Bylaws, Section 4, Subsection B, Other Coordinator Elections.
Should the position become vacant within one (1) month of the Head Coordinator Election, an appointee may serve until elections are complete.
And in Conjunction with Administrative By-Law 4.B., as required above:

Other Coordinator Elections
The Head Coordinator will nominate all other Coordinators.
The Head Coordinator will accept applications for nominations for a minimum of two (2) weeks from the time the application procedure opens, which must be posted to the Council, ST, OWBN-OOC, and mailing lists in addition to the OWbN website.
The Head Coordinator is required to nominate any applicant who has the support of five (5) or more member chronicles of OWBN. They may decline candidates with less support at their discretion.
Each candidate must list prominently on their application from where their support is coming.
Chronicles may support more than one candidate in this manner and they do not have to vote for the candidate(s) they supported.
Current Coordinators may also support individual candidates. This support is a traditional method, and may count towards the five (5) support required, but is not officially required to be counted towards the support required.
Should only one person submit an application for a given position, then the Head Coordinator may nominate that one applicant without a second applicant on the same ballot or extend the time for collecting applications as the Head Coordinator sees fit.
The Head Coordinator may indicate which nominee is preferred.
The Ballot will be presented to Council seven (7) days before the voting period begins for discussion, but no later than March 27th without a ratified proposal granting the Head Coordinator an extension.
The Ballot will be posted on the Council, ST, and OWBN-OOC mailing lists at the beginning of the vote discussion period.
The vote will open on the day after the fourteen (14) day council discussion period, and close at the same time seven (7) days later.
All candidates for Coordinator positions will be put on Council during the fourteen day discussion period, and election week, to defend and explain their platforms. Those not elected shall be removed once the voting period is done.
The nominee carrying the most votes on Council shall become Coordinator.
In case of a tie, the Head Coordinator may either break the tie or hold a run-off election between all tied parties.
For a run-off election, only the candidates who were tied will be on the ballot. The option to reject all candidates will be removed. The option to abstain will remain.
If the election is still tied after the run-off vote, the HC will break the tie.
Coordinators will serve beginning two weeks after the election vote for their election closes, including any run-off election that may have taken place. The current Coordinator will be expected to brief the Coordinator-elect during these two weeks on issues and events relating to the particular Coordinator position being assumed by the Coordinator-elect.
I, Robert Crosby, as Head Coordinator, do hereby nominate the following for the position of Gangrel Coordinator, following the resignation of Chris Klackring - the previous Gangrel Coordinator: Brendan AmmermanReject All CandidatesThis election proposal will be discussed for 14 days, pursuant to regulation, and will open after 14 days on November 23rd 2012, after which point the vote will open and then close on November 30th, 2012. My preferred candidate is Brendan Ammerman, who Exec feels will do a spectacular job.Until two weeks after the election, Mr. Ammerman will remain as Interim Gangrel Coordinator.You can find his application HERE


Current date: November 27, 2012 - 11:52am
Opening date: November 23, 2012 - 12:00am
Closing date: November 30, 2012 - 11:58pm

2 comments