v0.5.5b

Details

  • Filename
    rscPermissions_v0.5.5b.jar
  • Uploaded by
  • Uploaded
    Sep 20, 2013
  • Size
    65.77 KB
  • Downloads
    271
  • MD5
    597a0802362f78c272d4e67fb2746bd2

Supported Bukkit Versions

  • 1.6.4

Changelog

v0.5.5b (should work with server versions 1.4.x - 1.6.x)

  • There are many bug fixes from minor to critical.
  • Added command /rscp examplerows to generate examples in db (but only entities at now).
  • /rscp reload now completely disables and enables plugin; config.yml is also reread.
  • Localizations for maintenance modes thought config.yml. Read Pages/Configuration for some details.
  • When Rewards are enabled, players will see list of available rewards for self after login.
  • Third-party plugins are able to setup prefixes and suffixes though Vault.

v0.5b

  • Maintenance mode works on 100% — now saving state into config.yml and kicks all players without permissions.
  • Vault integration removed. Otherwise, I forked Vault and added hook for rscp; waiting for Pull Request acception. After that chat prefixes and suffixes will appear. My own build of the latest Vault + my code can be downloaded here.
  • Rewards started: work with commands and permissions only; currently they are infinite — column `activated` not changing in db. Conditional inheritance from groups will be implemented later.
  • Bans and Rewards become optional features; disabled by default (you can enable them in config.yml).
  • Little performance improvements, bug fixes and refactoring.
  • Tested a little bit on 1.6.2, I see no any problems.

v0.4.5b

  • Fixes in building inheritance tree. Sometimes players haven't any permissions.
  • Added base permission calculation at onAsyncPlayerPreLogin event: region, world and expirience are unknown and interpreted as nulls/zeroes. Without that some plugins were unable to find permissions and allow player connection (MaintenanceMode, maybe some ban or whitelist plugins, etc).

v0.4.4b

  • Fixed a way to live with Vault together due to BDO recommendations.

v0.4.3b

  • Breaking change: renamed some configuration nodes: autoreloaddelaysec to auto-reload-delay-sec, defaultgroup to default-group, metrics to use-metrics; added boolean treat-asterisk-as-op (true by default). This was done is the aims of readability.
  • Added configuration option settings.region-finder-thread-granularity-msec that determines how ofter parallel thread will rescan players for being in WG regions. Hardcoded limits are 20 (lower) and 10000 (higher), default value is 1000 (1 sec).
  • Implemented commands /rscp lock [maintenancemode] and /rscp unlock. At now it doesn't kick online players but prevent others from logging in. To allow player log in give him rscp.maintenance.<maintenancemode> or rscp.maintenance.* permissions. Ironically, the default maintenance mode is called "default". When maintenance is enabled testing of a player's permissions is made in event's thread and results in some insignifficant delay during logging in.
  • Vault is now truly optional — no more exceptions at startup if you haven't it.
  • Minor performance increases; more thread-safety; little bug fixes.

v0.4b

  • Group prototyping working! Perhaps we should create page to describe it in details...
  • Prototyping symbol # changed to ?.
  • Breaking change: all permission nodes renamed from rscPermissions.blablabla to rscp.blablabla due to simplicity and shortness. However, only one permission was implemented earlier (reload) ...
  • Breaking change: list of MySQL servers in config.yml is now realized as a list of hashmaps. This gives the ability to setup any reasonable number of permission sources. Look at Pages/Configuration to see new format. Testers of v0.3.2b can see old format in their config.yml.
  • Asterisk permision * gives OP! But if you set some permission values to false (zero) - OP will not have them (Bukkit's behavior!).
  • Removed debug message "ThPrmUpd" to the players whose permissions were recalculated.

Latest Vault release still doesn't support rscPermissions, but you can download it's sources and compile them yourself or download .jar compiled by me.

Use on production servers at your own risk.
Since project started I have no one report about errors so I think it is quite stable, but firstly make some tests on private servers, please. Hovewer, if you have tested it and it shows good stability you can use it as you want, but tell me that it really stable. I should to know it!

The only in-game/console commands available:
/rscp lock | unlock | examplerows | reload — admin features.
/reward — player features.

Because of data editing commands are not ready yet (and is not a priority task) we recommend you to use any comfort SQL editor like:

  • phpMyAdmin (requires web-server with PHP interpretator)
  • MySQL Workbench (free official GUI tool with Excel-editing-style (mouse right-clicking, etc) for Windows)
  • Any other, I don't know. Write your own toolset for this =)