The last scenario is if there is a certain place I've died, in which case I'll usually leave a state before coming there again. I don't really ever use them, it's more of a habit - a "just-in-case" thing. In Darius Twin (side-scrolling shooter) I leave saves at the various bosses. I tend to use savestates relatively often in certain places in certain games, like SMW, because I'm playing with a laptop, and when I hold the sprint button in, it often disconnects regardless, making many simple run segments a pain. It's like they don't even know why they do it. There are certain people that save and load pretty much constantly.
Watching a Let's Play video with excessive savestate usage makes me sick. There are also many older games that don't have any ability to save. I use it in place of SRAM mostly because it's faster. I have a hack thread - Link (Now with a demo!) For the most part, they're a crutch and relying too heavily on them removes any skill that might be required to get through the game. Thats one place I'd say its ok to use savestates.Īside from the places I mentioned, I think its kinda pathetic to use savestates. Though I can do this level without savestates and collect everything, its very difficult to do because of that segment. Dieing resets your current count back to 0. To get 100% completion, you need to collect 100 musical notes (among other things) in every level. Personally, I only think they should be used before/after levels, before/after bosses, and before/after particularly difficult segments.įor example, in Rusty Bucket Bay in Banjo Kazooie, there is a soul destroying segment inside the ship where a single misstep will kill you. In your opinion, when is it acceptable to use a savestate?