OpGuard release v3.2.5

Update 3.2.5

Update Log:

• Add toggleable 'management' permission
  • By default all OpGuard commands are only executable by verified operators and console.
  • If use-opguard-management-permission-node is enabled in the config, players with the permission node 'opguard.manage' will be able to execute OpGuard commands (regardless of verified operator status).

OpGuard release v3.2.4

Update 3.2.4

Update Log:

• Remove special characters from random permission node generation.

OpGuard release v3.2.3

Update 3.2.3

Update Log:

• Allow exempt plugins to grant players access to all permissions.
• Non-exempt plugins that attempt to grant all permissions will now be disabled, renamed, and however else OpGuard is configured to handle them.

OpGuard release 3.2.2

Update 3.2.2 "Clutter Cleanup"

Update Log:

• Build against Spigot for 1.12
• Remove all event and command injections.
  • Remove the infamous PlayerWrapper once and for all.
• Remove command exemptions.
  • Command exemptions are no longer needed because commands simply aren't injected anymore.
  • Plugin exemptions still do exist, however, to allow other plugins to execute /op, /deop, and /opguard.
• Remove PlugMan dependency.
  • Automatic PlugMan exempting is now done with reflection.
• Cleanup the config.
  • Remove the 'experimental' config options, since they mainly revolved around event injections.

OpGuard release v3.2.1

Update 3.2.1 "The Opt-In Update"

Update Log:

• From this point forward, all injection-based features will be disabled upon installing this update. If you wish to continue using these features, simply re-enable them in the config (opting in).
  • inject-player-commands and inject-player-events will be set to false even if you're just updating OpGuard.
  • They have been disabled because they were deemed too unstable; several plugins break with these features enabled.
• Add support for bStats metrics, since mcstats hasn't been up... in a very long time, to say the least.
  • Any metrics collecting can be disabled via the config.

OpGuard release v3.2.0

Update 3.2.0 "The Compatibility Update"

Update Log:

• Pass player object hash codes.
  • (fixes issue #10, using pull request #6)
  • OpGuard's WrappedPlayer class now forwards the underlying Player object's hash code instead of its own.
  • Fixes compatibility with many plugins that use Player objects as keys in maps.
• Add plugin exemptions.
  • (highly requested feature and fixes #9)
  • Enabled by default, with PerWorldPlugins as the default exempted plugin.
  • When a plugin is in the exempt list, OpGuard will:
    • Automatically exempt all of its commands as if they are in the exempt-commands list.
    • Allow it to set and remove op.
    • Allow it to run /op, /deop, and /opguard on behalf of players.
      • 
      • Though, OpGuard will still block /op and /deop.
      • OpGuard just ignores the fact that a plugin forced the player to run the command.
  • If plugin exemptions are disabled but a plugin that's in the exempt list is loaded on the server:
    • OpGuard will send a warning to the console at startup.
    • The plugin will be treated like any other plugin.
      • Commands won't be exempted, unless they're defined in the exempt-commands list.
      • If the plugin does something that OpGuard prevents (like op a player, for example) OpGuard will warn about the plugin being exempted but continue with plugin-attempt mitigation.
• Update command exemptions.
  • To accommodate for plugin exemptions, the command exemption system has also been updated.
• Remove 'opguard.manage' permission.
  • It was a completely redundant permission node.
  • /opguard may only be run by verified operators and console.
• Add plugin update checks.
  • According to http://mcstats.org/plugin/OpGuard, several servers still run outdated versions of OpGuard.
  • When an update is found (using Spiget), a message is sent to the console with a download link.
    • This should help remind users to update OpGuard whenever one is available.
  • Update checks can be disabled in the config.
• Add Java 8 check.
  • Once again, according to http://mcstats.org/plugin/OpGuard, a few servers didn't get the memo that OpGuard requires Java 8.
  • If OpGuard is loaded onto a server running a Java version below 1.8, OpGuard will disable itself.
• Add automatic PlugMan exemption.
  • If PlugMan is loaded, OpGuard will automatically add itself to PlugMan's ignored plugins list.
  • This can be disabled in the config.
• Update config.
  • A complete rearrangement of the config.
  • Config option descriptions were updated to add clarity.
  • The config now has a link to OpGuard's support server on discord: https://discord.gg/E4dzuQ7
  • A motivational message was added to the top of the config.
  • Added:
    • All config options mentioned above (exempt-plugins list, update checks, etc).
    • Options that toggle event and command injections.
      • WARNING it is recommended to keep these enabled at all times.
      • They're very important to the functionality of OpGuard.
  • Old configs will now be renamed to config.yml.backup-v<config version>.

OpGuard pre-release v3.2.0 beta 1

Beta Release

This release is for testing purposes only and should not be used on a production server. Please report any bugs found as a new issue.

Update Log:

• Player object hashcodes are forwarded by WrappedPlayer (fixes issue #10, using pull request #6)
• Add plugin exemptions (fixes #9)
  • Automatically exempts all commands defined in the plugin (as if they were in the exempt-commands list)
  • Allows the plugin to set and remove op
• Rearrange and update the config
  • Add options relating to plugin exemptions
  • Add options that toggle event and command injections
  • Add option to automatically exempt OpGuard from PlugMan

OpGuard release v3.1.2

Update 3.1.2 - Vanilla Commands Patch for 1.11

• Fix compatibility for all vanilla commands on Minecraft 1.11.
• Other small (super tiny) fixes.

OpGuard release v3.1.1

Update 3.1.1 - Vanilla Commands Patch

Fix the minecraft:<command> variant of each vanilla command.

OpGuard release v3.1.0

Update 3.1.0 "The Improvement"

Fixed issues #3 and #4.

Update Log:

• Fix compatibility with vanilla commands.
• Update config.yml
  • Add only-deop-if-online option.
    • The default value is false so that offline verified operators can have op removed.
    • That way, for example, if you have a rogue staff member, they can be deoped while being offline.
  • Add exempt commands options.
    • OpGuard may interfere with some commands, so adding commands to the exempt-commands list will prevent errors caused by Opguard.
    • The enable-exempt-commands option must be true in order for the exempt list to work.
    • All vanilla commands will always be exempted.
  • Add config list migration.
    • Before there was no need for list migration, but it's certainly necessary now with options like punishment-commands in the config.