Die4Ever

Maybe you could do unit tests based on saved states? Load a save state, run 1 frame, then create a save state and ensure it matches the expected save state?...

I would also like this. When I share an Oengus link with my community for them to submit to a marathon, it would be very useful if the due date...

This would also allow us to do an rss feed? https://video-game-randomizers.github.io/rando-list/feed.xml

list of recent updates works now, but the cutoff date is hardcoded https://github.com/video-game-randomizers/rando-list/blob/main/src/_includes/recents.html hopefully it can be made automatic by doing math on `site.time` variable, which is the build date...

Tags for platforms might be a bit complicated with multi platform games where the game runs on multiple platforms but the randomizer only works for certain ones. Or even randomizers...

how about this? would this be too much work for us to track? ``` diff --git a/src/schemaCheck.py b/src/schemaCheck.py index d410c2a..11c5a2b 100644 --- a/src/schemaCheck.py +++ b/src/schemaCheck.py @@ -21,7 +21,48 @@ MaybeString...

We already have the ability to do it in waves! That code diff shows that the new fields are only required according to the updated date of the item being...

I'll add just `opensource` and commit it for now, just as an example later we'll maybe just do an automated script to extract out lists of games

here's some example restructuring Deus_Ex.yml ``` name: Deus Ex comment: null sub-series: null games: Deus Ex: genres: [] platforms: [] release_year: null GMDX (mod): genres: [] platforms: [] release_year: null...

forgot to put the issue number in the commit messages... https://github.com/video-game-randomizers/rando-list/commit/d337f1d165c8935249a5e167c202989d9c5cad98 https://github.com/video-game-randomizers/rando-list/commit/7f923d58778f8c726a2efc48528cf03b0655466e