Pressing F9 or whatever is the quickload button and opening container is way too simple to abuse, even accidentally. There is also the downside that if I get some really cool loot, forget to save, die immediately after and load, I don't get that cool loot anymore and feel cheated.
Basically all arguments are I hear against this is that "its not game breaking, don't fix it" which seems incredibly silly, how insanely annoying would it be to play a game with only completely breaking bugs were fixed? Clitchy UI? Don't fix it. Missing textures? Dont fix it, etc.
Games should be designed so you CANNOT abuse the game mechanics without external program or dev console. This is super simple stuff guys.
you talking about a bug. technically this is not a bug. it is a game mechanic that some of you use to your advantage (ie cheat), nothing more.
Since when do we not try to fix cheats or potential imbalances?
Let me use a different game as an example. I play a game where the major focus of the game is on survival, which requires you to gather consumable resources (food, water, depletable equipment, etc). It's also co-op, with character saves being done locally.
You can easily manipulate this setup to dupe items... which really pretty much sacks the entire "survival" aspect of the survival game. You really don't have to worry about running out of resources (or take them seriously at all) when you can just create more by manipulating saves and loads. You're not hacking anything or exploiting a bug.. you're just using a poorly thought out save/load system to trivialize the content.
There are ways to fix that, but should they? A player might argue that an isolated single-player or co-op game doesn't impact other players. But a developer might be thinking
"you know what? For the past X years my team busted its collective butts getting our dream game out to the players, and I'm not about to let a huge element of that dream to be trivialized by this exploit.". And that would be a perfectly understandable for a developer to take.
There's nothing wrong with bringing these sorts of problems to a developer's attention. Trust me, it's worse when it catches them by surprise post-launch.