DwarfForge
Wiki | Permissions & Commands | Usage | GitHub Source
The Dwarfs learned long ago how to manipulate lava to their will. By building their furnaces directly above lava, they can smelt metals and bake goods for a long time without hauling buckets about. Now, you can too. Build your furnace directly above a lava block, then punch the furnace to ignite it. Punch it again to douse the flames. No fuel/buckets needed!
There is a minimal configuration file; the plugin will automatically generate a default config.yml file if none is present. Just drop the JAR into your plugins folder and reload.
Featured Videos |
---|
Features |
---|
- Runs forever! No fuel/buckets needed.
- However, Forges can be required to operate with fuel, which is pulled from the input chest along with raw materials.
- Punching the furnace toggles it on/off.
- Dwarf Forges stack vertically. Lava only necessary under the lowest forge. (Lava is powerful, man!) Stacked forges can all access the same set of input/output chests.
- Input and output chests (left and right of forge, respectively, when facing it) supported. Double-size chests also supported. Additionally, you can "stack" horizontally to access nearby chests.
- Stacking limits are configurable (defaults: 3 high, 4 wide).
- Can change the cooking time: warp speed!
- Blocks in a short, 3-block radius from any Dwarf Forge are protected against fire from lava.
- Supports Permissions.
- Supports Metrics
Demonstration |
---|
Originally developed by matt_moss and DonRedhorse.
@DonRedhorse
Is there an ETA for a 1.3 fix? :)
@crohakon
perhaps with 1.3 of Minecraft, as that will probably break the plugin till I fix it..
I need to check though how the plugin was coded, can't remember anymore atm and I did take over the plugin, I didn't code it..
Any chance of getting an in game reload command for when changes are made to the config file?
@dandelion02
don't know if bukkit finally implemented methods for it... I think IIRC reading the code that this is kinda hardcoded.
Love this plugin, but is there any way to set it to be longer than the default time? The default is 9.25 and I wanted double so I've set it to 18.5, but in the start up I get a message saying it's too long, setting to 9.25. Is there a way to change this? Thanks!
@medede
no idea... will need to take a look
@gawelium
looking into it, but you should post your permissions via pastie.org
@Stealthboss
could you post your permissions via pastie.org
I want to cook stuff fast with this plugin so i made the burn thing very short (0.15sec) and when i put stuff in i cooks it once normally with the long original minecraft time the next one is instant then it goes back to normal minecraft time and so on is that a bug or is it unfixable
Me too Stealthboss...
Maybe need an update for new RecommendedBuild no ?
I have players on my server and they cant use this plugin! (not op) I am using PermissionEx please help
@Strahan201
strange.. could you post config, log and permissions via pastie, don't know if you want to open an issue on github for it..
I thought about spawn protection too, but I added:
spawn-protection-size=0
..to my server.properties to no avail, still doesn't allow non-admins to use DF. Turned on PEX debug and had my non-op alt try:
20:15:59 [INFO] User Rhiannon201 checked for "modifyworld.blocks.interact.furnace:3", "modifyworld.*" found
That's all that came up. Shouldn't something DF related come up? I did /plugins, it's there and in green. I enabled DF debug, and nothing comes up in the console at all when the test account tries to use it. Admin attempt shows the debug info.
@Strahan201
gawelium's idea could be it, otherwise I would need a debug log, and perhaps also some debug from pex with pex toggle debug
@Strahan201
Spawn is maybe protected.
I have a weird problem. Users cannot use the dwarfforge I placed at spawn. At first I thought it was permissions, but if I make a DF away from spawn, my users can use it. In the course of my testing I stripped out all my plugins and ran just PermissionsEX and DwarfForge and still had the problem. I know the first reaction would be to say "oh, it must be PEX" but as I said.. DF works fine away from spawn so I don't think that's it.
Any idea?
@gawelium
that is just for the config... IF I would implement command which would be able to change settings you could enable there if the changes would be saved.. and autoUpdateConfig would automatically update the config file if I would code updates for it, for example add a new option.
@Gravemind2401
yeah, no probs
@DonRedhorse
I compare to the link of configuration and I changed this sentence : - autoUpdateConfig: true - saveConfig: true
I have to put "false" ?
<<reply 697680="">>
thanks :) looks like my config was a really old version or something.
@Gravemind2401
you have a problem with your config file... it should look like this:
http://dev.bukkit.org/server-mods/dwarfforge/pages/configuration/
@gawelium
hmm I only save them on onDisable as there is no chance for a clash.. so when you do a reload or a stop it should save..