From Wikipedia of the Dark Jedi Brotherhood, an online Star Wars Club
These are the updated rules for the Antei Combat Centre as of February 2012.
ACC 'Regular' Battles
- Standard posting time limit for battles is 72 hours in the Combat Centre Hall and 336 hours in the Classic Hall unless otherwise stated by ACC staff. Other time limits must be stated in the comments and be reasonable.
- The updating of character sheets 'during' a battle is not prohibited, however:
- If a Character sheet is changed, the former stats will be used, i.e. the stats used when the battle was opened. Any attempt to utilise the new stats will be ignored/penalized, depending on severity.
- The Staff will approach these situations on a case-by-case basis.
- A 'regular' battle is defined as an ACC battle which takes place in the Combat Centre Hall, and thus only has one post and a deathpost required from each participant.
- The 'Classic' Hall is used for longer battles (more than a post and a deathpost each), and as such follows the traditional 336 hour time-out limit.
- Regular rules apply with regards to realism, writing and posting times.
- To participate, all combatants must hold at least one point in Piloting skills and the scale represents your ability to respond, how well your tricks go and your general knowledge of how a ship works.
- To end the battle, one pilot must be incapacitated to the point they cannot continue, however this does not mean that there has to be a death to end it. The ship does not have to be destroyed, nor does the pilot have to be dead, but there must be a clear victor.
- All requests are to be sent to opponents and firstname.lastname@example.org via email.
- Any requests sent to just email@example.com or to individual judges will be ignored.
- All requests must state a time for their extension. Any without a given number or with an extension longer than that of the post limit (i.e. 72 hours for the Combat Centre, 336 for the Classic Hall), will be ignored.
- All battles that do not have one post from each combatant will be deleted and will therefore not count on the CS.
- Any that pass this amount, will count towards the win/loss record.
- Any disagreements with any judgements made by the Staff must be emailed to the CM, Senior Operators, the Judge and your opponent. Leaving any of these out will effect how the disagreement is handled.
- There is to be no harassment on IRC towards the Staff about their judgements. Harassing any Staff will be taken seriously and individuals may find their CS deleted without warning, even if it is not a combatant directly involved with the judgement, then the same course of action will still be taken.
- All emails are to be worded as a formal complaint.They are to state why exactly you believe the judgement is incorrect and refer to what rules you think have been misinterpreted.
- There will be an acknowledgement of this from one of the senior members of Staff within 24 hours of the original email.
- There is no time limit on when these will be resolved, each complaint will be taken seriously and investigated thoroughly.
- A Staff member will be appointed by the CM to rejudge the battle if deemed necessary.
- Arguing once a decision has been reached by the Staff will be taken seriously and individuals may see their CSes deleted without warning.
- The official language of the ACC is English. All formal complaints will be made in this.
- All posts are to be written in English, the only exceptions are for known Star Wars languages.
- Candidates must qualify in the Genesis Combine before they are allowed to participate in the ACC.
- Candidates can train as often as they like prior to qualification.
- Candidates will not have more than one battle open at one time in the Genesis Combine.
- All matches will be judged as qualification unless training is stated when sending a challenge.
- Training battles can be judged at the request of the combatants but the Staff must be emailed, with a link to the battle for the request to be followed through.
- The deathpost is the combatant’s last post of a battle - each participant gets a chance to post one in each match they participate in.
- The idea of a deathpost is to end the battle, whether it be by the death of an opponent or oneself or both, unconsciousness, surrender or any other method. Regardless of the method used, however, the battle must be unambiguously finished i.e. it would make no more sense for any other ACC post to realistically follow this one.
- No two deathposts should be the same. Each deathpost is a different ending to the battle.
- No combatant may edit a post to correct any mistakes nor request this of any other participant or Staff member.
- No combatant may copy and paste (or re-use) a post from another battle (regardless if it is their own or someone else’s).
- Basic elements such as phrases of speech, fighting patterns, terminology etc. which can be considered part of a character’s trademark are allowed.
- Each post should hold an originality of its own.
- Exact copies of other posts (even if found after the judgement) will be docked.
Editing of Posts
- No staff member may edit any posts made, either by themselves or someone else.
- Any Staff member found guilty of this will be removed from the Staff.
- Throwing weapons/shurikens are capped at 10. If any combatant requests more than these, then it will be automatically lowered.
- The skill level indicates accuracy with each weapon.
- To be effectively used in battle, 3 points would be required in that weapons slot.
- Grenades/Explosives are capped at 5 of any kind.
- 1 point in throwing weapons/shurikens are required before these can be allowed into battle.
Dual Weapon Allowances
- Must fulfill the requirements listed on the ACC Weapon Guide to dual wield with any weapon.
- No two-handed weapon may be dual-wielded at any time.
- Any lightsaber form except Form 0 (Banlanth) may be used to dual wield.
- Must have strong and off-hand filled sufficiently on the CS.
- Annotations must be used. Missing them out will incur a penalty. See the compendium for further details.
- Force Powers that are listed on the relevant CS are the only ones that may be used in battle.
- Force ability should resemble that of the Force related stats on the CS through the writing of the combatant.
Time Out and Withdrawal
Time Out; a battle 'timed out' is when a combatant has failed to post within the specific post time requirements of a battle
Draw; a battle is 'drawn' when a combatant voluntarily withdraws from a battle
- The official time keeping is the time stamp affixed to the battle stating the time and date of the last post.
- Timing out a battle is a manual operation. It is the responsibility of the person next to post to arrange an extension if it is needed.
- If an opponent posts after a battle time limit, then their opponent may request the win by default by emailing firstname.lastname@example.org with their request.
- Draws are manually accomplished by combatants under the ‘my battles’ section.
- Any battles with no posts or less than one post per combatant are automatically deleted and therefore do not count towards the win/loss ratio.
- Any battles with more than one post per combatant count towards the win/loss ratio, with the loss going to the combatant who failed to post.
- Training/Qualification battles do not count towards the win/loss ratio.
- Any participant or staff member caught cheating will be disciplined.
- Any participant or staff member caught ‘padding’ someone’s win/loss ratio will face expulsion or suspension from the ACC.
- Arguing with a staff member’s decision may be cause for disqualification and/or dismissal.
- Writing in a way to bad-mouth your opponent with RL intentions will be cause for disqualification.
- Failure to keep to all of the ACC rules, especially for hosted events, will be cause for disqualification.
- Out of Character (OOC) comments are not acceptable in any posts except the battle introduction which will be made by staff. If the participants wish to inform their opponent and the ACC staff of something pertaining to the match, please do so by email.
- Explicit sexual references may be cause for disqualification or editing by the staff.
Disqualification Requests (Official Complaint)
The following are the procedures to follow if you are involved in a battle and feel that your opponent has breached a standard of the ACC. This can be anything that would cause the opponent to be disqualified, either indicated in the Rules or the Compendium, to wit; you are seeking closure of the battle and the win by default.
- All official complaints are to be emailed to the Voice, the CM, Senior Operators and CC’ed to your opponent. You must include a link to the battle, your ID line, your opponent’s ID line, the specific item which you believe has broken the rules, what rule(s) has/have been broken, and the action you want taken.
- You must file this complaint before you post again. Continuing the battle means that you are willing to participate and will have an effect on any complaints raised.
- If a complaint is raised during a competition with a specific time-limit, this time limit may be waived according to when the official complaint was received. However, it is the responsibility of the combatant to ensure that they raise the complaint in a timely manner.
- Your opponent will have a 24 hour time period in which to explain themselves and their email must be sent to all listed in the original complaint email. "I did not know" is not an acceptable excuse if the combatant in question is CL:1 or above, or has taken the ACC basics course.
- You may request disqualification of your opponent.
- A decision will be reached by the Staff as quickly as possible. If the complaint is decided to be correct, then the battle will be closed and the win will go to the opponent who was not disqualified. Otherwise, the battle will continue as normal.
Doing any of the items below will result in an automatic disqualification.
- Either combatant using a weapon that was not listed in the introduction.
- 'Self-promoting' during the battle (writing a character who is promoted in rank during the battle). Each combatant remains the same rank throughout the battle as listed in the introduction.
- A deathpost failing to end the battle.
- Timing out without requesting an extension.
- Ending the battle (usually by the killing of one combatant) before the deathpost.
- Writing in such a manner that realistically prevents their opponent from continuing. Example: injuring your opponent severely before the deathpost.
- Ignoring damage, injuries, CS stats, Force use limits, Character attributes and/or traits to the point of severely hindering the battle’s realism.
- Version 1.0 released 1st February 2012.
- Version 1.1 released 16th May 2012.