Don't double-save fast, as this invalidate the last quicksave. When quicksaving, give it a second or two before triggering again. Greater than this chunk of C++ antipractice lmao. You make mistakes, because nobody is perfect. I can share source if anyone asks politely. To each their own, don't need it, don't download it, don't use it. I also take full responsibility for my saves if they break. I know that a meta way is to disable quicksaves and autosaves as soon as you start playing Bethesda game, yadda, yadda. This piece of code is simple - and I did my best to make it as tidy as possible, but you know what they say - 'Every day at work is an adventure if you are underqualified enough'. However, if save managers you have installed use the default naming convention, this will most likely cause trouble. They should not interfere they use a different naming convention. Chances of it breaking your saves are slim but never 0.

This whole part of code is the most shameful for me, but what can I do. If it finds a 'LAST QUICKSAVE' set of files, it deletes them first. So, this tool is monitoring changes to quicksave files - when it detects a sequence of file changes that suggests a quicksave event, it renames quicksave files to 'LAST QUICKSAVE', and that's about it. We don't have multiple quicksaves, there's only one, so we can't cycle them and make room for the next one.

Quicksaves Now here the situation is quite different.

Fallout 4 faster loading screens mod