FoundOres Revisited
FoundOres Revisited
Version: v1.8
(Follow me on Twitter for updates!)
FoundOres Revisited is a revisited version of FoundOres.
Due to FoundOres going inactive I continued the project so it could still be used.
FoundOres Revisited is a plugin which lets server admins watch the ores players break. It's used to act against cheaters and x-rayers.
FoundOres Revisited will count all ores a player breaks and a server admin can get the amounts and their allowed percentage.
The old FoundOres can be found here.
Features:
- Counts the broken ores of a player
- Allowed percentages change colour when they reach maximum.
- Very lightweight
- Very simple commands (No learning to do)
- In-game changelog
- Permissions
- Easily create a report with bad players!
- Announce mode
- Multiworld support
- Interval saves
- Disable worlds to choice
- SQLite support
- Custom leaderboards
- MySQL support (online saving)
Permissions:
- - foundores.check Allows to lookup the info about a player.
- - foundores.clear Allows to clear all info about a player.
- - foundores.list Allows to get a list of checked players.
- - foundores.report Allows to create a report with likely to be x-rayers.
- - foundores.notice When Announce mode is on, players with this permission will be notified when a player finds configurable blocks.
- - foundores.remove Wipe all data about a player.
- - foundores.forcesave Allows to perform the '/fo save' command.
- - foundores.reload Allows to perform the '/fo reload' command.
- - foundores.purge Allows a player to purge the database.
- - foundores.materials Allows a player to perform '/fo materials' command.
- - foundores.top Allows a player to perform '/fo top' command.
- - foundores.updateMySQL Allows a player to update the MySQL database to the correct version.
Commands:
- /foundores Shows some info about FoundOres Revisited.
- /fo Alias to /foundores.
- /foundores check <player> <world> Shows broken ores count of a player.
- /foundores clear <player> <world> Resets count of broken ores of a player.
- /foundores help Shows a list of commands.
- /foundores report Creates a report with likely to be x-rayers. (Very handy for big servers)
- /foundores list Shows a list of checked players.
- /foundores remove <player> Removes player from all lists and deletes all data.
- /foundores save Force a save.
- /foundores reload Force a reload.
- /foundores purge Purge database.
- /foundores materials Get a list of materials.
- /foundores top <material> <world> Shows a leaderboard of the top ten highest ratio's.
- /foundores update Updates FO:RE to the latest version.
- /foundores MySQLupdate Converts the database to the latest version of Minecraft.
Pictures:
Broken ore count info about player Staartvin in world 'Quest_World'.
Donations
I'm a poor student and I'm developing this plugin in my free-time, if you like my plugin and want to help me, please donate. Donating is the best way to help me out, it goes towards more bug-fixing. Thanks! Donate is in the top right corner. ;)
Donators
Thanks to all the people who donated and downloaded this plugin! I love you all! <3 Especially thanks to my donators who gave me that little boost:
- - Rodier for donating 5 dollars
- - Rilesthegiles for donating 1 dollar
- - FaxionMC server for donating 40 dollars (!!)
- - Timo Triisa for donating 30 dollars (!!)
- - alek4032 for donating 5 dollars
Do you want to have a special spot on this page and in the '/fo donators' command? Donate! Any amount is appreciated!
@Staartvin
ahh ok thanks, anyidea about the error?
@semirotta
/fo report creates a report in the /foundores revisited/reports/ folder. This report will show all players that have suspicous activity.
Works fine in 1.6.2. (Pytohost servers)
How does the /fo report work? Is it meant to be /fo report PLAYER, it reports the player whom name there is?
ERROR:
http://pastebin.com/7BTL13n8
@KignArthurVII
The higher a percentage is, the more is mined from that block. FO:RE uses warning colours to make it more readable for humans. A green percentage means that this is normal behaviour for a Minecrafter. A yellow colour tells you that this player might be hacking and that you should keep an eye on him/her. The red colour tells you that it is very likely that this player is hacking.
Alright, help me out here. What does a higher/lower percentage indicate? What does the highlighted number in red indicate? Thanks.
@Narimm
I checked my code and I saw indeed that I did not have a check if they connection was closed. I have added this and it will be in the next update.
@Staartvin
It isnt that big for a mysql database really...
This error is due to the program not checking the connection is available via the JBDC connector before it tries to make a call. Its either timing out or implicitly closing it. Due to the time between saves I would expect you either renew the connection or have autoreconnect set true?
@Narimm
Do you have a big database? You might want to refresh your database.
We get around 50 of these each time /foundores tries to save
It causes mildly detectable server lag as well
@Brawnkers
It's actually counted but you might configured something wrong. Could you pass me your config?
Having a minor issue where diamond ore isn't being added to the count. It notifies ops that its been mined, but shows up as 0.00% (0) under the players names. Shows up as 0 mined in the top list as well. Using CB 1.5.2 R0.2 and latest version of foundores (May 26)
@Marium0505
Yes.
Works on 1.5.2, right?
@smallpen
This is fixed in the 1.7 version.
@mastalol
This is hopefully fixed as well. Because it wasn't the 'whole' error code, I couldn't trace it back, but I checked my code and it should be working now.
@PinkSlime
Do you mean MySQL? If so, I can add it.
In your features it says it supports SQLite. Is there anyway you can add support for SQL? I would rather use that.
@mlopezv
I have a big server (100+) where I test all builds on. It works fine on the latest release. If you get any errors you can report them to me so I can resolve them for you.
I want to use this plugin in my server, but the last 2 comments are turning me doubtful... Is this plugin working fine with CB 1.5.2-R0.2 ?
Your plugin has fucked up my server configuration 3 times in a row..
2013-05-01 14:18:03 [INFO] [FoundOres Revisited] I don't recognise ericasperges! 2013-05-01 14:18:03 [INFO] [FoundOres Revisited] Creating info about ericasperges... 2013-05-01 14:18:03 [SEVERE] Could not pass event PlayerJoinEvent to FoundOres Revisited v1.6.2 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:427) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at net.minecraft.server.v1_5_R2.PlayerList.c(PlayerList.java:204) at net.minecraft.server.v1_5_R2.PlayerList.a(PlayerList.java:100) at net.minecraft.server.v1_5_R2.PendingConnection.d(PendingConnection.java:129) at net.minecraft.server.v1_5_R2.PendingConnection.c(PendingConnection.java:44) at net.minecraft.server.v1_5_R2.DedicatedServerConnectionThread.a(DedicatedServerConnectionThread.java:41) at net.minecra < it stops here.
I user v1.6.2 , and craftbukkit 1.5.1-R0.2 . When I shutdown server , it will happen this exception !! How can I fix this issue ?