[DISCONTINUED] EssentialCmds [v8.1.14]

Release v8.1.4:

Tested on SpongeForge 1326

Changes:

  • Added a specific permission for using /kill on other players - essentialcmds.kill.others

Enjoy this Update! :smile:

2 Likes

You can safely ignore that - it wo’t affect anything.

1 Like

How to enable the prisoner in jail to eat? And open chests?

/broadcast how to make a line break?

The mobspawn command seems to be a bit broken at present. This happened on the SCS, using SV 1.8.9-4.1.0-BETA-306, EssCmds 8.1.4:

[11:00:14 ERROR] [Sponge]: Error occurred while executing command 'mobspawn 1 minecraft:creeper' for source EntityPlayerMP['Inscrutable'/1437, l='survival', x=198.13, y=71.00, z=495.00]: SpawnEntityEvent MUST have a SpawnCause as the root! java.lang.IllegalArgumentException: SpawnEntityEvent MUST have a SpawnCause as the root!

@Inscrutable

Okay, I’ll fix it today. Thanks for reporting it

1 Like

Release v8.1.5:

Tested on SpongeForge 1329

Changes:

  • Bug fixes for commands that spawn entities - they now use a SpawnCause.

Enjoy this Update! :smile:

2 Likes

This happens now that I added nucleus to the server… when i remove both nucleus and essentialscmds its fine but now i cant even log into my server without the client crashing and throwing this error when i do have nucleus and/or essentialscmds added… I’ve tried deleting every source of player data i could find to try and reset this but nope still crashes.

Edit Reason Found: Due to the server being hooked to a bungee; and the bungee happend to have randomly thrown me into vanish mode which enabled a potion effect that I was not aware of; it would crash the client every time I tried to join the sponge server that had either essentialscmds or nucleus on.

I need permission for warp for player. essentialcmds.warp.use is not working for warp player.

Well essentialscmds.warp.use is to allow the player to access the /warp <name> command. You need first to set it with /setwarp <name>. Is this what you are referring to and what you are using? Ensure that if you are using PEX, you have correctly placed the pemission node in.

Release v8.1.6:

Tested on SpongeForge 1343

Changes:

  • Added /me and /say to prevent players from bypassing mute with the vanilla version of these commands.

Commands:

  • /me <message> - Broadcasts a message in the format * <player name> <message>
  • /say <message> - Broadcasts a message in the format [<player name>] <message>

Permissions:

  • essentialcmds.me.use
  • essentialcmds.say.use

Enjoy this Update! :smile:

Can’t they just do /minecraft:me and /minecraft:say?

most players won’t know this though

either way the best thing to do is just disable those two minecraft commands in pex

1 Like

yeah but now players can do /me (essentials version) so that mute works and you don’t give them permission to use the /me (minecraft version) so /me is usable but also now works with mute.

1 Like

Hi, i think im just a noob at this but only ops have access to any of the commands? lower ranks cant do /spawn ect. I know im probs not doing something right but if anyone could help me that would be amazing

Probably there is something with your permission file. If you are using PEX, you can go over that thread first.

If there is still issues, we can help you out over there

Can you add a chat feature to /sudo? Somthing like /sudochat or /sudo <name> c:<message>

Sure, will do soon

Hi ! We’re encountering some problems :

  • First, we don’t have any colors in chat, event with color codes.

  • Then, can you do something for fixing colors on names ? Like you did for Prefixes ^^

  • And finally, is there any solutions (When the colors will work), to speak in a permanent color for a Grade, like Moderators in green or Administrators in red, without putting at the begining of every sentences a code ?

Thanks a lot for the plugin btw :slight_smile:

You need permission to do colors in chat

colored names can be done in pex… /pex group ExampleGroup options namecolor yellow