Skip to main content

Illarion Team Work (First Draft)

Illarion is only possible thanks to a team of volunteers who sacrifice their spare time to develop, improve and moderate the game and fill it with life by letting the players tell great stories. This team does only work, if all members of it respect each other and have common vision of the game in mind. Since there are so few of us left, the loss of any team member would probably mean the end of the game.

Any staff member can be member of the following three groups:

  1. Developer: Devs improve the game by implementing new game scripts in LUA, enhancing the client and the server applications of Illarion, adding new items and skills for the players to use and offer new content for players to explore by editing and creating maps with the map editor. Their development vision has a major impact of what the game will become.
  2. Gamemaster: GMs improve the game by filling it with life. In a pen and paper fashion, they develop storylines for the players to play out ingame allowing them to experience much deeper stories and events than the game engine normally allows them to. GMs can impersonate town leaders and NPCs to enable players to directly interact with them. Also GMs enforce the rules.
  3. Community Manager: Community managers currently dont do anything, because there is no one left.

Society members are not automatically members of the Illarion team. The society is an organization that owns the rights to the game Illarion and supports the game by operating and paying for the infrastructure of the game. The society and its board have no control over team decisions beyond ensuring that Illarion remains free to play and continues to pursue its goal of being a multilingual, globally accessible roleplaying game that connects interested roleplayers.

Monthly meeting​

  1. A staff meeting takes place every month on the second sunday at 8:00 pm GMT.
  2. The meeting should not exceed thirty minutes.
  3. Every team meeting takes place in a Discord Thread in the team channel.
  4. Every meeting has exactly for agenda items.
    1. Important issues and events
    2. Current dev vision: Intended game changes.
    3. Current gm vision: Intended story outlines.
    4. Others
  5. If a team member does not show up for two consecutive meetings and shows no other sign of activity in between those meetings, the member is absent. The team may appoint a representative for the absent member until the member is active again.

Development​

  1. Any person is allowed to contribute to the game. Illarion is open-source, excluding it's graphic and sound assets.
  2. A contributor may become a developer and therefore a team member if a majority of the existing team votes in favor.
  3. A developer may add any small addition or bugfix to the game without any further discussion to the game's sourcecode.
  4. Larger additions or changes have to be posted in the development section of Illarion's Discord before implementation. Any team member may raise valid concerns or propose changes. In the event that no agreement is reached, the developers vote on the issue.

Game-Mastering​

  1. Any person may become a gamemaster and therefore a team member if a majority of the existing team votes in favor.
  2. A gamemaster may change small portions of the map, interact with players or hold events without any further discussion.
  3. Larger map changes or consequences of storylines that may interfere with other GMs (for example: catastrophes, war, dead players, town leadership etc.) have to be posted in the game-master section of Illarion's Discord before execution. No story spoilers have to be given. Any team member may raise valid concerns or propose changes. In the event that no agreement is reached, the gamemaster vote on the issue.
  4. A gamemaster must examine reported rule violations. If the rule violation has happend any advantage gained by the rule violation is to be removed from the violating player. The GM decides in any further form of punishment. If the violating player is a repeat offender, the punishment has to be discussed with all gamemasters. The team has to be informed if a significant punishment is imposed. The punishment must be clearly related to the offense in terms of time.

Any Staff​

  1. Any staff member may propose smaller and larger map changes. Any team member may raise valid concerns or propose changes. In the event that no agreement is reached, the team votes on the issue.
  2. Any staff member may hold small ingame events or create insignificant player interaction as long as they dont have any long term roleplay consequences and do not conflict with a storyline or an event organized by a GM. To be temporarily excluded from these restrictions the staff member can create an inquiry in the game-master section of Illarion's Discord for a single event. The gamemasters vote on this issue.
  3. Any staff member should inform the team about extended absences. If possible, the team member should name a representative that can conclude any open dev features or gm storylines of the member.

Votes​

  1. A vote is done via the Illarion's Discord as reaction to the specific issue.
  2. Only votes of the defined voter group do count.
  3. All votes are votes of simple majority.
  4. The result of the vote is final.
  5. Any vote takes seven days.

This document​

  1. Any content of this document may be changed by proposing a change and let the team vote on it.

Current issues​

  1. Not yet handled rule violations are punished by removing any illegally accessed items. No further punishment is to be imposed, as the offenses occured a long time ago.
  2. A rough plan for concluding the Letma storyline should be made available to the team.
  3. Any previous disputes should be settled amicably. A mutual apology is appropriate from the perspective of all uninvolved team members, as both sides reacted inappropriately, unfairly, and rudely at times.