You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
Lets say I have a dungeon with 100 levels where each level is 70x70 tiles, that equals a total of 490000. Each tile is around 128 bytes (according to the chrome debugger). That means the dungeon alone takes around 60MB of memory.
Instead of generating and storing all the levels, maybe just generated them as needed and store only the current one, and any levels that a player has died on? That would leave a max of around 3MB of memory.
The text was updated successfully, but these errors were encountered:
What could be done is phase old dungeon floors out of memory (adventurers never ascend). I generate the whole dungeon, though, because it lets me populate all of the info for the dungeon tab (plus, some victories add on to the bottom of the dungeon, which would be hard to estimate if a victory condition generated a random number of floors).
I'd be open to a PR that can retain all existing functionality and generates on demand, though. A place to start would be to phase out the old floors while descending.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Lets say I have a dungeon with 100 levels where each level is 70x70 tiles, that equals a total of 490000. Each tile is around 128 bytes (according to the chrome debugger). That means the dungeon alone takes around 60MB of memory.
Instead of generating and storing all the levels, maybe just generated them as needed and store only the current one, and any levels that a player has died on? That would leave a max of around 3MB of memory.
The text was updated successfully, but these errors were encountered: