show in the credits? ask the server for the leaderboard for the current seed and flagshash, and also for the flagshash with any seed? this helps prepare for monthly seeds #290
maybe also track leaderboards for number of deaths, number of loads, and number of saves?
data to store:
playthrough_id, player_name, version, seed, flagshash, difficulty (some can also read it from the other tables)
bools for isMonthly? Max Rando? Chosen seed vs random seed? (the GUI can remember which seed it generated)
in-game time, complete in-game time, menu time, complete menu time (all broken down by mission?)
deaths, loads, saves (also broken down by mission? deaths could be queried with a join, except deaths while offline)
bingo progress? which ending, and carriedItem?
maybe just use sql columns like:
playthrough_id, keyname, mission, value
so you could do keyname for menutime, value would be the timer, and have it for each mission, although a playthrough can have multiple completions so maybe need an autoincrement id too
show in the credits? ask the server for the leaderboard for the current seed and flagshash, and also for the flagshash with any seed? this helps prepare for monthly seeds #290
maybe also track leaderboards for number of deaths, number of loads, and number of saves?
data to store:
maybe just use sql columns like:
so you could do keyname for menutime, value would be the timer, and have it for each mission, although a playthrough can have multiple completions so maybe need an autoincrement id too
currently (2023-02-13) we have: