OpGuard v3.2.0

Download

Details

  • Filename
    OpGuard-3.2.0.jar
  • Uploaded by
    View RezzedUp's Profile
    RezzedUp
  • Uploaded
    Jan 12, 2017
  • Size
    88.34 KB
  • Downloads
    565
  • MD5
    c9f32049fa804d8ee87a171ead6ee82a

Supported Bukkit Versions

  • 1.11
  • 1.10
  • 1.9
  • 1.8.1
  • 1.8
  • 1.8.3

Changelog

Update 3.2.0 "The Compatibility Update"

 

Update log from: https://github.com/RezzedUp/OpGuard/releases/tag/v3.2.0

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>.