CommunityBridge V2.0.0 (build #284)

Details

  • Filename
    CommunityBridge.jar
  • Uploaded by
  • Uploaded
    Dec 3, 2013
  • Size
    86.30 KB
  • Downloads
    534
  • MD5
    3f378acd2b0743acdf96297d9244ee12

Supported Bukkit Versions

  • CB 1.6.4-R2.0
  • 1.7.2

Changelog

Installing for the first time

  1. Copy the jar into your plugins folder. Restart to generate the default config.yml.
  2. Set the log-level to "config".
  3. Configure the player-linking feature for your web application.
  4. Either use cbreload, or reload, or restart the server to load the new configuration.
  5. Make sure you don't see any warnings or errors. Take necessary steps to correct them and cbreload/reload/restart.
  6. Select another feature of CommunityBridge that you want to use and configure it.
  7. Either use cbreload, or reload, or restart the server to load the new configuration.
  8. Make sure you don't see any warnings or errors. Take necessary steps to correct them and cbreload/reload/restart.
  9. ...repeat as necessary.
  10. Gently guide your players toward building a community...:)

Upgrading from a beta release

The best, yet most tedious way, is to copy your current config.yml and messages.yml somewhere else and let CommunityBridge generate the default template files. Then using your old ones as a guide, configure using the new default config.yml template.

Upgrading from 1.x or the alpha releases

You should make a backup of the CommunityBridge plugin directory and then delete it. You'll need CommunityBridge to generate a new default config.yml and work through the configuration carefully as it has changed significantly from 1.x or the alpha releases.

Changes since beta 5

  • Fix: Missing or empty message in messages.yml causes an NPE.
  • Fix: Eliminate command executor duplication.
  • Fix: CommunityBridge mistakenly claims Vault is not enabled. (#112)
  • New: Config option to control the inserted date format. (#79)
  • New: Config option to control whether CommunityBridge uses join message during connect events. (#94)
  • New: Config option to control synchronization during join/quit events. (#31)
  • New: Basic support for zPermissions (depending on configuration, Vault+zPerms may be preferred). (#16)
  • New: cbsync will now take a playername as a parameter.