Honor Matches, Prisoner of War Matches, Death Matches, Misc. Matches, and any Mass of the fore-mentioned are allowed in any event.
2.
Assassination Attempts, Capture Attempts, and Thievery Attempts are allowed in events unless the event flier states otherwise.
3.
Enhancers may be allowed in an event at the discretion of the host(s) but follow the same rules on breakage as in any other combat situation.
4.
NC’s may not take part in any match that requires violence against the opponent. [ For this reason, any match that follows the Honor Match structure but does not require harming another must be labeled a Misc. Match. ]
5.
Host(s) may decide whether or not to allow:
A.
Split Attacks are default. If host does not want them to be in use, it must be stated on the flier.
B.
Use of Healers/Battle or Support Mages [ Healers and Mages must be registered ]
C.
Hosts may decide whether or not those killed or captured, as a result of Event Matches, may proctor for full CP Credit.
6.
Matches are to be turned into the Host(s) event team, the event Ministry and all participants of said match. Contested matches should be turned into the Trinity as well.
1.
Submissions will be reviewed and approved on a first come, first serve basis.
A.
To schedule an event date the Events Calendar should be referenced with 5 day buffer between events.
B.
Reservations may be taken three months in advance but flyers must be submitted two weeks prior to reserved date or risk forfeiting reservation date.
2.
Every Event must have a unique name following the template: Guild Acronym, Number Event Hosted (in three digits), Name of Event. (i.e. If the US Navy were hosting their fifth event called “Drown the Fish” it would look like this: USN presents 005 Drown the Fish)
3.
Submitted event fliers should be sent to the Host(s) event team, the Event Ministry and the Trinity.
A.
All submitted events must be original to the author.
--
All events are considered copyright of the author(s) until the start date of said event. After which the rights of the event transfers to the entity host, and there-fore, the GC.
a.
The GC may do whatever he/she wishes with the event once rights transfer, including offering rights back to the Author(s).
b.
An agreement may be made, in writing, between the GC and the Author(s) before the submission of the event stating that rights never transfer away from the Author(s). This is to be between the GC and Author(s) only and is considered legally binding.
--
The theme and matches within the event may be used by others provided the event is not directly copied. Plagiarized events will be turned down.
B.
Submitted event fliers should be complete and ready to be sent out. Complete fliers include (not limited to):
--
Event Name.
a.
Intended start and end dates of registration for the event.
b.
Rules of the event
c.
Intended start and end dates of registration for the event.
d.
Registration application
Intended starte date and end date of the event
e.
Matches/Match Descriptions
f.
CP awarded in each match to participants
g.
Rooms for Event use
h.
Mailstring for event team (include event ministry for match submission and contest only)
i.
Proctoring Instructions (headers\subj template) and Template
j.
Any graphics being used
4.
Submissions will be reviewed and corrected or approved by the Event Ministry.
A.
Please allow 48 hours for your Event to be reviewed and responded to. If the Event Ministry sends notice that more time will be needed to review the event, please allow the requested extension.
B.
If an event submission is responded to requesting changes those changes must be made within one week of the time the request is sent. Should the corrections not be made within the given time, the dates held for said event will be re-opened for use in other submissions.
1.
Any match of any type with only a single entity represented will be voided.
A.
All one on one matches must have at least two entities represented, including the proctor.
B.
All Mass Matches must include the presence of three entities including the proctor.
1.
All information stated on the registration form must be consistent with the persons profile.
2.
Registration forms are submitted to the event team only. The event team may request a resubmission of any registration form not properly or completely filled out.
3.
Members may only represent one guild per event.
4.
An Event Roster must be constructed to show all the participants necessary information.
5.
Event Ministry must receive a final participant roster and mailstring before the start of the event.
6.
The host entities are responsible for reviewing matches. This includes (but is not limited to):
A.
Checking for inconsistencies between the particpants stated information and the participants event roster information. [ i.e. An opponent is stated as a d56 on the event roster but states d60 in the match log ]
--
Checking for inconsistencies between the Proctor’s format and the Proctoring instructions on the Event flier. [ i.e. the event proctor instructions call for the Proctor to state room match is taking place in and they don’t ]
--
Checking for basic math or strength use errors. [i.e. A match requires d10 be rolled and a d6 is rolled]
--
Checking for rule errors. [ i.e. Event rules state no weapons and weapons are used ]
--
Checking for round consistency [i.e. Proctor accidentally ends match a round early or skips a round]
7.
It is recommended that if a Proctor submit a match in a faulty manner [ wrong header, missing information, etc. ] that they be given until the end of the event or 48 hours to resubmit (the 48 hour time limit is up to the host. The host may choose to cut it off sooner). If a proctor does not resubmit after being sent a request by the host(s) event team, that proctor may have their CP for that match revoked.
1.
The hosting guild may decide which entities their event is open to (or leave it open to all). There must be a minimum of three separate entities [ other than the hosting guild(s) ] allowed to participate in any given forum event.
2.
Events may run anywhere from 3 to 5 days at the discretion of the hosting guild(s), but may not overlap.
3.
Each entity may submit up to 3 events per year. (Co-hosting is included in this number)
A.
Entities may submit standby events that will take place if there are no scheduled events for a particular month.
4.
Earnings:
A.
Single host entities earn a base 30 CP regardless of event earnings. On top of that they receive 10% of the events total earnings.
B.
Co-host entities earn a base 50 CP each, regardless of event earnings. On top of that they receive 5% of the events total earnings.
5.
Event ministry will only get involved in the rulings of the events in the event that a mandate is broken, a contest is posed, they are asked or it is believed the guilds event team missed something.
6.
Death or Capture obtained during an Event (by means other than contract) cannot bypass the event end date.
7.
Forfeits only count if the match has gone past the first round (one full action from each participant post-init).
8.
If a person is cleared by the host(s) to participate in the event, meaning they are on the event roster, participation may not be denied to them.
9.
Host(s) have seven days after the end date of the event to send Final Tallies to the Event Ministry for approval or risk being fined an amount of 3 cps per day beyond the deadline date (exception may be made for valid reasons). Final tallies include the CP earned by each individual, under which entity and each entity’s total CP for that Event.
10.
Event Ministry will submit the approved final tallies to accounting, but it is the Host(s) responsibility to submit the approved final tallies to the participants and the mailstring offered them by the event ministry.
11.
Questions or complaints regarding an Event or Ruling of a Host must go to the Event Ministry and the Trinity.
