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.
What is Value for? This config makes NO sense. i set the Chests up assuming that if that chest spawned then the items i put in it, in the config, would be inside the chest... but no they were random?
Does 'DIAMOND: 64' not mean 64 Diamond? if it means 64 value... what does that contribute towards?
there were also things in the "Rare" chests that were not even under "Rare" in the config...
@Taien1
No i mena like an Example Config 'Page' like most other plugins have, where it gives you a example version with comments... Not nessesarily In the actualy config, And DIAMOND_SHOVEL is automatically generated in the file... so that one wasn't my bad.
@disciple218
Thanks for trying to help people disciple. :)
@deleted_7536780
It has to be like this:
POTION:822: 150 (or whatever value)
and it's DIAMOND_SPADE, not DIAMOND_SHOVEL.
@deleted_7536780
Some people really need to learn how to speak to others. I don't know what you mean by config documentation, but there is a TON of info up there /\. If you're talking about comments in the config, I don't do that because it would cause redundant crap in there since some sections (under worldoptions) appear more than once. Not only that, but everything can be set ingame by someone with taien.th.admin.
@deleted_7536780
Did you try running it through a YAML parser? The error you posted was regarding a line with DIAMOND_SHOVEL in it, but I didn't see that anywhere in your config. Try taking out the lines with potions. If it works, you know that's where the problem is and you can then submit a bug report ticket.
@disciple218
Config: http://pastebin.com/hK0nmZ1h
Also tried putting the potions with "" like it says.. e.g "POTION:8292": 5 but it auto removed the ""
@deleted_7536780
Obviously, there's something wrong with your config.yml. It works just fine out-of-the-box for me and many others. Why don't you post it? That may be a little more helpful than the snark. And please use pastie.org or pastebin.com so as not to cause spam.
Config documentation? how can you NOT have Config documentation?
fails
@neceros
Just double-checked all the code that uses the hunt tool and the /hunt command and it's all set up correctly to use the correct variables. So I have to guess you're just getting them mixed up :) WorldOptions.<world>.ChestInterval is the amount of seconds between checks to see if a chest should be spawned. Options.SecondsBetweenChecks is the interval between uses of /hunt or the hunt tool. :) Hope this helps!
@Sileos
It is not yet possible to set up enchanted items to spawn in chests. HOWEVER, I will add this to my list of things to do, because I, too, have been wanting that functionality. I'll try to set it up so you can define specific enchantments OR have it randomly determined. :)
@neceros
Also, yeah, I had intended to add better handling of improper command usage so it would tell you what you did wrong, but I haven't gotten around to it yet. I'll add that to the list of things I need to do. Sorry about that!
@neceros
If you're talking about the command /hunt interval(which in the yml file is supposed to be WorldOptions.<world>.ChestInterval), I will look into it. That should be linked to the interval between chest spawn checks. If you're talking about the .yml file and the node Options.SecondsBetweenChecks, that is what that variable is supposed to do. :) Options.SecondsBetweenChecks is the amount of time in seconds before a player can do /hunt or use the hunt tool after they have last used it.
@Taeila_Fae
Question 1: Currently no.
Question 2: Yes. :)
I could not find this so I apologize if this is a re-occurring questions.
I know its possible to add other items to the config file but how to you add enchanted weapons and armor?
I would like to add these to the Epic chest so that it is properly named. My players do not find records and/or blocks worthy of the title Epic.
Do you realize the interval is being used as the limit to how often players can consume the rotten flesh, right? It's not supposed to.
It's supposed to be how long the plugin tries to place another chest. What's going on?
I found the issue. It's telling them they can't use it because the hunt got reset. That's a very confusing message. In fact, most of the messages are confusing. Try doing a command with the wrong variable. It simply tells you /hunt
Come on :)
My players love it. Just a few questions that I didn't see above or that I might have looked past. Is there a way to have it auto spawn a chest after one has been found. And can there be more than one treasure chest out at a time? Like I can do /starthunt 5 times and there will be 5 chests in the world.
ill wait for costomizable messages, i suggested that long time ago and i really want this plugin, but i cant use it with out translations...my users dont speak english
0.9 Released!
See changelog for details :) Also please check the next version section to see what's coming soon. I'm also going to write a chart right now of which commands go with which config nodes. Up there /\.
The file has to be approved on bukkit, so as soon as it appears on the right -> feel free to test it.