The Elsir Project
Role of the Game Engineer
The Game Engineer is competent in the rules of the game and how to apply them in situations. The Game Engineer has the following duties:
1) Knows the Mechanics of the Game: The engineer knows the way skills, powers, key words, key terms, and other aspect of the game works.
2) Rules Encyclopedia: The Game Engineer is the designated source of rules. He is not a Rules Lawyer; he does not argue for and against rule or an interrupter of RAW (Rules as Written)v RAI (Rules as Intended). Instead, he only provides the information, even if he has to look them up for clarification. The job of interpretation is for the Referee.
3) Sets Challenges level: He sets the DC on objects, ability checks, set based on the narrative, object characteristics or average class level (for example, a heavy door has DC 20 to bust open). Calculates the level in a combat or skill challenge encounter. For example, calculates the average party level and states how many XP of foes can be in the fight.
4) Knows how combat works: Knowing the mechanics of the game does not necessarily imply that one knows how combat works. The Engineer is familiar with all aspects of combat and how actions are divided in a turn.
5) Knows how Skill Challenges work: Knows how to conduct a skill challenge, sets DC based on level and records successes and failures.
6) Provides application of rules for situations not covered in the rules: While the Game Engineer does not interpret existing rules, he is charge of orchestrating application of rules to different situations not covered in the rule. For example, a player crouches behind a chair, and the Game Engineer deems that he now has superior cover (ie. +5) rather than partial cover (i.e. +2). Or player wants to hunker down to resist the force of the wind blowing him and the Game Engineer determines that it is like a total defense action, which uses the players standard action.
7) Not responsible for Players lack of Rules Knowledge: It is not the responsibility for the Game Engineer to know how a players powers work, only how the mechanics work. It is a players responsibility to know how his character’s powers work. A players should only build a character he understands.
8) Power to Reject a Character: The Game Engineer who suspects a character is not mechanically sound (i.e. not put together correctly, calculating bonus wrong, having feats or powers that do not meet prerequisites, etc.) may decide to reject a character. When he rejects a character, the group votes on whether to allow the character to be used in the session. Because of the nature of the Game, the Game Engineer may make the rejection at anytime (i.e. before, during or after). The Chairperson takes the vote on the character with the Referee ruling on any ties.