Skip to content

Upgrading to v1.1.0

Innectic edited this page Nov 8, 2026 · 1 revision

Upgrading to v1.1.0

Stop the server, back up the database/configuration/profiles, replace the JAR and restart. Use Spigot 26.3 and its required Java runtime; Permissify targets Java 25 bytecode. The API is bundled in PermissifySpigot.jar. The current build does not include Sponge.

Behavior changes

  • Weights replace manual primarygroup and setmain commands.
  • Highest-weight active membership becomes main; names break equal-weight ties alphabetically, ignoring case.
  • Existing groups start at weight 0; previous primary flags are ignored.
  • The default group remains available for players with no active memberships.
  • Direct player rules override group rules; higher-weight memberships win conflicts, with denial winning ties.
  • Help and completion respect command access.
  • RCON requires allow-rcon: true; absent remains disabled.
  • Messages follow the player's client locale with fallback.

Storage

Database migrations add expiry, weight and permission-value columns, plus inheritance, track and audit tables.

Old temporary grants without stored deadlines cannot have their deadlines recovered. Remove and re-add grants that should expire. New deadlines count time offline and while the server is stopped.

Compatible older profiles still load. New saves preserve denied rules, weights, inheritance, tracks and expiry. Imports merge data and do not reset audit history.

Builds and API

Maven was replaced by Gradle. Use ./gradlew clean build or gradlew.bat clean build with the configured Java 25 toolchain.

The standalone API is PermissifyAPI-1.1.0.jar. Integrations using old primary-group methods must migrate to weight-based getMainGroup(UUID) and rebuild against the new API.

Clone this wiki locally