4 ms·
Yes this is a key insight, and fortunately something I realised very early on in my JavaScript game engine which had a custom PRNG - but effectively for part of
by purple-leafy 4mo ago
Yes this is a key insight, and fortunately something I realised very early on in my JavaScript game engine which had a custom PRNG - but effectively for part of my game engine (stateful replays) every time I change my codebase and release/publish I effectively have to freeze that version of my engine - and route players to that engine version silently.
It’s not elegant but I don’t see any better way to do it to maintain backwards and forwards compatibility.
My plan is to control engine versions via a manifest.json or similar that points to applicable engine versions as a compatibility layer