FoundDiamonds
Standard Installation and Basic Test
Video: http://youtu.be/9Ke1vDRLsRw
Just drop the FoundDiamonds.jar in your plugins folder and reload!
If you're an OP, continue to the next step. If not, give yourself the permission fd.*
(You'll give normal players fd.broadcast for broadcasts, and fd.monitor for admin messages and light level monitoring.)
The best way to test the plugin and verify that it's working is to find some natural iron or coal and break it! You should see a message.
>Note: FoundDiamonds does not announce blocks that a player has placed (Unless an OP or a player with the fd.* permission uses /fd clearplaced after placing the block) Note: Only Players with fd.broadcast can see the broadcasts (this plugin requires permissions)
Permissions, commands, and configuration file information
- FoundDiamonds Wiki Main
- Commands
- Permissions
- Configuration File
- Setting up admin messages and/or light level monitoring
Recent Changelog
Version 3.6.4
- Note: Traps may or may not work in this version. Not sure what direction to go with these yet.
- Updated outdated licenses and renamed packages
- Fixed a bug with the clearplaced command not working for flat file setups
- Fixed odd things in the config
- Fixed a bug where it was impossible to give out one random item
- Fixed a bug where the random item is also given to the person who mined the diamonds...
- Added random potions to the config so you can now select which potions to give out (even bad ones maybe!)
- Removed potion messages for now and replaced with something far simpler
- Added more default potions (night vision is cool!)
Troubleshooting
- Is the ore you broke a block that was placed by you or someone else. Do /fd clearplaced?
- Is the world you're breaking ores in listed in /fd world list?
- Are you using the latest version of FoundDiamonds? /fd version
- Are you using the CB build this was built against?
- Are you breaking ore in creative mode with creative mode disabled in the config?
- Did you make changes to the config and forget to do /fd reload?
If none of the above helped you, it's likely that you have found a bug. Please report the bug along with your config.yml and any errors in the console you may be receiving so I can look into it.
Credits
- itsatacoshop247 - Original concept
- CeramicTitan - Providing unparalleled support
- Team Haven (HAVENmc.com) for an awesome logo
- nossr and GJ - Help in IRC for making the plugin compatible with mcMMO
- snoepje0 - Making traps a lot better.
- SAKingShibby - Updating traps for emerald ore
Comments
-
_ForgeUser6845624 Owner
-
_ForgeUser7637362 Contributor
-
_ForgeUser7830444 Author
-
View User Profile
-
Send Message
Posted Sep 3, 2012@SeeD419
I followed your advice when you said "fd.monitor is for admin messages. You need to give them fd.broadcast". I then removed fd.monitor from default and gave them fd.broadcast instead.
This looks to have been one of the problems all along, I've been testing everything under the impression that fd.monitor wasn't to be used for default (as my original problem was with default users and fd.monitor).
It works now that I went back to original settings with fd.monitor for default users.
-
View User Profile
-
Send Message
Posted Sep 3, 2012@DoctorBoyd
I'm not sure what you're trying to accomplish. Why would the admin message blocks be the exact same as the broadcasted blocks?
Of course the default group can see the broadcasts, you've given them fd.broadcast.
Try this: Remove fd.broadcast from the default group and instead give default fd.monitor. I think that's what you're after.
-
View User Profile
-
Send Message
Posted Sep 3, 2012@SeeD419
Thanks for replying. Our permissions for groups are:
admin (fd.*), moderator (fd.admin), default (fd.broadcast)
-Broadcasted Blocks are: gold, lapis, diamond and emerald ores
-Admin Blocks are (same): gold, lapis, diamond and emerald ores
Everything works except the default group can see the broadcasts. I tried with PEX and bPermissions, no other plugins or permissions present. Default group could see broadcasts in both cases.
I would like it so group default doesn't get on screen broadcasts. The problem is when I remove the (fd.broadcast) permission from default, their mining isn't broadcasted to the admins/mods, if I keep it in, they see the broadcasts.
Should the Admin Block list be enough to prevent users with only the (fd.broadcast) permission from seeing the ores on the list?
-
View User Profile
-
Send Message
Posted Sep 3, 2012@DoctorBoyd
I can't reproduce this at all.
Do your admins have the fd.admin permission?
-
View User Profile
-
Send Message
Posted Sep 2, 2012@SeeD419
Thanks for the help but I'm still having a small issue.
Default players now see broadcasts on the admin message block list. They have fd.broadcast.
Is there a way to keep broadcasts hidden to the default group? It's worked for me in the past, I'm not sure what I'm doing wrong now.
We have 4 ores on the admin message block list and the same ones on the broadcasted blocks list. Taking an ore off the broadcast list (but not the admin list) stops the broadcast for everyone, even admins. How exactly does the admin message block list work in this case?
-
View User Profile
-
Send Message
Posted Sep 2, 2012@DoctorBoyd
fd.monitor is for admin messages. You need to give them fd.broadcast.
Don't use anything below 3.6, please. 3.6 is stable and tested.
@rangewonk
Make sure your players have fd.broadcast and that whatever you're breaking is in /fd bc list
-
View User Profile
-
Send Message
Posted Sep 2, 2012Broadcasts are silent any ideas to fix?
-
View User Profile
-
Send Message
Posted Sep 2, 2012I'm having a small problem. The 'fd.monitor' permission isn't working in bPermissions or PEX.
When our default group mines a broadcasted ore there's no broadcast or log entry. When I mine an ore with admin permission 'fd.*' there's a broadcast and log entry. Any ideas?
Using RB 1.3.1 2340 and v3.6 of found diamonds
Also I tried v3.5.4 and it doesn't broadcast, even with the 'fd.*' permission. I tried using the '/fd bc add diamond ore' and it says I don't have permission for the command.
-
View User Profile
-
Send Message
Posted Sep 2, 2012@Kirbyarm @SeeD419 @chwergy
I've cracked it! The reason you don't recieve a broadcast message when someone breaks the block is because for the new update you have to add the block you want to be broadcasted.
For example,
"/fd bc add diamond ore"
Then whenever someone breaks diamond ore it will be broadcasted.
https://github.com/SeeD419/FoundDiamonds/wiki/Commands <
-Everything i've said has been here the whole time.So please next time, before abusing the developer just spent a bit more time reading.
Seed419 you a great coder and have done a fantastic job on this plugin.
-
View User Profile
-
Send Message
Posted Sep 1, 2012For those of you having trouble, I've added a new section with links to all the information you should need, including some examples of how to set up admin messages and light level monitoring. Perhaps I should have made the information more obvious.
Hope this helps.
-
View User Profile
-
Send Message
Posted Sep 1, 2012@chwergy
The permissions are listed on the wiki, on the permissions page...
https://github.com/SeeD419/FoundDiamonds/wiki/Permissions
It IS mentioned on the main page. It's right at the top, the link that says 'Wiki'.
-
View User Profile
-
Send Message
Posted Sep 1, 2012I was having the same issue as Kirbyyarm. I could only get it to notify me when someone breaks an ore listed in broadcast. You need to add 'fd.monitor' to the default group.
Perhaps SeeD419 should mention that on the main page, because right now it looks like the only two permissions are fd.admin and fd.broadcast, so I didn't bother looking for other perm nodes.
-
View User Profile
-
Send Message
Posted Sep 1, 2012@Kirbyarm
There is a permissions page for this.
It's all on the wiki, which is linked clearly at the top of this page.
I've tested every feature of this plugin thoroughly with the latest build and had absolutely no issues.
-
View User Profile
-
Send Message
Posted Sep 1, 2012Used to use this plugin ages ago. Started again, and it's incredibly buggy. As an OP with "fd.*" even when de-opped it is not notifying me when players break the ores found in the Admin Alerts part of the config. I use it primarily as an admin tool to have my staff pinpoint suspiciously unheard of amounts of valuable ores being mined.
Now, I've tried most up to date, all 1.3.1 versions, downgraded. None of them work properly even with full permissions.
Might I recommend making a permissions page for this? Can't seem to find one anymore and I'm relatively annoyed that this plugin doesn't work by "dropping in the JAR" like it says in the header.
Scrapping the plugin. Kirbyarm~
-
View User Profile
-
Send Message
Posted Aug 31, 2012Update to 3.6 once it gets approved.
I've tested everything I can think of and it looks bulletproof.
-
View User Profile
-
Send Message
Posted Aug 30, 20123.5.4 doesn't work in my server.
-
View User Profile
-
Send Message
Posted Aug 28, 2012I guess stick with 3.5.2 until I get this next update out, which will hopefully be very soon.
-
View User Profile
-
Send Message
Posted Aug 28, 2012With the new update I am getting spammed for players mining 1 ore at a time even though they are part of a cluster. Is this a current bug or?
-
View User Profile
-
Send Message
Posted Aug 27, 20123.5.4 doesnt broadcast broken ores at all, with '*' permission nod or with OP. Using Bukkit 1.3.1 R2 Recommended build. testing 3.5.3 now... Removed every plugin, OPed myself, restarted server, tested 3.5.3 and i dont see any msges in console or in chat about ores beign broken...
-
View User Profile
-
Send Message
Posted Aug 26, 2012@spazmonkey777
Glad you fixed it. I'm in the process of fixing a ton of bugs, and making this whole process a lot simpler for developers (myself to maintain and troubleshoot this, and others who want to help).
The next update will be really solid. I'm in the testing process as we speak.