Hacking a save file is a pain in the ass. The question isn't whether it's possible to change a result, because of course it will always be possible it's a question of how convenient it is. Having F5/F9 right there at all times to erase every mistake is downright encouraging, and the game shouldn't encourage constant reloads.Д®arlier examples of 'Well people can redo things by hacking their save files, so there's no point in designing systems to stop them' are silly. Not forbid, outlaw, prohibit merely discourage.

It's not about stopping anyone cold it's about making the barrier reasonably high to discourage abuse. Seems a pretty extreme 'solution' to something that's only a problem because you personally find it distasteful. Going through Happy Valley or the Valley of Titan would suck pretty hard if you couldn't save. So how would you Bronzeman that? Game only saves when you enter an area? That would blow pretty hard, especially considering how big some of the WL2 maps were. You would have to restrict actual saving. Therefore getting the 'reward' only once.Дrool wrote:But removing the quickload button won't stop compulsive save scummers and you know it.

My idea was more to reward XP (or even better skillpoints of some sort) only when the failure is permanent, eg you broke a lock beyond repair. So, for example, you can't keep intentionally failing a lockpick to rack up unlimited XP. The only thing that I would suggest is that you can only get one batch of XP per activity. I definitely like your idea of rewarding extra XP for a failure.

TL DR : People will save-scum but a good CRPG should not promote this behavior mechanicaly When save scumming is something that will give you better results, it means players will eventually use it (more or less depending on their personalities) and that is simply bad game design.ДЄ good CRPG should give incentive to players to make choices that aren't always optimal or have a fail/succeed state. Jimmious wrote:Guys, of course save scumming is a personal issue and the rate in which you do it completely depends on you as a person.Д«UT, a game's mechanics can make that an option of value or not. If someone savescumms or not is not the choice of the Game, its the Choice of the Gamer. To the challenge which i want to solve, only because some want the challenge but have not the will to fail it and savescumm and are angry about

So why make it more complicated to reload (savescumming will never be not possible) in trying to let it take longer to come Some fights i lost(or lost one of my Teammembers) i reloaded again and the second try worked out. Of course you could try to only place chests, locks or anything else skill based in places where it is possible to do this,Д«ut designing a game that way would be really bad.ДЄs i said, i don't have anything against an ironman-mode or anything, but design everything to prevent savescumming only will produceДЄnd, the 'bronzeman' thing was also no problem. Otherwise, when there are chests (even if theres a fight, before you open the chest) you can save and load if you fail to IF you try to this, you need really bad limitations as only one autosave at the start of a map and nothing more. I don't think there needs to be more adjustment than other that you can't save when you're in a fight.ДЄnd even this can be 'savescummed' when you save before the fight starts und when you loose one or more Rangers you reload and doДЄlso, i don't think there is a possibility to bring such a system to everything like lockpicking and other tasks.

Xcom 2 save scumming