-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
./tree and /bigtree #2125
Comments
Why blocking? |
a reason please |
issue close! |
Perhaps we can figure out a way to roll these back. @Wild1145 any ideas? |
Admins can rollback it Issue close |
/ro |
@Gusted /ro would risk removing more than the tree that was just placed. The issue here is that //undo does not appear to roll it back, though I am not entirely sure why, as I understand it, the command simply creates a tree / big tree at the location you are looking at? Not sure why //undo would not work with it... |
Use CoreProtect. |
@Ir1x TFM does not officially support CoreProtect at the current time. The TFM version of Rollback or TF-WorldEdit are the plugins a solution should be found through. As I mentioned, WorldEdit does not appear to track these commands and that is an issue. |
Both commands are used for griefing; upon ban doesn't roll back any created blocks.
The text was updated successfully, but these errors were encountered: