Warning Popup for Remove Filtered button

[CosmicGlowsticks]

Is there an existing change request for this?

• I have searched the existing change requests.

Are you using the latest Structurize Version?

• I am running the latest alpha version of Structurize for my Minecraft version.
  I am also running the latest versions of other mods that are part of my problem.

Did you check on the Wiki? or ask on Discord?

• I checked the MineColonies/Structurize Wiki or I asked on discord.

Minecraft Version

1.20

Structurize Version

1.0.733 RELEASE

Related Mods and their Versions

All of my mods are up to date. Forge version is 47.2.32

Current Behavior

I accidentally pressed the "remove filtered" button and obliterated a massive chunk of land, removing literally every single block within the scan area. I am unable to restore it.
Reasons:

1. Every block removal is listed as an individual action, clogging the undo list.
2. Undo function does not always work well on large amounts of blocks. (I would love a fix for this too, though I fully understand if it isn't possible)
3. I have no recent backup.
4. I panicked and left the world, ruining my chances of fixing it.
   *I am running a release version, not an alpha, but it wouldn't let me submit this post if I didn't check that.

Enhancement or Change description

When pressing the "remove filtered" button, I would like some kind of warning pop up asking if I'm sure I want to do this. This will prevent any major accidents, say, losing something I have been working on for a solid week or 2.
I am going to be a bit blunt, I don't care if its inconveniencing to some people, this level of accident is far, far worse. Maybe have it only apply if there are more than 3-4 different types of blocks/entities that would be removed if its that bad.
If possible, I would also like a way to reverse the entire action in one go, rather than one button click being split into individual actions per block.

Anything else?

Footer

---

Viewers

• Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
• Add a comment if you have any insights or background information that isn't already part of the conversation.