✓ SexyPex [Network Wide Ranks with PEX] 1st leak ever 1.2.1

spigotmc link: https://www.spigotmc.org/resources/sexypex-network-wide-ranks-with-pex-no-longer-for-sale.6512/
Tested Minecraft Versions:

• 1.7
• 1.8
• 1.9
• 1.10

Why the high price?

Support via IRC at #ryred. I may be asleep, but it will be the fastest method of contact if I'm at my pc, along with teamspeak at talk.spigotmc.org.



Now supported by BungeePEXBridge! Thanks to PhilipsNostrum! <3

Where I was using a fork of PermissionsEx, I was unable to upload it here due to licensing issues. So I've had to make it into a plugin..

This PEX backend allows for your users to be controlled via a database. And the groups to be controlled via permissions.yml.


Why use SexyPex over the default MySQL backend
By default, PEX stores groups & permissions entirely in the MySQL database. While this is intentional by design, it becomes unnecessary over a large-scaled network overtime as you stack permissions for every group to be used by each server. Your player doesn't need Plot permissions while on a minigame server, do they? Keep all your groups organized per-server via permissions.yml while allowing your users to sync on MySQL and remain scalable and tidy.
A configuration such as this also allows servers who aren't Bungee/multi-server to take advantage of MySQL while being able to easily manage their permissions and groups within' permissions.yml without having to use overly complicated in-game commands or modifying the actual database, which at times, isn't deemed user friendly.
Provided by @Log1x

INSTALLATION

1. BACK UP PERMISSIONSEX FOLDER!
2. MAKE SURE YOU'VE BACKED UP!
3. Make sure all servers have IP Forwarding synchronized (keeps all the UUID's the same)
4. Drag this into plugins folder.
5. For now you've got to use this version of PEX. Fixing it soon!
6. Restart server.
7. Edit the PermissionsEx/config.yml
8. If you're lazy do the following else see 7.
   1. Change the backend to sexy.
   2. Reboot the server.
9. Add your database credentials. (See here)
10. Change the backend to sexy if you haven't already done so.
11. Restart the server
12. [DONE] Unless you want to import the file.
13. Go into server, and do /pex import file

Example Configuration
File: ${SERVER_ROOT}/PermissionsEx/config.yml
Code (Text):
multiserver:
use-netevents: true
permissions:
debug: false
allowOps: false
user-add-groups-last: false
log-players: false
createUserRecords: false
backend: sexy
informplayers:
changes: false
basedir: plugins/PermissionsEx
backends:
sexy:
type: sexy
file: permissions.yml
uri: mysql://localhost/DatabaseName
user: root
password: alpine
updater: false
alwaysUpdate: false

NOTE:
If you wish to use UTF-8 chars such as '❤' you need to ensure the following is done...
In the config.yml where your uri is, ensure it has ?useUnicode=true&characterEncoding=UTF-8 in the URI args.

It should look similar to the following...
Code (Text):
uri: mysql://localhost/ryred_co?useUnicode=true&characterEncoding=UTF-8

Disclaimer
So here's the deal. We use UUID's from http://uuid.ryred.co/ to get and broadcast a slightly personalised message about certain users. These users have earnt their place here however if you wish to disable this feature create the file ryred_co in the server root. The source for this is on github, named UUIDServlet, and UUIDCredits. This should not affect how the plugin works.