Merge Save Point and Trigger Autosave

[vrad-exe]

Save Point item is not needed as it serves the same function as Trigger Autosave, and just takes up an extra spot on the palette. Save Point should be removed, or merged with Trigger Autosave if it does have a special function that Trigger Autosave doesn't.

[LautaroL20]

Well, for some "mysterious reason" developers still want to keep both instead of merging in one unique item, even when they works the exactly same. I have posted this before in the past, but they didn´t answered my latest comment, you can check the comments of the old post, here:

273

[ghost]

Spooky!

[TheDarkBomber]

@LautaroL20

didn't answered? Don't you mean didn't answer?

[ghost]

@TheDarkBomber Does that really matter?

[LautaroL20]

@TheDarkBomber - Wops, I just forgot that i must not write two past tense verbs at the same time, thanks for the reminder.

[TeamSpen210]

Part of the reason I'm keeping HMW's item around is because of the neat model it has. Maybe I'll alter that autosave to have a differently-sized autosave brush in different orientations, and other things to ensure you're in a safe place before doing the autosave.

[vrad-exe]

@TeamSpen210 Maybe the save point item could be re-purposed as a visible save point, which would appear as a flag or something in-game.

[LautaroL20]

@Luke18033 - If you make it to become visible, I doubt that would fit into the game atmosphere, players will likely going to say "Oh fiddlesticks, what is this thingy?"

[vrad-exe]

@LautaroL20 Okay then, maybe it could have it as a red circle on the ground, which would turn green when stepped on, and turn yellow when another save point has been activated.

[TheDarkBomber]

It should be invisible.

[vrad-exe]

I'm going to continue to use Trigger Autosave when I use the BEE2 (which is rare now that I'm using hammer) as opposed to Save Point, as it saves palette space.