THE OLD CONFIGURATION FILE MUST BE DELETED OR MOVED TO A NEW LOCATION! ALL THE SIGNS WILL REMAIN, BUT THE GATES HAVE TO BE REGISTERED AGAIN.

Note: Independent on what stands on the sign, the one registering the sign will be the owner. Make sure the gates go to the right owner!
Note: Q: Register the gate? A: Just right click it!

• * Increased performance and reliability of mostly everything.
• * Changed permissions
  • + gates.command.setowner
  • + gates.command.setgroup
  • + gates.command.setredstone
  • + gates.destroy.player.*
  • + gates.destroy.group.*
  • + gates.use.player.*
  • + gates.use.group.*
  • + gates.destroy.player.[username] (Dynamic)
  • + gates.destroy.group.[groupname] (Dynamic)
  • + gates.use.player.[username] (Dynamic)
  • + gates.use.group.[groupname] (Dynamic)
• * Changed configurations
  • * Changed the split string from - to , in the gates list.
  • + Added a option for default group.
  • + Added a option for default redstone state. (OFF by default)
  • + Added real support for instant gate open/close.
  • + Added group configurations, with global as fallback, if the particular configuration was not found.
• + Added a group system for more permissions and configuration options for each gate.
• + Added redstone support, off by default.
  • ! Activating gates with redstone does NOT support ANY permissions. You have to use third-party plugins to handle redstone permissions.
  • + OFF - Redstone will have no effect on the gate. (Default choice)
  • + ON - The gate is open when it's powered, otherwise closed.
  • + TOGGLE - The gate will toggle on every redstone input.
• + New command syntaxes.
  • ! To apply these settings, you have to Left Click (or Damage) the gate sign.
  • + /gates setowner [username] - Change the owner of a gate.
  • + /gates setgroup [groupname] - Change the group of a gate.
  • + /gates setredstone on|off|toggle - Change the redstone state of a gate.
• - Fixed a issue where destroying another players gate would cause the gate to load on next reload of the plugin, causing errors as the sign wouldn't be there.
• - Fixed a issue where negative coordinates for a gate would send errors, as I did split the gate information with "-" inside the gates.yml, it would cause problems.