AlchemicalCauldron
Overview
AlchemicalCauldron is a plugin for bukkit which is used for converting items thrown into a cauldron into other items (e.g. dirt into iron ore).
Features
- Supports the transmutation of items when they come into contact with a cauldron
- Can define input and output materials
- Can define the statistical probabilities of how often items are transmuted
- More seamless item conversion (timers)
- Pop-out effect when items are converted
- Rudimentary collision detection
Permissions
Permission | Usage |
alchemicalcauldron.use | This controls whether or not a player can use cauldrons to transmute items. |
Usage
Simply run the plugin, in order to create the "config.yml".
Use the "config.yml" in order to adjust the item input/output ratios in order to suit your needs.
Reload the server in order to update the config.
Throw items towards a cauldron in order to convert them into other items.
Note: if items do not seem to be getting transmuted, try standing closer and ensure you are throwing items INTO the cauldron.
Ratios
- Items can be input through their name or their item ID
- Input item ratios (0.0-1.0) control how often an item is converted (e.g. 0.46 for dirt will convert it 46% of the time)
- Output item ratios use a slightly more complicated system, but in general the higher the number (0.0-1.0), the greater the chance of that item being created
Source
https://github.com/Indiv0/AlchemicalCauldron
Download
http://dev.bukkit.org/server-mods/alchemicalcauldron/files
Changelog
Version | Changes | Compatible Builds |
1.16.0 | Update for 1.7.2 | 1.7.2 |
1.12.0 | Cleanup/fix code & permissions | 1.6.4 |
Implement basic collision detection | 1.6.2 | |
1.11.1 | Fixed permissions being given by default | 1.5.2 R-1.0 |
Moved to Mbapi | ||
Various fixes | ||
Changed versioning scheme | ||
1.4.2 | Various fixes | 1.4.7 R-0.1 |
Forced Java 7 | ||
1.4 | Large code rewrites/optimizations | 1.4.2 R-0.2 |
Fixed config.yml versioning scheme | 1.3.2 R-3.0 | |
1.3.2 | Added permissions support | 1.4.2 R-0.2 |
1.3.2 R-3.0 | ||
1.3.1 | Fixed several bugs | 1.4.2 R-0.2 |
Added ability to configure item outputs individually | 1.3.2 R-3.0 | |
1.3 | Fixed Java 6 compatibility | 1.4.2 R-0.2 |
Fixed PluginMetrics implementation | 1.3.2 R-3.0 | |
1.2.1 | Built against Java 6u37 to ensure compatibility | 1.3.2 R-3.0 |
1.2 | Added ability to throw stacks of items into cauldron | 1.3.2 R-3.0 |
Fixed small error message spelling mistake | 1.3.2 R-2.0 | |
1.1 | Added timers in order to allow for more seamless item spawn/despawn | 1.3.2 R-2.0 |
Added PluginMetrics support | ||
1.0 | Added base functionality | 1.3.2 R-1.0 |
Added ratio support | ||
Added configuration file support/ratio storage |
Bugs/TODO
All bugs and TODO information can be found on the issue tracker for this project on GitHub.
@Garfonzo
I understand that.
However, the `/reload` command petition arguments apply to plugin `/reload` commands as well.
Specifically, it is very difficult to ensure that there are no memory leaks across plugin reloads. Either way, I do not have the time to allocate to ensuring that AlchemicalCauldron avoids memory leaks across reloads.
Sorry, but I will not be implementing this feature.
@Indivisible0
I'm referring to a reload command for your plugin. The page you linked to is a petition to remove the actual "/reload" command. I'm talking about a command such as "/AlchemicalCauldron reload". This would reload just this plugin and not the whole server.
@Garfonzo
I will not be implementing a /reload command because using /reload for individual plugins is a very bad idea.
@Indivisible0
Have you implemented a reload command yet? It's a good plugin but the whole reboot the server just for this plugin is brutal.
@Indivisible0
Ingredientes for make items, fell like "craft".
For example, put 3 coal in the cauldron and get 1 diamond
Put a watch and a diamond a get one esmerald (?
Please send me a MP if you make my suggestion... i have a server of Harry Potter: Twwom.com
@MrCobayo
Like what?
thats a very good plugin, but i need more options
Only a few things that I can think of that would be nice additions.
Permission support.
The ability to get multiple items back.
@Garfonzo
Currently it is not possible, but it is a planned future feature.
I will also look into a reload command.
Is it possible to have multiple inputs? For example:
Inputs: 3 Dirt, 6 Cobblestone Outputs: 1 Diamond
Also, you need to implement a /reload command. Having to reload the whole server just to reload this plugin's configuration is not good.
@deleted_10645961
Unfortunately I'm too busy to make a video, but feel free to ask me questions.
You need to have a video made on this I dont under stand it very weel
@Likasy
Thanks for the feedback!
I understand what you mean and I've been planning to upgrade the configuration system but I simply haven't had the time. I'll look into implementing what you asked, just keep checking back once in a while.
Hey! Awesome plugin and really cool idea, perfect for my server and friends are enjoying it! Anyways, I don't know if it's possible, but I was thinking of adding more configurable data in the config. Say I toss a dirt in and want a portal block to pop out (ID:90). I put :
'3': 90: '1.0'
and it works perfectly fine. However, sometimes we enjoy a good roleplay and it would be amazing if we could configure lore, name, etc. for the output.
Hopefully I explained it clear enough, and sorry if it's too outrageous of an idea. Even if it isn't possible, thanks for the awesome plugin and keep up the great work!
@Ferrocane
Fixed.
@user_135859
Fixed.
@user_135859
Fixed.
@piter909
Wish granted. Thanks! :)
Update it, please!
Awesome plugin.
now its just not working lol
config keeps resetting.
My config always resets :(
@Indivisible0
Hey there. I had originally deleted the plugin, but when I read your reply here just now, I figured I'd grab it and test it a bit more to see if I could help you. I discovered the following:
The plugin appears to default to allow access to everyone, as every group could initially use it without requiring the "alchemicalcauldron.use" node. The node does technically work, however, because I was still able to deny access by using the negative node:
- -alchemicalcauldron.use
The group I added this node to was no longer able to use the cauldron. All others can.
I'll happily grab and use this plugin now, since I can just deny access to groups that shouldn't be able to use it.
Oh, and I'm using PermissionsEx. Almost forgot.
Let me know if I can be of further help.