Commanders' Council
Commander's Council is a group of individuals who have been chosen
to play Commander Characters. The players of these characters are
automatically given a position on the Commander's Council.
Commanders serve on the council until the time when their
character graduates/ices. These individuals are responsible for
discussion and implementation of new rules that effect commanders
in particular. They are also expected to give advice on policies
that may affect the armies as a whole. This group is also used to
organize battles and other intra-army events.
Commander characters are usually between the ages of eleven and
thirteen. (ICly) Most people who enter battle school do get command
at one point or another. Unfortunately that is not the case as we
cannot hope to facilitate a commander slot for everyone. Players
who may not be as active have an option of choosing to take a
non-player command. This means you take command of an army that
does not have player characters in it. Others, who are active or
may become active, often wait out the time it takes to be eligable
for an 'active' command. Active command means that you are leading
an army with real player characters in it.
There is no application process for this staff. Please do not ask
to be placed as a commander. Commanders are placed upon need and
upon ability. If you would like to be considered please fill out
your commander availability information via @cmd-set . We
suggest that all characters ages nine or older fill out this
information. It can be edited at any time if needed. You can view
your own commander availability information by typing
@cmd-info YourName .
Commander Expectations
- Connect Time : Barring unforseen circumstances, commanders are expected to connect at least ten hours each week. In the event that a commander cannot meet this minimum, they should contact the admin accordingly.
- Commander Inactivity : Commanders (both player and non-player army) are held under much stricter rules than normal players when it comes to inactivity. If a commander is going to be gone for longer than one week they must notify the administration. A commander who does not connect for two weeks (14 days) without some sort of notice, will be subject to graduation and replacement. The maximum time a commander is alloted (even with notice) before graduation and replacement will be three weeks (21 days) as with other inactives.
- Battles : A commander is expected to arrange at least
one battle every two-three weeks. Battles are the heart of role-play
and they are what many seem to look forward to. If you are having
trouble setting up a battle, let the administration know. Although it
should not be too terribly difficult to set one up. Random battles
are encouraged when there is at least a commander, and four other
players online in two armies.
There will be at least one inactive "@battle" per month (probably around the 1st). Additional @battles may be requested. Opponents are chosen randomly or by plotline need. - Battles & Player-numbers : During random battles a
commander may request that there be even numbers. There will only be
even numbers if it is requested at the time of the random battle.
There must be at least four members of the army (not including
commander) present for a battle to take place.
In a scheduled battle, the default terms are that everyone who shows up will battle. At the time of the scheduling the battle, if either commander would care to change those rules they will work it out amongst themselves. The commanders will agree, before the battle is scheduled, to default terms, even numbers, one-up, or some other acceptable terms. . This will be established when the battle is scheduled, and the commanders will be held to that.
As a way of keeping track of battles and terms, please send a listing of the scheduled battle to *battle (using the standard format). - Absent Commanders : Commanders who schedule battles are expected to be present at the time of the battle. If a commander is not present, the next highest ranked character will be set as the commander and the battle will commense (as long as the minimum number of soldiers can be mustered). Repeated absences from battles may result in loss of a commander slot.
- Bunking : Commanders are expected to update their
bunk listing at least once every three weeks. If there is a
significant change in the roster of an army, they are also expected
to be updated. Remember that NPCs need bunks to. If you are unsure
about how to set up bunks, please refer to
help @bunks. - Inactive Players : A soldier is classified as an 'Inactive Soldier' if they have not connected within three (3) weeks, or twenty-one (21) days. To remove the soldier from your army, please mail *requests with a request for the Elligible Inactive Soldier to be placed in Inactive Army. If they notify you ahead of time that there is a condition, such as parental disciplinary intervention (AKA Grounding) or a planned 'real' life event that will prevent them from connecting long enough to classify the soldier as 'Inactive,' work with the soldier in question to meet their requests, if the expected period of inactivity is within a 'reasonable' amount of time. If not, you may wish to suggest they get a transfer to Flame army until after their leave.
- Role-play : Commanders should make an effort to encourage role-play within their armies. Perhaps have scheduled practices, or make it a requirement that you must RP to participate in battles. In either case, you are expected to get your armies active and interested.
- Non-player Commanders : Non-player commanders are expected to write up at least one *TP for their army each month. If it is something unusual please clear it with a RP staffer. Inactive commanders are also encouraged to go out and play amongst the other armies and commanders.
