TreasureHunt
TreasureHunt 1.1
- Randomly-Generated Chests - Stationary Chests - Money Distribution - Multiple ItemLists - Excessively Configurable - Excessively Fun -
Find that loot!
Message from Taien
I've officially changed the license to Public Domain. I don't have time to maintain the project anymore, obviously. Sorry guys....hopefully someone will take over for me. If you want me to give you official access to the plugin, PM me. I'll pick someone based on their other plugins' quality. I put a lot of work into this plugin and am sorry to have to do this, but I don't even really play MC anymore since I no longer am in contact with all the people I used to play with. Sorry...
Hello everyone. This is my second released plugin for bukkit, but probably my tenth or twelfth overall.
The purpose of TreasureHunt is to give people even more fun things to do in your server. The plugin allows your worlds to randomly generate chests based on very specific settings that you choose. You can use any number of worlds with this plugin, and each can have a different configuration. :) You can also set up specifically enchanted items to appear in your chests, stationary chests that respawn after an interval (with a bit of randomization), and as many custom item lists as you could ever want - to use a separate item list for each world or even for each stationary chest!
For ALL info on how it works, please see the Plugin Tutorial section. :)
Plugins Supported
- PRIOR TO 1.0: Vault (for economy and permissions)
- 1.0+: Vault (for economy and permissions), WorldGuard and Towny (to prevent chests spawning in certain areas)
Note: If you don't use Vault, ops can still do the admin commands. See command list for details.
Help! I can't get any chests to spawn automatically!
Please see Example Configs. :)
Planned Features (Soon)
- Option to create maps centered at the chest location, fully mapped.
- Suggestions?
Next Version (1.2)
Green = Done Red = Not Done Gold = In Progress
- Add support for Residence.
- Config option ChooseChunkFirst - will tell location selection to choose one chunk to perform all of the spawn checks in. This will potentially cause more failed spawns (meaning the spawn attempt would be cancelled until you hit your random chest chance again), but is designed to help out servers which backup their world on a constant basis. (TreasureHunt needs to check certain conditions in each spawn location. This causes the chunk's modified date to update on the server, although I fail to understand why since it's not actually changing anything. To prevent many chunks being "modified" by TreasureHunt, this option will be added.)
- Command for normal players to find out how many of each type of chest (Common, Uncommon, etc) are currently present in the world.
- Change Damage on EnchantedItems entires to MinDamage and MaxDamage, to give you a chance to assign the spawned item a random damage between those values if you wish.
- Cover error messages with the new message system as well.
- Config option to have messages about chests only displayed within the world they originated in.
- Command to view a list of EnchantedItems entries ingame, /th enchlist. Command to view a list of CustomLists entries and one for WorldLists, /th customlists and /th worldlists.
- RandomGen and GenValue options for EnchantedItems entries, to allow the plugin to randomly assign enchantments to the item instead of using the Effects list to be specific.
- Command to view a list of EnchantedItems entries ingame, /th enchlist. Command to view a list of CustomLists entries and one for WorldLists, /th customlists and /th worldlists.
Known Bugs
- See Ticket section.
Changelog
Version 1.1
- Removed TopChestsByValue config option and converted /tophunters to /top and /top values, which displays by chests or by values respectively. /top command is also aliased as /thtop.
- Fixed a bug with PlayerData loading. /top should no longer reset on server restarts.
- Moved other updates to 1.2 due to PlayerData bug needing a fast release.
Version 1.0
Note About 1.0
Be sure to back up your config prior to updating to 1.0. There are changes to the config structure, and to be honest I am not good at writing conversion methods. The changes will be obvious enough once you see the new version of the config compared to the old version, so you should be able to copy/paste old data directly into the new file once you've got it running.
- New optimization for chest spawning. No more lag when a chest location is being selected!
- Connection to WorldGuard to prevent chests spawning in regions where block breaking and chest access are disabled.
- Connection to Towny to prevent chests spawning in town blocks.
- Config option to set the levels at which chests become Uncommon, Rare, Legendary, and Epic. (Currently they are 1500, 2500, 3500, and 4500 respectively.)
- Custom (named) Item Lists, and an ItemList option for each world as well as each stationary chest. (Worlds will only be able to use itemlists from the WorldLists section; Stationary chests will be free to use WorldLists or CustomLists.)
- Complete rewrite of the way configs are handled so as to prevent the 'where's my config file?' issue. Apparently I've been using an outdated method of config usage. :/
- Config option to choose the block left behind after a chest fades (perviously hardcoded to soulsand). Also the ability to say RETURN instead of a block name to have the block return to what it was before the chest spawned.
- Permission node for starthunt commands, in the format of taien.th.starthunt.world (or *). Also taien.th.admin still covers this.
- Permission node for stationary chest commands, in the format of taien.th.stattool.world (or *). Also taien.th.admin still covers this.
- A command to view a list of the top ten chest-finders, with listings of the total value of the chests they have found, as well as a command to clear the list and a config option whether to display by number of chests found or total value of chests found.
- Finish/fix directional text, so that when a player does /hunt(or uses the tool) it will tell them which direction they need to turn to be facing the chest in addition to the distance. Config option to shut off this function already exists.
@Taien1
Thanks for the answer! That being the case, I'd like to request those two things be added to the plugin as they would make it a perfect fit on my server! Just out of curiosity, how far off would additions to the plugin, such as those two, be from now? Could they be possible in a next release? Or would such an addition require much more time?
Thanks!
-Drewmoe0194
@erdrickk
My plugin also now uses /th as an alternative. If the /hunt command is still being handled by my plugin and not MonsterHunt, I think there's a way to set something in your bukkit.yml file in your main server directory to indicate which plugin you want to use the command. If not...I'll see if there's a way for me to create a config option to turn off the command...not sure if you can do that though since the commands are defined in the plugin.yml inside the plugin....hmmmm....
will this now work with Monster Hunt? your plugin and Monster hunt both use /hunt
Version 0.8.1 Released!
Please see above for changes. It adds a few minor features and works in 1.2.3 :)
Let me know if there are problems. Thanks, and enjoy!
@Drewmoe0194
Answer to question: Yes they would spawn in protected areas as I have not built a bridge to WorldGuard. However unless a large amount of your world is protected, it's statistically unlikely. And if it spawned in a protected zone, then no, people wouldn't be able to access it unless they own the land. :/ Might have to bridge WorldGuard at some point.
Regarding suggestion: Definitely doable.
@Ebins
Hmmm I would think that Vault would be the problem in that case. All my permissions handling is done through Vault, and so I think maybe Vault's bPermissions bridge is messed up...try downloading a new version of Vault and see what happens.
I just had a quick question and suggestion.
Question: Would treasure chests spawn in protected areas on the map? (We use WorldGuard and have numerous areas protected to players) And if it were to spawn in a protected zone, could the hunters access it if they found it without permissions to that land?
Suggestion: Perhaps add a command to clear all active treasure hunts? (/hunt clear) Or something of that nature. (Unless its already there and I missed it in the description)
Thanks!
-Drewmoe0194
nooooo. Where is the update?! lol... not whinging... just sitting on the edge of my seat waiting for it cause I'm hoping it will work with my 1.2 server!!! (previous one doesnt seem to work :( )
EDIT: May I also suggest that you change all the commands to /thunt instead of /hunt? As there is at least one other plugin (Monster Hunt) that uses /hunt... and it seems likely that those of us who like these sorts of plugins would probably use both of them! Just a suggestion :)
Is there any chance you can get this to be compatible with bPermissions please? Anyone who's not an op only gets /hunt back as text when they try to use the command/tool. It works fine for ops. Many of us server owners use bPermissions because that plugin is very lightweight on resource usage as compared to essentials and such. I would love to get this working for my server, and the users are very excited. :)
PS - Vault IS installed.
Update please.
well it wasnt your plugin but thx for responding
@Drehverschluss
It shouldn't cause that kind of error as it doesn't really open many files.
@drorex
Some of the command aren't set to work with console yet, but I can add that soon. The starthunt command does work, though.
@Sevennemesis
This plugin will be updated later today, after I sleep. It's already pretty much ready, just needs a test before upload. There are two minor new features as well.
update 1.2.3???
Hi,
Would be convienient if I could use the commands from the console, looks like your code doesn't expect that right now. Here's a sample error I get:
Thanks!
Well ok i try that with the chance and interval. otheriwse can be your plugin the reason for a "TooManOpenFIlesError" ?? Well like if tey try to get to much chunks?
@OriginalMadman
I will add that to my list as something to fix for the new 1.2.3 release. It's supposed to accept taien.th.tool.* or taien.th.hunt.* or taien.th.claim.*, but apparently I need to individually handle the * permission with Vault. Yeah, will fix.
@Durand1w
It's supposed to supply a default item set. If it's not, I'll have to look into that.
@drumming102
It's not per chunk. If X is the chance you choose, there is a 1 in X chance that a chest will spawn each <interval> seconds. So if you set your interval to 30 and your chance to 5, then every 30 seconds there's a 1 in 5 or 20% chance for a chest to spawn somewhere in the world. That's why by default it's like 1 in 50 every 60 seconds or whatever it is. Otherwise it'd be a lot of chests :p But that's all based on your style. If you want tons of chests, that's when you set the chance lower :)
@Drehverschluss
The interval is only how often it has a CHANCE of spawning. So it might appear that way. Set your chance to 1 and you'll see it more obviously. It will spawn a chest every interval at 1 chance.
@Katkat1010
Sorry, I had been having some trouble with changes to the way a chest inventory was handled in bukkit. I should have it fixed by tomorrow after work :) As for the delay in general, I worked 70 hours last week. So yeah....there has been a delay in me catching up :p
1.2.3?
Got it to work fine with rebuilt configs. Works fine now. Just a wee bit annoying that claim and tool permissions don't seem to work with * as world or by themselves (anymore). I had to add permissions again.
Jap interval is using in Minutes not in secounds