CommunityBridge

Version 1.09

• Feature: The unit of time used for remind-every and sync-every can be configured to be either ticks, seconds, or minutes. The default is ticks.
• Feature: Slightly more verbose output when a database error occurs. Hopefully, this will help us with troubleshooting.
• Feature: You can now specify additional columns/fields that CommunityBridge will insert _formatted_ versions of the statistics tracking information. You must have the unformatted fields/columns configured correctly for the formatted ones to work. This will greatly ease the 'forum side' of the setup, especially for those forums that have a built in mechanism for adding custom profile fields. There is a real possibility that such forums will not have to do any forum side modifications, depending on how the forum handles custom profile fields. Setting the options to the correct key/field/column will turn on the feature. Leaving them out of the file, or setting them to

  ''
  

  , will disable the feature. You can count on gametime and lifeticks not exceeding 60 characters, so a field 60 characters wide will be sufficient for those fields.
  • (If you're NOT using multi-tables-use-key)
    field-lastonline-formatted-field
    field-gametime_formatted-field
    field-currentxp-formatted-field
    field-lifeticks-formatted-field
    
  • (If you ARE using multi-tables-use-key)
    field-lastonline-formatted-key-value
    field-gametime-formatted-key-value
    field-currentxp-formatted-key-value
    field-lifeticks-formatted-key-value
    
  • And a sample of what they insert:
    lastonline: 2012-09-16 01:41:07 AM
    gametime: 3 days, 8 hours, 47 minutes, 57 seconds
    currentxp: 83%
    lifeticks: 3 days, 8 hours, 47 minutes, 57 seconds
    
• Fixed: Minecraft usernames were case sensitive. Previously, a player with the name cRaZyCaSe who told the forum their name was crazycase would would not be seen as same player.
• Fixed: The last group listed in config.yml wasn't being read correctly, and a null group was being added at the beginning of the list.
• Fixed: If basic tracking was enabled but none of the tracking fields were enabled, an error would occur. Basic tracking now turns itself temporarily off in this situation. A brand new install will default to basic tracking being turned off.
• Fixed: Fully filled out the information in plugin.yml. Other plugins rely on this information to determine what commands to display in help. This should work correctly now.