Strict Standards: (assassin) Declaration of SSLAuthPlugin::modifyUITemplate() should be compatible with AuthPlugin::modifyUITemplate(&$template, &$type) in /afs/athena.mit.edu/activity/a/assassin/web_scripts/wiki/extensions/SSLAuthPlugin.php on line 47

Strict Standards: (assassin) Declaration of SSLAuthPlugin::setPassword() should be compatible with AuthPlugin::setPassword($user, $password) in /afs/athena.mit.edu/activity/a/assassin/web_scripts/wiki/extensions/SSLAuthPlugin.php on line 47

Strict Standards: (assassin) Declaration of SSLAuthPlugin::initUser() should be compatible with AuthPlugin::initUser(&$user, $autocreate = false) in /afs/athena.mit.edu/activity/a/assassin/web_scripts/wiki/extensions/SSLAuthPlugin.php on line 47
Feasibility - Assassin Wiki

Feasibility

From Assassin Wiki
Jump to: navigation, search

“You blew up God…with a rocket launcher?�

Writing a Guild game is no small matter with respect to effort or time. While several endeavors have produced playable games within an extremely limited amount of time, the truth remains that most games take a GM team several months to author, and design schedules of a year or more both common and recommended by many writers in the Guild. When designing games games, GMs need to consider if they are capable of turning their ideas into operable mechanics and if they can support those mechanics during the game. To better understand this, we first need to look at a typical schedule of game development.

Return to Tensions in Live-Action Roleplaying Game Design

Retrieved from "http://assassin.scripts.mit.edu/wiki/Feasibility"
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox