Archivable and ChangeHistoryService

[GollyGreg]

Proposal: Objects with [tt]Archivable[/tt] = false should not be logged with [tt]ChangeHistoryService[/tt]

Reasoning: I’m using it for a brush preview thing on a plugin but I want them to be able to undo terrain strokes but doing so also affects the preview

I was also talking to Vorlias and he was having an issue with his own plugin

@Vorlias

I keep having an issue with it undoing the position of a brick I use for a plugin that lights up the area like fuck so I can see in dark places on the map even though it’s not archivable

Given the name of the property, it would seem that this behavior shouldn’t be occurring. I looked into [tt]ChangeHistoryService[/tt] on the wiki and couldn’t find a way to have it ignore specific objects. What do you all think?

[Vorlias]

Yeah, this is one of those little things that really don’t make sense and cause problems.

I’m getting sick of pressing undo only to have it undo the position of this proxy part instead of what I last did.

[Pyrolysis]

Am I missing something?

[Tomarty]

Being unable to ignore instances used by plugins has been frustrating me for years. We need this.