WorldEdit

WorldEdit

43M Downloads

disallowed-blocks for //set #copy

LadyCailinBot opened this issue · 5 comments

commented

WORLDEDIT-3312 - Reported by Externalizable

Hi!

I think disallowed-blocks should be integrated to //set #copy and //paste, or generally, clipboards should be checked for disallowed-blocks.

Reproduce:

  • Disallow TNT in the config.yml
  • Be a person without worldedit.anyblock
  • Place TNT
  • First and second position with //wand on the TNT
  • //copy
  • Select a huge region
  • //set #copy
  • Cry because op h0ax

My discussion with PseudoKnight, my thoughts and aruguments can be found on the Forums: http://forum.enginehub.org/threads/disallowed-blocks-for-set-copy.16219/

Love you (づ ̄ ³ ̄)づ

commented

Comment by wizjany

as pseudoknight says, disallowed blocks was only designed for input. support for source/destination masks is currently WIP though so that may allow for this sort of limiting.
on the other hand, we don't suggest giving worldedit perms to people you can't trust anyway.

commented

Comment by Externalizable

@wizjany I understand your concerns regarding the permissions for people I do not trust, however, I configured WorldEdit to work very good. 1 year and nothing happened until now that those kiddies found out how to //set #copy. Is it possible to check clipboards for disallowed-blocks, and would you consider adding this in the future?

commented

Comment by sk89q

It will be added at some point but I am not sure soon. There are currently some higher priority things.

commented

Comment by Externalizable

@sk89q Thank you!

commented

Our stance has since changed, and there is no plan to leak disallowed-blocks any further than input.