It’s almost like it’s a requirement that Bethesda programmers never write defensive code.
*remaster. It’s largely just a reskin. As such…yeah, this probably still crashes the game (if it was a legit bug itfp).
and I’m willing to bet that there’s an hour-long video on Youtube about it
The fan wiki page says Salmo is programmed to deliver bread to the inns they visit but if you give them bread they eat it instead. The crash is probably due to attempting to complete delivery of an item that’s no longer in the inventory.
The wiki also says other characters in the game erroneously refer to Salmo with “she/her” pronouns, but until I ask Salmo for their pronouns I’ll keep using neutral language.
In Elder Scrolls III on Xbox, there was a memory leak that they couldn’t fix, so sometimes when the game is loading a new area, it actually reboots the Xbox. Apparently there’s a way the developer can keep a freeze frame loading screen up while the console completely reboots.
I still can’t fathom how implementing that “solution” is easier than fixing a memory leak. Like what the hell?
Fixing a memory leak takes essentially looking at random data that got there somehow and try to figure out the source. You know what approximately it is by analysing a memory dump but it’s most likely a common structure that is all over the app. Best case it’s easy worst case it’s looking for a needle in a haystack.
On the other hand, checking if memory is blowing up, then using already built save and load functions is pretty straight forward. Especially since Elder Scrolls saves the entire state and reloads it.
