|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+* 2016-09-29 gameplay design doc (0d0919529a96c4c3d81384251aac1864bf55ddcc)
|
|
|
2
|
+- There's too much 'maybe' in there, and it just looks like just about any game of the sort
|
|
|
3
|
+ (too general). I suggest you actually write about what will make the game fun, what will
|
|
|
4
|
+ make it re-playable, what is unique about it, etc, along with an actual detailed description
|
|
|
5
|
+ of the world, the setting, the conflicts, etc. you need to pretend this world really exists
|
|
|
6
|
+ to entice anyone to want to play it, or other developers to jump aboard.
|
|
|
7
|
+- Having a very clear goal is a good way to get attention and stay focused, rather than
|
|
|
8
|
+ tweaking core features forever....then again, it is a forever project
|
|
|
9
|
+- overall comment: i would simplify the complex world design as much as possible, and start with
|
|
|
10
|
+ a smaller prototype where you develop the combat/movement ideas first----in a smaller
|
|
|
11
|
+ world. then, after that's solid, build out more of the complex time-consuming stuff like civ
|
|
|
12
|
+ generation, etc. ------- i think you will be more successful if you relentlessly prioritize
|
|
|
13
|
+ actual player activity/combat in the short term.
|
|
|
14
|
+- for example you could develop the smaller version around a single town with a procgen
|
|
|
15
|
+ countryside, some dungeons etc.
|
|
|
16
|
+- Yes, I recommend an org document with nested TODOs. start simple and build upon it
|
|
|
17
|
+- https://itch.io/jam/january-2016-lisp-game-jam/topic/12836/my-collected-notes-on-keeping-game-designs-simple-and-accessible
|
|
|
18
|
+- simplify relentlessly and don't be afraid to postpone more complex stuff
|
