Re-Adding NBT Paste for ops

> Malicious player creates a chest containing a huge amount of NBT
> Player then saves that chest as multiple schematics with various names to avoid detection
> Player can now create chunkbans extremely easily with these schematics by simply pasting multiple copies

No.

can i make a small request for you to not use polls as consistency wise it kind of irritates me as we got all these suggestions with votes with reasons then we got a poll on something that might actually be of contraversy

speaking of which im not sure if it should be reimplimented because the guys who exploited it are gone so probably not a good idea until it cant do dumbass shit

↩  videogamesm12 This.

I Object.

↩  Zarcana That doesn't fix another issue that isn't caused by oversized NBT.
> Malicious player places a block containing a server-crashing exploit but doesn't use it
> Player then creates multiple schematics with the exploit under various names to make them difficult to find
> The exploit gets blocked off by a plugin like VulnerabilityPatcher, which does not take WorldEdit into account
> Player now has a way to bypass VulnerabilityPatcher and continue to crash the server

This has happened before in 2019, and I really hated trying to track down all of the exploit schematics.

WorldEdit is a clusterfuck to modify and compile. A change like the one you suggested would require a significant amount of effort, and considering the tiny development team we have at the moment, that really isn't feasible.

vouch
bad idea am dumb but maybe some cooldown from bans or other permission thing that can be removed?

Considering how much of a nightmare it can be to keep on track of active crash exploits as it is, this would just make it even harder. It was removed for a reason. It should stay removed for that reason. Object.

Quote

↩  Zarcana not like there's really anyone to use it maliciously because the dudes who would use it maliciously are basically all gone at this point

What's your source for this, lol? Malicious players are always going to join the server.

Quote

↩  Zarcana and if they do use it maliciously, thats why bans exist

Our server isn't actively moderated 24/7. Sure, it might be fine to say "let's unblock it and just punish as stuff happens" in some cases, but not in the case in which a player can easily load and paste schematics to crash players, or worse, the server. Especially when, even to an active staff member, seeing someone innocently pasting schematics (unless they're named servercrasher.schem which they might not be) is not an immediate red flag.

So yeah, it's better to just.. not let people create easy crash chunks.

Quote

↩  Zarcana i see no reason not to add NBT paste back into the game for everyone to use.

Should've gone to Specsavers

object lol

this has been suggested soo many times

If someone can provide a sane solution to re-enable NBT that The dev team, @"videogamesm12"#4 and @"Panther"#54 are all content with (Because I sure as hell don't know enough about NBT to be an authority on the matter) then we can roll with it, but that is and continues to be my position on the matter. I don't mind re-enabling it, but we need to be able to safeguard the server...

↩  videogamesm12 My understanding is that the permission node worldedit.setnbt blocks NBT while applying edits (e.g. //paste), not when saving to clipboard or file.

If that's true, we might still have malicious schematics around but only staff members can accidentally harm the server with them. Better than nothing, I guess.

Bump again because I've not seen a good answer to my last question, and want to give folks half a chance here.

i can see this being done in a sane way if we fork worldedit to have our custom checks in the paste and schem loading functionalities. because we use AWE (closed source) that's not possible from the plugin itself.

it could work if we could explicitly whitelist which blocks to support nbt paste, and if panther is willing to advise about it. containers are the obvious bad guys but if we don't use a whitelist i'm sure something like beehives would slip through the cracks.

vouch if an actionable solution is presented

↩ @'Ryan' How about a playtime limit? Kind of a "You need X hours of playtime to unlock this feature". I doubt a ill-attentioned person would spend a day or two of game time just to unlock NBT pasting.

Otherwise, since the Master Builder has been recently deemed to be a "display of skills" they could be awarded that permission.

Or as a third option, we could set a upper limit for NBT, something like "x kb per block".

The last thing I could think of is applying for NBT paste. Having a hidden "rank" (kind of like how discord handles roles and permissions?) that grants you access to that and to which you can apply to by simply asking. Were you to abuse that, an admin will remove your extra worldedit permissions and sanction you.

↩  Folfy_Blue can tell you prior. those first two proposals wont fly here. cant give more perms to people who are not admin

Quote

↩  Folfy_Blue Or as a third option, we could set a upper limit for NBT, something like "x kb per block".

The last thing I could think of is applying for NBT paste. Having a hidden "rank" (kind of like how discord handles roles and permissions?) that grants you access to that and to which you can apply to by simply asking. Were you to abuse that, an admin will remove your extra worldedit permissions and sanction you.

Any further input on these two suggestions? Given this was already bumped by Ryan a week ago, this will probably be the last window for discussion before an approved/denied tag is applied.

↩  RedEastWood

1. A size limit would not protect against schematics with embedded exploits (e.g. crash exploits), like I've said before.
2. A hidden rank that gives players more permissions than other players doesn't really make sense for a server like TF.