Wishray Wiki

A central hub for intelligent game design and play.

User Tools

Site Tools

Trace: • resolution
livehack:model_of_play

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
livehack:model_of_play [2013/08/19 16:16] – [Method] Mike Holmeslivehack:model_of_play [2013/08/19 16:21] (current) – Mike Holmes
Line 5: Line 5:
  
 =====Rigor===== =====Rigor=====
-The game does all of this in relatively rigorous fashion, just as a roguelike game does (and in contrast to how some live RPGs work). Optimally, the GM will never have to resort to fiat to answer a question of success or failure, or even quantification of results. LIveHack should almost not require a GM, just as a CRPG does not. Almost. +The game does all of this in relatively rigorous fashion, just as a roguelike game does (and in contrast to how some live RPGs work). Optimally, the GM will never have to resort to fiat to answer a question of success or failure, or even quantification of results. LiveHack should almost not require a GM, just as a CRPG does not. Almost. 
  
 Note that this makes this game completely unsuitable for those who prefer the sort of free-form problem solving that some people ascribe to play of early versions of D&D, where resolution of most actions is a matter of convincing the GM that the player's clever plan for their character's success will succeed, and having the GM decide on that success or failure without reference to any standardized mechanics. In fact, if anything, LiveHack is a reaction to that sort of play.  Note that this makes this game completely unsuitable for those who prefer the sort of free-form problem solving that some people ascribe to play of early versions of D&D, where resolution of most actions is a matter of convincing the GM that the player's clever plan for their character's success will succeed, and having the GM decide on that success or failure without reference to any standardized mechanics. In fact, if anything, LiveHack is a reaction to that sort of play. 
Line 26: Line 26:
 Given that we want to encourage creativity, do not punish the players for it ever. If the players come up with some method of proceeding that makes things seem "too easy" then they're playing correctly, and should be commensurately rewarded by the system. If the players find that such a strategy becomes degenerate, making the game too simple, then it's up to them to request that the GM change the game model in some way to make it more difficult. The GM has no responsibility to try to increase or decrease the challenge in LiveHack. The GM's role is simply to add content where needed, and to act as a complex command parser.  Given that we want to encourage creativity, do not punish the players for it ever. If the players come up with some method of proceeding that makes things seem "too easy" then they're playing correctly, and should be commensurately rewarded by the system. If the players find that such a strategy becomes degenerate, making the game too simple, then it's up to them to request that the GM change the game model in some way to make it more difficult. The GM has no responsibility to try to increase or decrease the challenge in LiveHack. The GM's role is simply to add content where needed, and to act as a complex command parser. 
  
 +
 +If this sounds interesting proceed on to [[LiveHack:Adventurer Construction]].
livehack/model_of_play.1376954181.txt.gz · Last modified: 2013/08/19 16:16 by Mike Holmes

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki