info/v0.2

Alright, v0.2 is released. To further explain some of the additions, I decided to add a page only for those changes.

1) SQL

There is no database needed any more. Please remove your databases (starting with "clasranks_") / the .db file.
Classes and Ranks are now defined in the config.yml, here is a simple example:

After loading the plugin for the first time with v0.2 you should see this in your config:

classes:
    Fighter:
        Warrior: 'Warrior I:&7'
        SWarrior: 'Warrior II:&7'
        MWarrior: 'Warrior III:&8'
    Business:
        Trader: 'Trader I:&a'
        STrader: 'Trader II:&a'
        MTrader: 'Trader III:&2'

The first layer defines the classes. They are only needed to actually JOIN the class, ranking is done without naming the ranks (except for admin commands!)
The second layer defines the ranks. [permissionName]: [DisplayName]:[ColorCode]

2) Multiple permissions systems (now optional!)

ClassRanks natively supports:

  • bPermissions
  • PermissionsEx
  • Permissions (2.7) - and all plugins emulating this version
  • SuperPerms

Default, even if something other is found, will be SuperPerms!

3) SuperPerms support => no Plugin needed

Here is an own description of how to use ClassRanks without any Permissions plugin. Simply check out the config.yml for the first time. If you need to adjust it because you have a hell lot of players, see the players block:

players:
    Notch:
        Fighter: Warrior

This should be clear. The first layer contains the player name, the second layer [classname]: [rankname], it's that easy :D

If you don't use any Permissions plugin, you might want to note that - of course - adding people to a group has actually no effect on them other than checking what group they have in other plugins. So no plugin that does not hook into ClassRanks knows about the ClassRanks group, so ... you should know that ;)

4) Debugging

If I need your help with debugging, you can now set a value in the config: debug: true will enable a hell lot of console spam to determine the happening of an error :)

Well that's it, I hope you enjoy the new version, the SQL database was quite overpowered in relation for what I used it, and the rewrite fixed some bugs, and it is nice to have a plugin covering multiple - if not all - permissions plugins, so I dont have to fix 3 plugins when i have 1 error :D


Comments

Posts Quoted:
Reply
Clear All Quotes