Skip to content
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

Open
DeternoMC opened this issue Oct 14, 2017 · 9 comments
Open

./tree and /bigtree #2125

DeternoMC opened this issue Oct 14, 2017 · 9 comments

Comments

@DeternoMC
Copy link

Both commands are used for griefing; upon ban doesn't roll back any created blocks.

@Gusted
Copy link

Gusted commented Nov 12, 2017

Why blocking?

@Gusted
Copy link

Gusted commented Nov 12, 2017

a reason please

@Gusted
Copy link

Gusted commented Nov 12, 2017

issue close!

@JeromSar
Copy link
Member

Perhaps we can figure out a way to roll these back. @Wild1145 any ideas?

@Gusted
Copy link

Gusted commented Nov 12, 2017

Admins can rollback it

Issue close

@Gusted
Copy link

Gusted commented Nov 12, 2017

/ro

@Wild1145
Copy link
Member

Wild1145 commented Dec 1, 2017

@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...

@aokod
Copy link

aokod commented Dec 20, 2017

Use CoreProtect. /rollback is very outdated.

@Wild1145
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants