SolusRpg

After a long wait, here it is! :)

Changelog

• A HUUUGE overhaul to the damage calculation system (read: more accurate/faster)
• Added the 'immune-to' directive for class configuration (see the Configuration Directives page for more info)
• Skill system is enabled! I'll have an API documentation page written for developers soon
• Added support for display name changing (see the List of Commands page for mor info)
• Moved the 'whois' commnd to "/solus whois <player fragment>"

From this version forward, SolusRpg will prevent all player actions until Spout has been validated. This means that when a player connects to your server, they will (most likely) be greeted with a mass of text from Solus saying that their login request is still being processed. I'm currently working on a way to make this a bit "prettier", but until then, please bear with me.

Why did I do this?

Solus relies very heavily on Spout for the majority of it's functions and features. During the grace period between connection and validation, a player is capable of completely ignoring the permit nodes set up for their class. By preventing all player action until Spout can be verified, I've removed any chance of a player circumventing SolusRpg's restrictions.