this post was submitted on 12 Feb 2025
1041 points (97.6% liked)
Microblog Memes
6882 readers
1228 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
- Posters are encouraged to link to the toot or tweet etc in the description of posts.
Related communities:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The opposite actually - rows are dramatically added to a database. In most games save files grow the longer you play.
and even if some idiot put every zombie npc in a database (or if you want to think of it that way), you wouldn't just delete the rows! the bodies would disappear, so instead you would update that row like (npcState = KIL, bodyLocation = ) or something. Especially if you wanted to keep player stats
Maybe you would have an array of active enemies in RAM, and when enemies are killed they are removed from that array for example?
In a game like Minecraft for example, you definitely wouldn't want to store every single dead entity and its location when there can easily be thousands created and destroyed in a single second
It obviously depends on the game though.
Definitely depends on the type of game, but it's more likely the game stores data about which areas you cleared and then infer that the bodies of any permanently remaining enemy (like bosses) is to be displayed.
Can vary even more for procedurally generated levels. If the set of enemies is fixed and stay in calculated positions in a map generated randomly, then it might store an array or something tracking the enemies.
Procedurelly generated stuff is all about storing the differences from the procedural generation.
So for example minecraft saves don't store the terrain, they store how it differs (due to player interaction) from the procedurally generated baseline.
(After all, all you need to recreate an untouched procedurally generate world are the bytes of the seed and nothing else)