/v/ - Video Games

>>15617227

>How often do you quicksave?

At the maximum length of time I'm willing to lose should I hit a failure state.

>How often does one have to quicksave for it to become savescumming?

Depends on the game. For me personally, I'm fine with using quicksaving as an RNG mitigation tool in cRPGs for out of combat actions, but I don't use them in combat situations. For games like STALKER, my rule is that I can only save "out of combat", no matter how long the firefight is, and that tends to keep me on my toes.

>>15617227

For FPSes, it's not savescumming, it's saving yourself time so you don't have to do the same thing 50 times over that you already succeeded at.

In games that require a lot of time investment that could all go to shit from a momentary lapse in judgement or just plain old rng being against you like rimworld or xcom for example I always save before doing anything that could lead to that.

I'm not spending 20+ hours of my life on a save game just to throw it away because I got fucked over in a 1 minute timespan, that shit is retarded and I don't understand why anyone would do that to themselves.

In Pillars of Eternity I was save scumming every encounter, and sometimes multiple times between encounters because fuck those traps. fuck all of the traps. Fuck the ones you can't disarm and fuck accidentally walking into them.

>>15617227

I play a lot of old shit so I quicksave pretty often due to how random crashes can be. I also quicksave during bullshit like MM7's black potion making.

polite sage

The ability to quicksave in a particular game is the mark of a lack of challenge, but the impossibility to quicksave regardless of the game is the mark of a worthless platform.

>quicksaving crashes the game

happened in stalker

happened in oblivion and every other bethesda game

So I stopped quicksaving at all and just manual save every time. It's not even that much slower. Also I often mix up which is quicksave and quickload and then spend more time thinking about which is which and just manual save anyway. Generally though I save less than the games tend to autosave. Usually only when I'm going afk, quitting, or heading into a new level.

>>15617269

>I'm not spending 20+ hours of my life on a save game just to throw it away

A day of playing video games. It would be a real travesty if that were wasted.

>>15617318

>not spending 20+ hours of my life on a save game just to throw it away

<A day of playing video games

How about you stop being retarded and consider that they'd have to spend another 20+ hours to get to the same point. That's actually two days wasted on a save game.

>emulation

never ever use save-states (besides backing-up the fallowing) always use in-game save options.

>>15617285

>FPS

classic FPS levels (**doom, duke3d,etc) ought to be completed without any save scumming. Saving between levels is only time its truly acceptable.

>dungeon crawlers

it depends on the game honestly, but a part of some dungeon crawlers is resource management and if you are save scumming to save on potion uses and to have the optimum outcome between every battle then you are sorta undermining the game design.

>>15617227

>How often do you quicksave?

depends, but usually if im playing a turned based game, its usually after every turn. if its real time, i usually save every couple minutes or before going anywhere or fighting anything.

>Easy section

>Maybe a very long cutscene too

>Hard section

>Lose and have to do easy section and/or a long cutscene too

If I the ability to savescum, I usually do it then to avoid having to go through a part I more then mastered.

You can quicksave as often as you like without it being savescumming. It becomes the latter when you reload whenever something bad happens.

>>15617342

>never ever use save-states (besides backing-up the fallowing) always use in-game save options

Joke's on you, I savestate after every level.

I don't really quicksave/load since it reduces the chance of accidentally of pushing the wrong one. Such as overwriting the quicksave when I want to load or loading when I want to save. Other than that, my save policy is simlar to >>15617342. Although I have used save states at save points and password screens, just to speed up the loading process when I boot up the game.

no quicksaves during encounters

>>15617544

>save points and password screens

that makes sense

Does load/save in Daggerfall counts as save scumming?

>>15617253

For STALKER I have a rule of only using the auto save from area transitions or only saving when i'm in a safe location, like cordon village or the duty camp, makes it more engaging.

>>15617227

I quicksave, go up a ladder and then quick save immediately again. so every 20 seconds

I grew to dislike any game with manual saves in it, including quicksaves of course. Being able to save whenever you want means you can never lose anything but a minute of your time and you're not terribly interested in survival. I prefer permadeath with a single autosave and a single difficulty that developer deems suitable or respawns like in Dark Souls.

One game with quicksaves I still like is modded Dragon Age: Origins, with FCR mod many encounters become so difficult they're like a puzzle that you have to solve over multiple attempts.

Never. Quicksaving has always been the Achilles' heel of PC game design. It has always resulted in shit pacing and difficulty scaling. With a number of PC games, despite your best efforts to enforce some degree of punishment for failure, it remains impossible to make skill-based progression feel satisfying in them. The games in which this occurs are fundamentally bad ones.

>>15617293

Nobody does that, faggot.

>Emulators

Never, unless I can't be assed to wait for save/load times

>FPS games/Max Payne

After every firefight/Slow mo death of the last grunt

>Stealth games

Usually never, unless I have no idea if a jump will kill me, or a specific area is too slow to want to redo.

Depends. For buggy / unstable games that might freeze or crash to desktop when you least expect it to, savescumming is a necessity, not a luxury.

>>15617227

I would quicksave pretty regularely, because I'm kinda prone to mourne losing progress.

For situations, like a boss battle, I usually try to go along and even put in good resources should something fail, but if I see that anything devastating happens that was just pure worst luck or I made a glaring mistake early on, I would just reload and retry the fight.

It's just perfectionism Vs immersion.

If you want better roleplay. Take your rolls.

If you want to 100% everything then quicksave like a motherfucker.

I'd say if you watch for flags in RNG and retry as soon as you see

<that boss has the highest HP set right now, don't even bother

then that would have crossed the savescumming line.

>>15617227

Never, because I’m too lazy but also because autosave is a thing

>>15617227

Before and after every enemy encounter if the game is designed to allow unlimited quick saves.

It's not save scumming if the game is a broken piece of shit. Fuck Pathfinder.

>>15619511

>I am a complete faggot.

Only if you'd take videogames serious you would be.

Quicksaving is cheating, absolutely. If the game doesn't have check points the only appropriate save is at the beginning of a level.

>>15619672

Didn’t enjoy bugs galore and broken dialogue boxes?

>>15619679

What if the checkpoints are badly placed? I don't mind repeatedly biting my teeth out on particularly nasty areas if they can be one with realistically means, but checkpoint right BEFORE the unskippable five-minute boss intro or those associated with a ten-minute foot slog through plainly tedious areas should be forbidden.

>>15619679

This. Quicksaving is a crutch.

>>15619532

>reloading 9/11

Why? Nothing of value was lost. If you mean to avoid the restrictions on liberty placed afterwards then sure.

never quicksave but i have no problem with save scumming

stop pretending like youre an elitist by playing the game with arbitrary rules

>>15618788

I do. I always question to myself. "Hm. If I'm saving time by doing this wouldn't it just be better to watch the ending and call it quits? Or better yet, just quit the game since that's the best way to save time?"

>>15617227

>How often does one have to quicksave for it to become savescumming?

Well here's the question how often does this game crash? If it's a game where it will crash at any time then you mash the fuck out of that quick save key whatever it doesn't matter. Now if the game is pretty stable then I would say quick saving whenever something is about to happen is save scumming.

>>15626025

>tfw i miss driving over from canada to buy illegal fireworks and cheap liquor because some amerilard politician decided that canada was more likely to be terrorist than the saudi dick he sucked that flew into the towers

Until games became crashy messes, I used to only hardsave when I was going to stop playing.

Now I feel forced to do it pretty often if it's not automatic.

>>15617260

>it's not savescumming, it's SaveScumming™

Ahh.

>>15626029

Bullshit you never used quicksaves, unless you turned quicksaves off then you have played atleast one game with quicksaves.

Savescumming itself encourageso a mindset of saving and reloading at even the slightest hint that something could go wrong. Results of this attitude is anything less than perfect means a reload. That is not a particularly thrilling experience.

quicksaving is for massive casuals.

the only acceptable quicksaving is for experimentation.

>>15617227

Honestly why do you care? Are your friends going to steal your pokemon cards if they find out you played a SP game incorrectly?

I don't quicksave

I quicksave whenever I feel like it. Only insecure faggots need to artificially restrict themselves.

I don't quicksave, I open the menu and save manually. Mind you I've done it up to 100 times in a game for my record.

Just save right before something that keeps beating you/pissing you off, so you can rapidly re-try it. If you have 5 minutes of relatively easy content then one balls hard part, constantly having to replay the last 5 minutes chews into what may be your limited vidya time and is likely to piss you off more than the hard part itself.

>quicksave this thread

>page reloads

Wooooow

I quicksave in Half Life's later chapters. Fight me.

>>15627870

Agreed to some degree. Shows a lack of confidence in the finished product to not bug out but some games don't do checkpoints due to the type of game etc.

It's only savescumming if there is some element of chance because you are re-rolling the dice to get a favourable outcome thereby denying the challenge of the game (managing RNG and making strategic choices based on known variables).

I only quicksave at obvious points (like entering a building or new area) when the game is too stupid to do it for me. So probably only every ten minutes or so, but it varies, and if I get really into the game I'll forget (only to die and realize the last time the game decided to save was 2 hours ago.

>>15626025

US has gone to complete shit after 2001 and dragged the rest of the world with it. It's the turning point after which (((they))) won.

Honestly that is up to personal opinion and to the devs. They gave you that feature to use and abuse after all.

If they wanted to prevent you from scumming they'd do something like Breath of the Wild where saving in a temple before you clear it does not save the progress you've made in it.

If you load the save you're just at the beginning of the temple again.

There's even "quests" that do similar things, like that one island that strips you off everything you have and forces you to survive in one go or start over, saving does nothing.

Depends on the game.

In general, the more random factors it has, the more likely I am to make a quicksave every 5 minutes and go back to it the moment something goes wrong.

Extreme 1: almost any DnD game. Those things have so much randomness to them, I have to constantly quicksave and quickload if someone dies and I can't revive them or I take too much damage and can't recover.

Extreme 2: any Total War game. I never reload but I'll still quicksave every move to prevent progress loss due to crashes. I like to see how everything is going to play out.

I'll often save if I feel like I'm going into a hard fight or if it's a branching path and the story is going to progress if I pick the one I'm supposed to when instead I just want to explore as much as possible first.

>>15618560

DaS had a great system, but only because death wasn't such a massive burden; you could still recover all your souls and thus progress if you died.

>>15638042

>what is Kosovo

>what is Iraq

USA was going shit even before that. 9/11 was just another benchmark in an already ongoing process.

I have a mod for fallout that quicksaves every 5 minutes so when it does the hourly crash I don't lose too much

I'm used to buggy games with save corruption issues from the '90s so I quicksave probably once a minute and use a new save slot per save.

all the time

>giving a shit about what other people think about how you enjoy a videogame

Depends on how much of the game is grind and how much of the game is actually fun.

If the game is all gameplay all the time, I quicksave before and after every big encounter. If the game is some bullshit of walking around and hunting for health pickups and ammo for ten minutes then I'll probably save every few seconds, even mid-battle, just because of how frustrating it would be to have to pick up the same pile of junk more than once.