uh i kinda feel like coding 2048 i guess - here's the journal (originally was gonna be 2 weeks but idk it's kinda fun and an opportunity to make actually nice code for once)
- create repo + first files
-
create grid
-
make methods to add, combine cells
-
change to make cells a dictionary
-
begin to implement move left (press left key)
-
consider changing implementation of tiles to set / multiply instead of add
-
changed my mind again on how to implement this
-
make a list of all the tiles in the row (not including spaces)
-
combine all pairs
-
return new list as row
-
probably should add typeErrors at some point
-
ong probably woulda been better to just use numpy arrays but hey we're here now
-
eod: now has a move-left function and a repr
-
further plans: implement movement in other directions, automagically adding new tiles, clean up code
-
next steps: add actual controls and potentially a score? then it's just ui work
-
finish up move_left and move_right
-
want to make a move_up and move_down using same code (DRY etc)
-
will copy code over, want to find nice solution that doesn't involve copy-pasted code
-
ok so move_up and move_down actually work now
-
add functionality to add random cell
-
eod: game now functionally works and finishes when 'attempt to add cell but no free cells' (ie move made and no free cells)
-
breaks when: move is made but nothing changes. not sure why (since code should still function) but worth looking into
-
next steps: prettify ie make gui
-
fixed crashing issue (forgot to implement part of move_horizontal and move_vertical lol, done now though)
-
todo: add proper game end condition (when add random cell fails, check to see if there are any valid moves), prettify, make gui
-
no longer adds a new tile when invalid move is made
-
now ends the game when there are no valid moves
-
would like to remove tile class and replace with ints but am worried that the class may come in handy later for rendering so i'll keep it for now then once the rendering is done, if that doesn't use the tile rendering i'll remove the class
-
made pygame window, moved to using pygame for key handling
-
removed Tile class, have broken something (move_right specifically seems to be broken for some reason) - will have to figure out how to fix at some point
-
ok the fix now works; turns out the bug was there all along lol (i was flipping the row when doing 'reversed' movements)
-
todo: make some sort of grid_coord -> pygame_coord system
-
game now has ui, mostly functional (need to remember to change font to something sensible at some point but webdings is fine for now)
-
now counts score and has a counter at the top
-
todo: add palette for the rest of the numbers (perhaps generative palette), implement proper game end (and retry functionality), adaptive font size, randomly spawning 4s occasionally, would be nice to have sliding animations eventually, nice notifications (+n when adding score)
-
issues: occasionally ends game (valid_moves returns false) when it shouldn't
-
fixed issue #1
-
add default style for when exceeding largest tile defined in palette
-
add randomly spawning 4 tiles (currently P(spawn 4)=0.2 but can adjust either default setting or when creating Grid object)
-
now has an alive status on top right and can restart (when dead) by pressing r - requires ui update (prettify alive status, give proper reset, perhaps max score?) - removed the alive status (but functionality is still there)
-
now displays game over message when losing
-
todo: reactive display (allow window to be resized, scale / move ui components as required), pop this onto a github pages
- oh the chores begin - i have begun refactoring in line with refactoring guru's recommendations. so far i have just moved large chunks out of the main loop, i still would like to change which parts of those are parameters though (it may be worth making a separate GridRenderer class for that, and perhaps a separate file)
- i also made a new file for this stuff (effectively journal) so the README can actually serve its purpose