Bukkit

Version 1.12.1

• Tested for compatibility with CraftBukkit 1.4.5-R1.0.
• Some (but not all-encompassing) testing for compatibility with CraftBukkit 1.4.5-R0.2.
• Added error check to ensure that if PEX is used, it is a high enough version for the version of CraftBukkit in use. (PEX1.19.5 or better on CraftBukkit 1.4.5-R1.0 or later).
• Added some safety checking to ensure the specified permissions plugin is in fact present and enabled.
• Fixed issue where the autosync and autoreminder tasks would not update their settings during a reload.
• Fixed issue where the autosync would generate an error after a reload.
• Fixed issue where the player linking wasn't logged if group-sync was off.
• Fixed issue on PEX where CommunityBridge would mishandle inherited groups (bugfix submitted by BangL. Thank you!).

Changes from 1.11 To be Aware Of

Details about the logging levels

# Log level controls the degree of detail that is sent to the console/log
# The possible settings are (in order of quietest to noisiest:
#   info, config, fine, finer, finest, all
# - During configuration, I recommend using 'config'.
# - During normal operation, I recommend using 'info'.
# - If you want to see the notifications that the synchronize and reminder
#   notices have been sent, use 'fine'
# - During troubleshooting of problems, set this to either finest or all.
log-level: config

Details about the new group-synchronization options

group-synchronization:
  primary-group:
# If this is set to false, primary group synchronization will not happen.
    enabled: true
# If a user's group ID on the web application side is on this list, it
# won't be synchronized. Example: ['1','2','3','115'], use [] for an empty list.
    group-ids-to-ignore: []

Known/Confirmed Bugs

• CommunityBridge does not release all the resources it should during a reload or onDisable.
• Configuration Analysis will not catch the error if the specified table for statistics tracking is incorrect.
• MySQL Column names that are the same as a MySQL reserved word will cause the relevant MySQL queries to fail.
• Under very specific conditions that are rarely used, the user will not be notified that the game knows they are registered, even if notify player is on.

None of these should be a major problem for anyone. Mostly, they apply to such specific combinations of configuration settings that most installs will not notice.