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.
@Sorky
I ran 2.2.8 for several weeks, 4-8 forges running no fuel mode (3-4 high furnace) with no issues. This broke with the 1.5 dev builds of course, so we wait and hope to see another release real soon.
Thank you for making such an essential plugin!
Update this please?
@Trinity_MorganC1
Theres no check for lava when running, only when starting. This is to make it run as light as possible. The large chest can hold 3456 items and i dont know what sort of impact that many checks has on performance when several DFs are running on the same server at the same time.
Since your problem is related to furnaces always being on, you may want to consider using fuel mode.
Perhaps some sort of intelligent check can be done and only do the lava lookup once a new stack is fed into one of the furnaces instead of for every processed item. I will do some testing and see what can be done about it.
Edit: Added small check every time it loads up more resource. It works in fuel mode but i need someone to test it properly in no-fuel mode and report back if it works or not. Aswell as any nasty sideeffects that may pop up. Grab v2.2.8 and test away :)
Hey, I have just installed version 2.2.5 onto my server. When you turn the furnace on, if you were to leave it on and remove the lava source below the furnace stays on. I was wondering if this had yet been reported/was meant to be that way, and if it is not meant to be and had not been reported, then I am reporting it. :D
Hope I have helped :)
@opgg6skipperv
Can you be more specific, how is it breaking, what fails and are there any error messages or errors in the console?
Edit: My server was last restarted 21 days ago and from what i can tell, the plugin still runs fine. Ofc, since it havent been restarted for a while its also using a somewhat older dev build (2615). So unless you give me more information on what went wrong i cant find the problem.
i am at 2.2.7 and it is breaking time to time
@Sorky
Thanks sorker!
I just laoded the latest version on the spigot 1.4.7 version of bukkit and its running perfect.
My apologies Sorky about forgetting to post but i updated my server about 3 days ago so i updated to 2.2.5 and it works very well. I am about to update it to 2.2.7 so will report back about any issues.
Thanks again for all your awesome work and keeping this plugin alive.
M3DS
@Sorky
Works great. Thanks Sorky.
v2.2.6:
Killed the version check since it gave an error when checking for version file.
v2.2.7:
Reenabled version check and pointed it towards my web server instead.
@Sorky
THANK YOU!!! :D hope theres no problems with this update. so far its working perfectly.
@mal67
From http://www.nub.nu/plugins
2.2.4 for 1.4.6
2.2.5 for 1.4.7
If you have any problems, let me know. Its not been tested too extensively with non-fuel mode.
@Sorky
is this one run against 1.4.7 only? or will this possibly work on 1.4.6 R0.3?
still doesnt seem to want to run, but i dont see any errors. had this working on 1.4.5 no problems.
@Sorky
Thanks, man. Way to stay on top of things. A true bro.
@Sorky
Thanks for taking the time to mail me on the server. I have downloaded the update and thank you for taking to time to sort it out for us all Sorky. :)
Big thumbs up to ya.
@M3DDLER
Officially its still chaoses, but as you say... hes been kinda inactive. Heres my fork which has been updated to work on 1.4.7 (use v2.2.5)
http://www.nub.nu/plugins
This error in 1.4.7
http://pastebin.com/XE53BmVU
So who is actually updating this plugin now?
We need someone who is going to stick with it and not say they are going to update it then up and disappear into thin air leaving all of us who love this plugin hanging high a dry.
@Sorky
ah thanks for the clarification :) ill be sure to only do restarts if possible. i appreciate you taking the time to create that version to begin with.
@mal67
Many plugins dont respond well to reloads (this plugin too it seems) and its usually a good idea not to do them. Do a restart instead. This plugin was originally made by matt_moss, then DonRedhorse picked it up and now finally chaoses is officially handling it, though he doesnt seem very active here. The original code probably wasnt intended for reloads. The fork i posted was mainly to solve the issue of unresponsiveness that the official version has.
I will try to look into making it reload safe but with limited time and extremely poor java skills... well, dont get your hopes up.