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!
I'm an idiot. I do not understand the features of the plugin. I'm sorry for my giddy. After reducing the time to five minutes lag is less but still there :/ Maybe it's because my computer is not very good. But somehow I can handle it, and thanks for a great plugin!
@piotrex43
Hello Piotrex43, I don't really understand you. 1.6 uses SQlite to write data to a database. This database can be found in the plugins folder. /plugins/foundores revisited. If you want to reduce lag when saving, try lowering your save time. Set it to 5 minutes, let me try if that works.
Hello! I have one question because, as I am using the latest version of the plugin (FoundOres Revisited v1.6) to write the data to dispute arises lag (freezing server on 5-20 sec). Or when you will be able to connect to the database to reduce the lag? (Sorry for bad English) And ... Greetings from Poland :-)
@Brainiacguy
Hmm, I can't seem to reproduce this error? What enchantments does the pickaxe have? Can you send me a copy of your config? What version of FO:RE are you using? Thanks in advance.
@Brainiacguy
Thanks for warning me, I'll be fixng this!
Major flaw: if a player is in complete darkness and the light level check is on , and then they use their pickaxe with a number of level 4 or 5 enchants they can keep breaking that block and diamonds will start popping out as if you were breaking diamond ore blocks over and over again.... Even worse if the player has a fastbreak hack
@Staartvin
Thanks, but in the beginning players will have a too high ratio and when I check it, its coal.
@Vincent1468
Hey, thanks for the suggestions! I'll add a way to automatically detect what world you're in and use that world. For the too high diamond ratio command, I think I'll change that to a 'too high ration command'.
Ive got two suggestions, the first one: A command to only check for people with a too high diamond ratio would be helpful and the second one a setting to change if the server has multiworld, I only have one world and I have to type the worldname everytime I check a player.
@faxionsurvival
@faxionsurvival
Haha, nice to hear that you appreciate my work! I've seen the donation and I changed the amount shown on the donators list to $40 ;). Thanks a lot! You really help me out. :D I hope it will work as intended. Adding ores to the watchlist doesn't effect anything. Unless the list is very long. (Over 100 ores or so).
Seems to be running good after 1 hr on default settings. I also added a few more ores to the watchlist, I am not sure if that effects anything. I think you solved the problem! I will let you know after about a day of usage how things are going!
Hey, thanks for your dedication and hard work! I cant wait to test the new version when it is released! I really appreciate you working so fast to try to come up with a solution to my problem. I will let you know how it goes as soon as the new version is available for me to download.
Btw I sent another donation to you, Thanks for your help on my issues.
@faxionsurvival
I'm done with the new implementation. Hopefully this will reduce the work done by FO:RE. I've uploaded a version to BukkitDev. It should be up by tomorrow.
@faxionsurvival
To temporarily solve the problem, just before shutdown (with an interval of 360 minutes), type /fo save. A save will be forced and after that restart/shutdown. Your players won't notice the lag because you immediately shutdown the server.
I looked into MySQL. The problem is that I'm not familiar with it. I need to learn it, to be benificial. I don't like to see that FO:RE is causing such problems. I've already started working on a time span save. This is already done aswell, I just need to get some bugs out of the way. For the shutdown part, I'm not sure how to fix it. I have to come up with some sort of creative idea. Feel free to suggest. The shutdown part is so slow because FO:RE saves all data at once (which is forced on shutdown). By looking at the code I found a memory leak which will lead to a server crash if the plugin is running too long. That part was fixed so I hope that will improve your problems quite a bit. I hope to get a good and stable fix out as soon as possible. Hold tight!
The server usually fills to 70-100 slots at peak, but average is around 40-50 during most of the day. What I am wondering is, if I set the interval to 360 will that cause problems on shutdown? I do notice when I shutdown/restart fo causes the stop process to take some time at 10 mins, sometimes I have to actually restart the actual server because of a freeze up. As far as server stability, without fo in, the server runs perfectly fine, I really think it is just the saves. Have you thought about adding mysql option for saving stats? Do you think that could help on performance?
@faxionsurvival
Hmm, how many players are there on your server (regulary)? What you can do, for now, is take it a notch up. Try to set the interval around 360 minutes. (6 hours). Only do this if you know that your server won't crash often. That sounds a little odd, but if FoundOres can't save, no information will be stored. Although there is a fallback server when everything goes wrong, it doesn't always working. I will start working on a better save system which spreads the work done. E.g: It doesn't save all items in 1 tick, but tries to save it in a time span of 5 minutes. Hopefully I get that working.
@EncryptedCurse
Haha, thanks :)
Hey I have been having a bit of a problem when this plugin saves at any interval, at the save time the server seems to almost lag out. There are no errors, but every 10 mins or so, with this plugin installed, my ticks drop to around 10, then after a few mins it goes back up. This also causes heavy chat lag/command lag. I have tried this several different save intervals. 1 min 2 mins 5 mins 10 mins 20 mins. Any ideas?
You work fast. Thanks for adding it in!
@EncryptedCurse
I'll add this to my todo list. Thanks!