Pex Help
dehaanjesses opened this issue · 176 comments
I need help with pex prefixes. If you can help me go to ...
] Edit by Stormbow: Server address removed [.
If you need help, post what you need help with as specifically as possible and I'll help you as best as I can.
I don't visit servers unless I absolutely have to, and advertising your server isn't allowed here unless it's absolutely necessary.
If your prefixes are not working:
• Do you have a chat management plugin on the server? If yes, which one are you using?
Are you using "EssentialsChat" or "EssentialsXChat"? ("EssentialsChat" was discontinued at Minecraft 1.8, so it's important to be very specific here. You would need a Spigot server to run EssentialsXChat.)
Do you have Vault installed? (It's required for either EssentialsChat or EssentialsXChat to function properly.)
And I do /pex group Owner prefix &f[&bOwner&f] but then when i type in chat it says [default] in front of my name
Ok, you will need to install Vault.
Do that, test the server, and let me know how it went. :)
Check the config.yml file in the Essentials folder. Make sure it's set to only display one.
If you're using the Multiverse plugin on the server, look inside that config file too because Multiverse also has chat management features which it shouldn't really have. You'll have to disable those. Multiverse is a common cause of double chat prefixes.
It is set to Owner: '&c[{GROUP}]&r {DISPLAYNAME}&7:&c &b{MESSAGE}'
Ahhhh! That's why.
In EssentialsChat, the {DISPLAYNAME} variable is your Prefix+Username+Suffix combined.
To correct the double group name being displayed, you can either remove {GROUP} in the EssentialsChat config file or remove the prefixes that you have defined inside the permissions.yml file.
Oh wait, I took the {GROUP} out and saved it and restarted my server and it still has it 2 Owner's
If you're using the config.yml:
GroupNameHere: '[&5{GROUP}&r] {DISPLAYNAME}&r: {MESSAGE}'
If you're using the permissions.yml file:
prefix: 'GroupNameHere '
(Notice the space after GroupNameHere.)
Oh wait, I took the {GROUP} out and saved it and restarted my server and it still has it 2 Owners.
Be sure to stop the server and start it again. The "restart" functionality of most servers isn't all it's cracked up to be.
In your case— being a 1.8 server —you can use the commands /ess reload and /pex reload while in-game to get these 2 particular plugins to reload. It's a bit faster than stopping and starting the server.
Ok but I got the 2 Owner's to go way but the space, didn't show up
How did you add the space in? Show me your prefix entry.
groups:
Owner:
options:
prefix: '&f[&bOwner&f]'
worlds:
'&a''':
options:
prefix: '''&f[&bOwner&f]'
'&a':
options:
prefix: '&f[&bOwner&f] '
members: {}
defoault: {}
schema-version: 1
users:
eb8c6eec-539d-48ca-a768-91f31f78a0a3:
permissions:
- '*'
group:
- Owner
options:
name: Lion048SB
I added the space for the 3rd "prefix"
All of that &a stuff needs to be removed. Those are incorrect multiworld settings. Only the group itself gets a prefix setting.
Here ya go— start from this file example.
You can see the complete file example, right here, if you want to see all the possible settings and a handful of groups pre-made. You can even use this example as the starting point for your server; the notes about Minecraft 1.9 can be ignored. (A 1.8 server doesn't have to have an inheritance section in every group, but it doesn't hurt at all to have them, and usually makes the file shorter.)
I corrected a typo in http://pastebin.com/Qf5keFWQ.
Yes, copy that one (it's the same as the link in this post) and paste it into your permissions.yml file. Save the file. Then type pex reload into your server console.
Whoops. The typo got you.
Reload this page: http://pastebin.com/Qf5keFWQ Copy that example. Paste it into your file. pex reload into the console.
Just like you see in the "Guest" group I made for you.
Add one blank space before that last apostrophe of the prefix setting.
This isn't about pex but do you know how to set the server spawnpoint?
Since you're using Essentials, you have access to the /setspawn command. Type that in-game and you'll see what the options are for it. :)
One final note:
If you add permissions to that Guest group by editing the permissions.yml file directly, be sure to delete the brackets (the [ ] ) to the right of permissions:. Those are just a placeholder until real permissions get added to a group.
What did you type, exactly?
/setspawn
is the in-game command.
setspawn
can't be used in the console as far as I know.
Page not found.
You have the "EssentialsX" .jar file on your server. You're literally using "EssentialsX" and not "Essentials" as I had originally thought.
Are you running a Spigot server?
That may be part of the problem. You're using the Spigot server versions of Essentials ("EssentialsX") on a non-spigot ("Bukkit") server.
As you can see on this page, there's no official 1.8+ Bukkit or Essentials download.
Yeah. The server host is supplying you with what is essentially an obsolete server wrapper ("Bukkit").
Do they have an option to give you a Spigot server?
Spigot is actually kind of like a child of Bukkit; they're kind of genetically related.
Since Bukkit is Spigot's daddy (they use the same basic genetics, or programming code), Spigot is "backward compatible" to Bukkit plugins and virtually all of the "Bukkit" plugins can be used on "Spigot" servers.
You can even run a Spigot 1.8 server, if you're very dedicated to running that specific version of Minecraft.
Minecraft is currently up to 1.11.2 and PEX 1.23.4 (which you're using) works with that version also.
(PEX 1.23.4 works with Minecraft 1.7.9 through 1.11.2, so far.)
Yep. The only important thing to know about 1.9 and later is that PEX needs an inheritance section in every group. That's when Line 19 of this example for PEX comes into consideration.
Other than that, your permissions.yml file doesn't really change from what you currently have.
(And neither does your EssentialsX config.yml file.)
Well, as we're seeing so far, you're not getting access to the EssentialsX command /setspawn, so a switch to Spigot appears to be a good idea for you— especially since you're right on the very edge of that "no official downloads" issue we talked about a little, earlier..
I'm just trying to avoid later versions because I don't understand the inheritance part
Inheritance is actually quite simple. Let's take a look at my example file and I'll explain it to you.
In the above example, we see that the "Guest" group has a permission node called modifyworld.* (line 12) that lets them do everything there is in the game, thanks to the plugin called Modifyworld. The members of the "Guest" group can move, talk, craft items, pick up items, carry items, hold items, use items on other items/blocks, and interact with everything in the game.
Now, let's look at the "Member" group. Since the "Member" group has an inheritance set to "Guest" (lines 29 and 30), the "Member" group users also get that modifyworld.* permission node that the "Guest" group has, and all of the other permission nodes that "Guest" gets.
If a group (Guest) has something that the other group (Member) does not want or that we don't want them to have, we use something called a "negation" to remove that permission. For example, since we do not want "Member" group users to have access to the "Guest" group's kit, we negate that permission at the top of the "Member" group's permission section (line 32) and we give the "Member" group users their own special kit— essentials.kits.member —on line 33.
There are also actually commands to do all of this stuff while being in-game, but it's typically easier and faster to enter all of this information directly into the permissions.yml file "manually", like you and I have done with previous changes we made to your file.
Does all of that make sense to you? Do you understand inheritances a little better?
They're not so scary, are they? :)
Would it do the inheritances automatically? Or would I have to put it in manually?
You've come this far in learning how to run a Minecraft server; don't stop learning now. :)
You have the example link and this post. (And, of course, you can always ask me questions here.)
I used to have much better guides for just about everything related to PEX 1.x, but since the Bukkit website was reorganized without warning and they disconnected/deleted all of the plugin forums, all of those posts are missing in action now.
Nope. Any of the "options" settings can be blank/empty.
suffix: ''
(2 apostrophes, right next to each other, with no space in-between.)
I only included the Suffix in the example so people could see where to add that extra blank space (like the one that you and I fixed for you earlier).
Absolutely.
I highly recommend deleting all of the fake permission nodes that I put in there— the permission.node.one type stuff.
Would you like to see that example customized to what we have for your server so far?
Here ya go! http://pastebin.com/eWnaiiq3
This file is a perfect starting point for you, on a 1.9 and higher server. :)
(On a 1.7.2 through 1.11.2 server, really.)