HawkEye Reloaded
NOTE
HawkEye Reloaded is still under active development! Due to many table altering changes we've been making, we've only been uploading new releases to our Jenkins Development build website.
Bukkit 1.7.10 / Spigot 1.8 Users
The current builds on bukkitdev are mostly outdated for builds 1.7.10 and above. I highly recommend you download a development build to avoid issue!
Description
HawkEye reloaded is a continuation of the beloved former "Hawkeye", which is now completely inactive. It gives you the ability to log changes, search through them, roll edits back and much, much more.
Features
- Logging of over 45 different actions
- Worldedit logging
- Smart logging
- Smart rollback/block restoral
- Block filter to avoid logging unwanted material
- Rollback commands with simple-to-use parameters
- Advanced interactive web interface for viewing logs
- Rollback previews - have the rollback only appear to you at first
- WorldEdit selection rollbacks - rollback everything in your WE selection
- Configurable search tool to quickly see edits on single blocks
- Simple, and easy to learn parameters
- Fast efficient logging
- API so other plugins can interact with the HawkEye database
Command List
Command | Description |
---|---|
/he help <Command> | Provides help for the specified command |
/he | Displays a page showing all HawkEye related commands |
/he tool bind | Binds the custom parameters to the tool |
/he tool reset | Resets tool to default properties |
/he tool | Toggles the searching tool |
/he search <parameters> | Searches the HawkEye database |
/he page <page> | Displays a page from your last search |
/he tpto <id> | Teleport to the location of the data entry |
/he here <radius> <player> | Searches around you |
/he preview apply | Apply the rollback preview |
/he preview cancel | Cancel the rollback preview |
/he preview <parameters> | Preview the rollback changes |
/he rollback <parameters> | Rollback specified changes |
/he undo | Reverses your previous rollback |
/he rebuild | Re-apply specified changes |
/he delete | Deletes specified data entries |
/he info | Display important information |
/he writelog <parameters> | Write results to a log |
Permission List
Node | Description |
---|---|
hawkeye.* | Access to all HawkEye commands |
hawkeye.page | Permission to view different pages |
hawkeye.search | Permission to search the HawkEye database |
hawkeye.search.<action> | Specific node to search HawkEye database |
hawkeye.tpto | Permission to teleport to the location of a search result |
hawkeye.rollback | Permission to rollback actions |
hawkeye.tool | Permission to use the HawkEye tool |
hawkeye.tool.bind | Permission to bind parameters to the tool |
hawkeye.preview | Permission to preview a rollback before applying it |
hawkeye.rebuild | Permission to rebuild actions |
hawkeye.info | Permission to view info |
hawkeye.writelog | Permission to writelog |
Requirements
- Latest RB of bukkit
- MySQL database (Your host should provide you with one)
- (optional) WebServer (if you want to run the Web Interface)
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Still have a question?
Still have a question?
Here is an extra help page, which contains things like, format, importation, and errors. If nothing helps, feel free to open a Ticket, explaining your problem will help us recreate, and fix the issue.
Want to Donate?
Want to Donate?
All the donations go directly to the former author oliverw92
I am currently very busy and cannot answer any questions.. I will try to keep all my plugins updated during my absence
@Nistune
I really don't know whether or not i'm going to implement UUID searches.. Seeing as players can change their names, you wont really ever know what your rolling back when typing in a name. Also a lot of the web interface would have to be reworked to work with UUID.
For now, i really don't see any reason aside from global user rollbacks to implement UUID support
@Nistune
Technically the plugin will work just fine without the UUID update fix. Though sure you won''t know if the person changed their player name, but when you ban them, you will ban by their UUID instead.
Love this plugin (Been using it for a good 2 years now) but wondering if there will be an update for the UUID changes? Would hate to switch to something else.
@Foxtrot_CZ
You seemed to know PHP so i thought you already fixed the issue. But the issue lies within the code to "decompile" the chest information. It should be an easy fix, most likely caused by a random space or random letter.
@Liger_XT5
That bug I posted is 9 months old... And there is ticket system full of reported bugs which none is solved. I am grateful that someone is doing this great plugin, but that unsolved bugs are horrible...
@Foxtrot_CZ
If you look at the comments, its not dead, just a lot of work to clean up bugs. Plugins like this does a lot and when a bug shows up, sometimes it takes a lot of work to debug and clean. I honestly havent had any major issues with the web UI, but then again, Im not generally worried about griefing.
What about this plugin? Is it death or what? Do you plan to repair web interface bugs?
Like this: http://dev.bukkit.org/bukkit-plugins/hawkeye-reload/tickets/42-web-interface-showing-wrong-block-names/
@bob7l
true true, what about having an option for using it (in the config files). That way its more fault proof for the future (when you choose that option). And when using the real uuid the minecraft api give i dont see a problem with that part also
true the web interface and hawk search/rollback commands have to be a bit reprogrammed but i think its a smal change with lots of bennefits comparing to other hawkeye like plugins
@janwil
It's hard to say.. Converting to UUID will make the plugin more prone to bugs.. Why? Because for whatever reason a lot of servers have been making custom UUID's per world. Although it truly wouldn't be very difficult at all for us to convert everything, just hard for the interface.
will there be support for the new uuid? instead of player names? And so yes, when? :)
Than i know when i need to change everything
Allot of plugins already have support for that
But's only with emeraldore and diamondore; only players below moderator-rank and no console/log-message appers.
This message is from HE, but why could users without HE-permissions see that message?
HE also logs the blockbreak, nothing unusual.
Ok, I think, I have to check the whole pluginlist.
@Jobsti2
Unable to reproduce your problem: http://i.imgur.com/HKgU3k2.png
I was de-opped and stripped of all my perms.
The possible issue here is....
a) Your HawkEye filter contains the ID's of the blocks, block-filter:
b) A plugin on your server is canceling the event, but still breaking the block
c) A plugin on your server is modifying the break event
All users geht the following Message:
If they break Diamond- or Emerald-ore with a pickaxe.
No problems if the user has the permission - hawkeye-* (moderators)
Permissions-Plugin: PEX (now latest build. also from HE, with CB beta 1.7.9)
I've got this prolbem since:
HEr: #35
CB: #2970
Also installed: latest XBP
Oh btw everyone using bukkit 1.7.9. Please update to the latest dev, it will support your version MUCH better and has some good optimizations.
I've had a few people asking me to compile the latest hawkeye from source - Simply click the "Dev-Builds" link a short ways up from this comment and grab the latest one.
I fixed the latest Hawkeye issue and sent in a PR :) https://github.com/bob7l/HawkReloaded/pull/41
@marubal21 https://github.com/bob7l/HawkReloaded/blob/master/src/uk/co/oliwali/HawkEye/DataType.java
has the action-ccodes
@bob7l Thanks for the reply. btw, would you happen to have a decode for the action codes within the hawkeye table? just something to show what each action code means...
@marubal21
I'm not to sure about this as i am going off my mind atm buut.. I believe Lock wait timeout is thrown when the Cleansing Utility "hangs", or takes to long to remove stuff. Also, please make ABSOLUTE SURE your not running ALL the tables on the same name.. Otherwise you'll get logs from other servers.
Btw - Extending the logging time a bit may help a little with mysql locks
I have 4 servers connected via Bungeecord with each server running its own instance of HawkEye and each connecting to the same MySQL database, it has been working just fine, but today during a scheduled restart i noticed an error message on the logs for all the servers.
ERROR: [Timer-0/ERROR]: [HawkEye] Unable to execute cleanse utility: java.sql.SQLException: Lock wait timeout exceeded; try restarting transaction