View Full Version: [Article] Standing Orders

Write With Flair > Nonfiction Articles > [Article] Standing Orders



Title: [Article] Standing Orders


Eisel - March 23, 2006 05:05 AM (GMT)
This is another shortie, but I need some more ideas for standing orders. Any of you gamers have some?

A PBeM, by its very nature, takes a very long time to play, and GMs are always looking for a way to speed things up. One way is to use standing orders.

According to Wikipedia, in military usage a standing order is a general order of indefinite duration. It remains in effect until modified or rescinded . . . Standing orders are necessarily general and vague since the exact circumstances for execution occur in the future under unknown conditions. Some examples of military standing orders are to give the alarm in case of fire or disaster, to report all violations of orders, or to be especially watchful at night. Thus a soldier knows generally what to do in many situations.

How does this apply to a PBeM? If a Player gives the GM standing orders for his character, it speeds the PBeM up. For instance, Levin, with a +12 bonus to diplomacy, tells his DM that he wants to talk to any non-threatening encounters. Thus when the GM posts that the group meets an old man in the tavern, he can also post that Levin greets him. Now the GM can begin a conversation with the old man and Levin. Without the standing orders Levin gave at the beginning of the game, this conversation could take 3-4 emails, and over a week.

Players can also give temporary standing orders for specific situations. An example would be combat. The group has encountered four mean minotaurs, and the GM calls for actions. Baeric might reply that he will cast mage armor on himself, then command and fireball on one of the minotaurs - so long as conditions remain the same. Obviously, should another minotaur threaten him or more enemies appear, he would amend these orders, but generally this will reduce the emails back and forth.

Following are some examples of common permanent standing orders (to be given to the GM when the character is created). Obviously, some of them are applicable to certain classes only or certain genres only.

    1. The bard will try to speak to any non-threatening beings met.
    2. The ranger will choose bow as his weapon of choice unless in close combat.
    3. The priest will try to heal any injured members as soon as the scene is secure.
    4. The barbarian will go into Rage when attacked.
    5. The rogue will always check anything for traps before opening (doors, chests, etc)
    6. The paladin will detect evil before picking up any items, or when engaging newcomers in conversation.
    7. The druid will not approve of any nature-destroying actions (cutting down trees for firewood, etc)
    8. The ranger will try communication with non-threatening creatures.
    9. The wizard will always cast mage armor before starting combat.




Hosted for free by InvisionFree