glenjamin / babblog-royale Goto Github PK

Having them limited to just one file seems arbitrary. Multiple log files in one zip would compress even better and a single zip file would be easier to manage.

• Create a minimal storage format for games based on deltas
• Build a way to convert to/from the in-memory representation to the minimal delta version
• The reason to have a different in-memory and saved format is so that the in-memory format can evolve over time without breaking saved files
• If the in-memory representation is small enough, can we bung it into the URL?
• Use a netlify serverless function to provide a server endpoint that validates it was sent the right storage format and writes it to some object store using a random/hashed filename (and returns the name)
• Reading should hit the object store backend directly without using a serverless function

TBC

• How can the serverless function be run locally? Do we have to use the netlify CLI or can we add it into the create-react-app process? Perhaps using https://create-react-app.dev/docs/proxying-api-requests-in-development#configuring-the-proxy-manually
• What's the best backend store to use? Ideally with a large free tier so I don't have to worry about it

In particular It's missing the preview state.

We could do with a log file from a game which got to 100% hot zone to check against

At the moment editing the UI is really slick, as fast refresh works great

However, things are a lot slower when making parser changes, as the file needs to be re-imported after a change.

We can use a webpack hot callback to trigger a re-parse every time the parser changes, which should help - just need to keep hold of the file handle between reloads

It might also be a good idea to write some automated tests for the parser logic by running it against some pre-saved log files

Eg. i can't remember how many games ago i played BEELINED and it's annoying to scroll through all of them trying to find it

(Via personman)

• Select which steps to be included
• Select which tiles to be included too?
• Use something like https://jnordberg.github.io/gif.js/

At the moment bombs aren't quite tied to players, so it gets skipped over

The log files are pretty verbose, but compress really well.

If the parser could decode compressed files then that would be nice

Rather than use a select, we can use a custom drop-down menu that will give a little summary of the session, including starting MRR - using elements means we can tidy things up and include number of kills / level etc

We could also add hotkeys for next/previous game

The player is marked dead on the opponent's second-to-last word, instead of their last word

Include some debug logging about the state of games and some suggestions for how to report it?