Make the build number or some sum number unique for each commit
Hi all,
Would it be possible to make the build number or some number unique so whenever you are compiling so we know that we are playing the latest build. What we get is something like v 0.15 which is not right. What I would suggest is if it each build becomes unique either by using the commit id (for e.g. 9504852 which are the first 6 numbers of today's update) or the first 6 numbers of sha1sum,sha256 whatever sum number is good.
$ sha512sum flare
229984d06e5a96bc64a19ee1f26587b0ac16887172604616eb31d2b7e73ae80e6a849844f239e5234fd8020ac18c29323dbe44425cba60d7bf8f881238136f56 flare
So in this case it would be 229984 . Mind you this is in on 64-bit GNU/Linux Debian on Debian Sid.
Btw can somebody share where the savegames are? I tried both in /home/shirish/games/flare as well as .config/flare/ but neither place I can see a directory or a file by the name save/saves or something, maybe I'm not looking hard enough. Any suggestion would be nice.
Update:-
Found that the save file is saved at ~/.local/share/flare/save1.txt . A weird place to save the save file if you ask me. Thank you ceninam on #OGA .
What would be your suggestion to the location of the save file?
(A better directory can be turned into a ticket in github, maybe with converting support)
Preferably in the same directory where the game is. I do see NOW that clint had told of the directory in the README .
SAVE FILES
==========
Save files are stored in one of these places:
$XDG_DATA_HOME/flare
$HOME/.local/share/flare
./saves
guess I should have paid attention to that part as well.
Save, config, and data file locations follow the XDG standard. I know it's weird.
We're not actually posting binary builds, just checking in code updates. It doesn't make sense to maintain a build number. Plus we have several developers working at different paces, not building on one central machine.
Add new comment