Comic for Monday 8/31 (Early High Res)
So I've made the quicksave/quickload mixup more than once in my years as a gamer... but until 1am last night at the tail end of a Wasteland 3 session, I'd never had the opportunity to do it in co-op. It makes it... OH so much worse.
Comments (8)
Man, that's just a failure of game design right there. Any game with quickload should have Auto-save built in.
It does have auto save. But autosave has intervals. Doesn't help if it doesn't autosave before you can accidentally hit quickload XD
So painful if it happens in a singleplayer game, but I can only imagine how bad it would be in co-op. Ouch! --- Hate to be nitpicky, but you're missing an "a" in the third panel. "What are the symptoms of A stroke?" :P
Actually, not technically. You have A stroke, but the condition itself can be referred to simply as "stroke". So you can say "what are the symptoms of stroke" as well as "what are the symptoms of A stroke". You can see that the Mayo Clinic uses both on their info page: https://www.mayoclinic.org/diseases-conditions/stroke/symptoms-causes/syc-20350113
Done that. Did the equivalent in Visual Studio at work and lost about a day of work. Luckily I didn't need resolve problems so it went quicker.
Oh God, I can actually feel their pain...
Ya, my solution to that has always been to _completely unbind_ quickload. I've never met a game where I couldn't load the quicksave from the normal load menu. Prevents me from fat-fingering it, at least.
That will likely be my first order of business when we start tonight XD