summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/tilde30.t50
1 files changed, 50 insertions, 0 deletions
diff --git a/doc/tilde30.t b/doc/tilde30.t
index 5eeb436..a2dfb9f 100644
--- a/doc/tilde30.t
+++ b/doc/tilde30.t
@@ -197,5 +197,55 @@ you can break up a mill
 when capturing.
 up next:
 ending the game.
+.
+.
+.IP 15
+implemented a game ending!
+now if a player has fewer than 3 checkers,
+the other player wins the game.
+up next:
+endgame edge case where if a player has 3 or more checkers,
+but no available legal moves,
+then they lose.
+.
+.
+.IP "WEEK TWO REVIEW"
+light week.
+spent almost all of it on vacation
+and not working on tilde30 at all.
+nonetheless,
+i'm mostly finished with the core of the game.
+i have one small edge case to iron out
+and then the game will be all the way complete.
+i think for my first stretch goal,
+i want to add some kind of generative story mode
+based on player moves and decisions, etc.
+so that by the time you're done with the game,
+you have a unique little story to take with you.
+i'm not sure whether i want to do a tracery grammar
+type of thing..
+could be fun to try to write that.
+well here's to tilde30 being half over!
+hope everybody is having fun making progress
+on your projects!
+.
+.
+.IP 16
+I wrote the "no-moves?" function
+to determine whether a player has no legal moves remaining.
+And a test for it.
+But integrating it created a bug I need to track down.
+.
+.
+.IP 17
+Didn't fix the bug,
+but rewrote "no-moves?"
+using the "->" threading macro
+which is neat.
+I've never used it before.
+It's basically the "compose" or "pipe" function
+that I have enjoyed using before in javascript.
+up next: fix that bug!
+
 
 .pl \n[nl]u