We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With engine.options.map, we now have the configurations (sectors, rotations).
We just need to send that configuration, and changes (transdim planets gaiaformed, and other extra data like buildings, federations...).
This would cut down a lot on network traffic & database storage.
This can be done on a toJSON() or toString() method of GaiaHex:
Actually since the map is grouped into sectors, the export can be done like this:
[{"sector": "1", "data": [,,,{"planet": "gaia", "building": "m", "player": 0},,,,,{"federations": [1,2]},]}, ...]
There's no need to even serialize coordinates as we can extrapolate the info from the sector & the index of the hex
The text was updated successfully, but these errors were encountered:
We can also, like with Take 6, only send log slices when a game is updated
Sorry, something went wrong.
No branches or pull requests
With engine.options.map, we now have the configurations (sectors, rotations).
We just need to send that configuration, and changes (transdim planets gaiaformed, and other extra data like buildings, federations...).
This would cut down a lot on network traffic & database storage.
This can be done on a toJSON() or toString() method of GaiaHex:
Actually since the map is grouped into sectors, the export can be done like this:
There's no need to even serialize coordinates as we can extrapolate the info from the sector & the index of the hex
The text was updated successfully, but these errors were encountered: