In Game Name:

Kozz​

What part of EcoCityCraft is this suggestion for:

Main Server​

Short title for your suggestion:

Disable '/pt clear', or make it '/pt ci'​

What are you suggesting:

Either remove the ability to add 'clear' to a powertool, or configure it so you must type '/pt ci' to actually clear your inventory.​

Why is this a good addition for EcoCityCraft?:

Powertool noob here. Intuitively typed '/pt clear' on my enchanted pickaxe under the impression that it would clear the commands on my pickaxe.

Low and behold, next time I went mining all my items disappeared. 'What a bug this is! Ahh well, let's try again!'

I enchanted another pickaxe, and went to mine again.
I hit a block. There goes all my items again! RIP.

Not until I inquired about it had I realized that typing '/pt clear' binds 'clear inventory' to your powertool. Usually this requires confirmation, but as I binded it to my pickaxe that confirmation was given instantaneously when I held it down.​

Other information:

I know it's my fault for being silly, and looking back it's quite hilarious honestly. I should have read up more about it.

That being said, this is a dangerous command that is not necessarily noob friendly. I feel I'm definitely not the only person who has made this mistake.​

Plugin or custom addition:

Powertool​

One suggestion per form:

I Understand.​

 

Ahh shucks.
I don't necessarily think you have to be "an idiot" to attempt '/pt clear'.
It's pretty intuitive and very easy to assume it does what it sounds unless explicitly thinking about it.
IMO, the powertool commands could be better defined.

Edit:
I was actually reading up on the Powertool wiki.
https://dev.bukkit.org/projects/powertool

I'm not sure if this is actually what the server uses, but from their documentation:

• /powertool clear — Clears all bound commands from the current item.
• /powertool clear <item-id-or-name> — Clears all bound commands from the specified item.
• /powertool clear -a — Clears all bound commands from all items.

So either another plugin is used, or this command has actually been overrided to produce this behavior.

Nonetheless, I was unaware this suggestion has already been denied. I will consider this one as such.