The opposite actually - rows are dramatically added to a database. In most games save files grow the longer you play.
this post was submitted on 12 Feb 2025
1047 points (97.6% liked)
Microblog Memes
7039 readers
1676 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
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
Isnt there this graveyard off map somewhere in Skyrim, where all the bodies get teleported?
Why would that even be necessary? Sounds like one of those “make a guy with a train for a hat and run up and down this hall” moves they like to do
I wouldn't be surprised if it is true though. Bethesda games are not exactly winning awards for coding elegance.
load more comments
(2 replies)
i can't speak to that, but it sounds plausible. in that case the body location would be updated to those coordinates
Grab the source here before Bethesda DMCAs it.
This is how it works in many game engines.
You set up the monsters and just hide them/disable them. They're already allocated to memory.
And it's a performance cost to create/delete versus just moving a dead enemy out of view, then respawning that enemy later in the level.
load more comments
(3 replies)
load more comments
(4 replies)
This is why Breathe of the Wild did the blood moon thing, periodically they'd just bring all the dead enemies back so file size didn't get too large.
Also, it's an unreasonably fast database. That makes lots of trade-offs that normal ones aren't willing to do.
*Noita file save on the 7th parallel world intensifies*
load more comments
(7 replies)
And spectator sports are watching people exercise and reading is staring at a tree while hallucinating
staring at a tree while hallucinating
Same with taking shrooms
Fantasising based on looking at ink blots on a butchered tree.
Staring at a tree while hallucinating. I love this.
Hah! Joke's on you, player! I pooled my game objects and you're endlessly killing the same bad guys with the same bullets over and over.
Macrodata refinement in cold harbor
Kier, chosen one, Kier. Kier, brilliant one, Kier.
Reductionism when "it isn't murder I just deleted your row from the national health government database"
Eve Online, basically.
(rofl!)
Or you know, monetary & financial systems we humans trust in.
After hours of trial and error, I finally changed the integer on the BossKill parameter from 0 to 1!
I like to dramatically DELETE rows FROM slow_database
No, I'm not playing. In reality, I'm just bumping atoms in a galactic billiards game with the biggest chain reactions.
Pretty much them zombies would be in active memory
Incidentally, just decided my new band name, active memory zombies
In the engine I've worked on it's even less dramatic than deleting a row. It changing a single boolean from 1 to 0.
"Single bit state CHANGED!!!”
Honestly excel would be more exciting if the commentator from mortal kombat described my actions if I correctly use a function.
DRAGGED A CELL BY ACCIDENT
RESET ALL THE FILTERS BY ACCIDENT
FLEW TOO CLOSE TO THE SUN AND MADE IT CRASH AGAIN, DIPSHIT
I've been working on a survival/RTS game and it's funny that even though the game development framework I'm using (Unity) tends to push you to put most of the code on the visual objects level and that was my original approach, over time I've figured out the whole code is way cleaner and works better (in other words, the best architeture for that software) when almost all of the game is really just a Data layer being manipulated by the player and a separated View layer for the players to visualized it in a nice way - basically a Model-View Controller Architecture, same as you'll find in systems were a server-side application has web and/or smart app UIs.
That said, I have the impression that something like an FPS is a lot less data-driven than an RTS because things like the 3D models that make up the world are a lot more important for data decisions (has the bullet hit an object, can the player move to this position). You can still say that stuff is data (3D models are data, specifically collections of vertices in 3D space with some additional information attached), but model data is generally way more visualization-oriented than what one could metaphorically call a "database".
load more comments
(4 replies)
I've joked with coworkers that our entire job as programmers is to find ways to light up pixels on someone's screen in patterns that they find pleasing.
LittleJohnnyTables > Get rekt
I would play a database management roguelike.
MDR in severance?
Intensity comes from keeping up and fixing the bullshit your coworkers cause while attempting to build in idiot guardrails to stop further damage.
load more comments
(2 replies)
Well. I mean. Both release dopamine for me anyway.
This reminds me of when I found a project combining Quake and SNMP, you walked around on a map with the routers and switches on the network and you have different guns representing different tools, you could shoot a router/switch with one gun and it would ping it, another gun with run a traceroute, a third would reboot it and so on.
What if killing the zombies is actually alleviating processing power where the server and database are able to function better because you are eradicating the zombies. Technically, that's world conservation
view more: next ›