The implementation of the rollback command leads to excessive memory usage when players massively place and destroy structures. Even with 4GB of RAM and -XX:+UseZGC, the memory consumption quickly reaches critical levels during such activity.

This becomes especially problematic in scenarios with repeated building and breaking of the same structures by multiple players. The system struggles to handle the volume of rollback data, and performance deteriorates rapidly.

I'm not sure how to properly fix this other than completely disabling the rollback feature or redesigning the algorithm to store identical destroyed structures more efficiently.

Possible solutions:

• Optimize rollback data storage, especially for repeated or identical actions.
• Implement deduplication or compression for similar changes.
• Add configurable limits to rollback history or memory usage.
• Allow selective rollback regions or player actions only.
• Use the disk to store data.