Difference between revisions of "Suggestions"

From The Shartak Wiki
Jump to navigationJump to search
(Split suggestions page into separate pages as it was becoming pretty unwieldy.)
Line 5: Line 5:
 
Bug reports should go on the [[Bugs]] page.
 
Bug reports should go on the [[Bugs]] page.
  
== Separate Suggestion Pages ==
+
== Suggestion Pages ==
 
 
This page was becoming rather unwieldy, so it has been split into separate pages:
 
  
 
* [[Suggestions:Skills]]
 
* [[Suggestions:Skills]]
Line 13: Line 11:
 
* [[Suggestions:Other]]
 
* [[Suggestions:Other]]
 
* [[Suggestions:Classes]]
 
* [[Suggestions:Classes]]
* [[Suggestions:Game_Mechanics]]
+
* [[Suggestions:Game Mechanics]]
 +
 
 +
== Related Pages ==
 +
 
 +
* [[Suggestions:Implemented]]
  
 
== To-do list? ==
 
== To-do list? ==
Line 21: Line 23:
 
--[[User:Simon|Simon]] 14:59, 5 March 2006 (GMT)
 
--[[User:Simon|Simon]] 14:59, 5 March 2006 (GMT)
 
:I'd say unless your debating whether to implement a change, or are seeking feedback, just make whatever changes you are going to make and only tell us afterward. While I'm sure we are all interested in what might be in the pipeline for Shartak, it creates expectations, and expectations lead to frustration when the ideas you are planning aren't implemented in a timely fashion. Think of a game like Duke Nukem Forever, which created massive backlash among its fans for going through delay after delay. If the game designers had not created the expectation (and being unable to fulfill it), there would be no basis for the fan backlash. --[[User:Jackel|Jackel]] 02:23, 6 March 2006 (GMT)
 
:I'd say unless your debating whether to implement a change, or are seeking feedback, just make whatever changes you are going to make and only tell us afterward. While I'm sure we are all interested in what might be in the pipeline for Shartak, it creates expectations, and expectations lead to frustration when the ideas you are planning aren't implemented in a timely fashion. Think of a game like Duke Nukem Forever, which created massive backlash among its fans for going through delay after delay. If the game designers had not created the expectation (and being unable to fulfill it), there would be no basis for the fan backlash. --[[User:Jackel|Jackel]] 02:23, 6 March 2006 (GMT)
 +
:I like surprises. :D --[[User:Lint|Lint]] 06:10, 8 March 2006 (GMT)

Revision as of 06:10, 8 March 2006

Suggestions for Shartak are always welcome, although there's no guarantee that anything will be added. Comments on or modifications for any of the suggestions below can be added by editing this page. Please be considerate and don't just remove ideas that you don't like.

Begin a new item with a * and "sign" your suggestions using -- ~~~~ so we know who to blame ;)

Bug reports should go on the Bugs page.

Suggestion Pages

Related Pages

To-do list?

Perhaps I should add a to-do list here on the wiki so you can comment/vote on the ideas before they're implemented. Then again, perhaps I shouldn't as this would spoil the surprise ;) Not so much a "things I might do" list like this page but a "things I am going to do" list.

--Simon 14:59, 5 March 2006 (GMT)

I'd say unless your debating whether to implement a change, or are seeking feedback, just make whatever changes you are going to make and only tell us afterward. While I'm sure we are all interested in what might be in the pipeline for Shartak, it creates expectations, and expectations lead to frustration when the ideas you are planning aren't implemented in a timely fashion. Think of a game like Duke Nukem Forever, which created massive backlash among its fans for going through delay after delay. If the game designers had not created the expectation (and being unable to fulfill it), there would be no basis for the fan backlash. --Jackel 02:23, 6 March 2006 (GMT)
I like surprises. :D --Lint 06:10, 8 March 2006 (GMT)