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.
Please update for 1.2.4!
The version posted above as a possible fix for r01 works on 1.24 for me. Sometimes it takes a server restart before newly made forges work.
Is there a working build for 1.2.4? :)
Why does my dwarf forge say there is a V2.9 avail and I need to update but I don't see any dl links to a 2.9?
@DonRedhorse
I'm having an issue where the bottom furnace shuts itself off.
Edit: I'm having a bigger issue now. This isn't updated for 1.2.4 yet. Oh well, patiently waiting for an update :)
@brezeeger
well... I took over the plugin so I don't know exactly why matt_moss did it that way.
but atm the plugin only listens to events.. and uses timed actions to toggle on and off.
this is very efficient on the cpu but there are some issues like you noted.
btw: I found the bug with the furnaces not toggleing.. it is bukkit.. it will return lava from time to time (when the toggle doesn't work)...
so I can now make the plugin exploitable again or leave it like it is.
Follow up on innate_ideas (aka, it's not just you!)
I've been running the probable fix for dwarfforge on CB 1.2.3-R0.2. It's been mostly working alright, unless you go far away and the chunk unloads - at least, I had no problems with it until I left to go build an arena for the War plugin fairly far away. I'm also running double chests to the left and right of the furnace. While it was supposed to be making stone, well, it wasn't. In this case, one of two things seem to be happening:
1) The forge turns off and stops producing. 2) The smelted item gets stuck in the furnace.
For awhile, I couldn't even get the forge to turn on, but that's when I noticed there was an item inside.
As I'm taking the trouble to make a post, I have a plausible improvement to your plugin that could go one of two ways:
a) When the furnace completely empties the chest, have it automatically turn off. This signal will signal that it's done and should be relatively easy to implement. I get the impression it does a pull_item_from_chest type function when it turns on and when it ejects an item. So upon failure to pull an item, just call the turn forge off code.
b) In the scenario where it burns through all the items, it stays lit. If you add more items to the adjacent chest, have it start pulling those again. You presently have to turn it off and back on (I'm lazy!). Although, this would be relatively CPU intensive to the server (comparatively speaking anyway) - having to check all the furnaces adjacent chests every tick or every 20, etc.
Personally, as I also code, I think (a) would be much better in streamlining things. (b) would be awfully handy in making sure my wheat and tree farms always grow, but would considerably slow things down if many people use them a lot. When trying to optimize and speed things up, responding to events is generally much faster than checking every time for events!
The forges have been about 98%+ problem free for my server. Worked all day long no problem smelting cobblestone. Then two and a half stacks of clay, left for a couple hours, come back and two are off with brick in furnace, one furnace is on with nothing in it (three high furnace w/ two double chests). All the clay was processed though.
I know the bukkit changes have been pretty major and its probably hard to catch up with the 1.2 changes. Thanks for your work on Dwarfforge. I can set DebugLogEnabled if you need more information.
Here's the Bukkit version I'm running and the info messages from Dwarfforge.
CraftBukkit version git-Bukkit-1.2.3-R0.2-38-gf6e6922-b2083jnks (MC: 1.2.3) (Implementing API version 1.2.3-R0.3-SNAPSHOT)
[INFO] [DwarfForge] Enabling DwarfForge v2.8 [INFO] [DwarfForge] Configuration v.2.4 loaded. [INFO] [DwarfForge] Config is up to date [INFO] [DwarfForge] Restored 26 active Forges. [INFO] [DwarfForge] v2.8 enabled
@TheFluffey
cool thanks... and I have no idea atm why the furnaces are so iffy :-/
The probable fix for 1.2.3 R0.1 appears to be working with CraftBukkit version git-Bukkit-1.2.3-R0.2-b2060jnks (MC: 1.2.3) (Implementing API version 1.2.3-R0.2).
Thank you donredhorse!
please make a update its not work under 1.23R02 it´s a very nice mod
You possible R01 fix works on 123.R02, just tested it. (It was pretty tricky to download tho!)
@DonRedhorse
Created an in-depth and clear video on dwarfforge... Check it out?
http://www.youtube.com/watch?v=3XhfTA4IVUM
@DonRedhorse
No, not in 2.2 but AFTER 2.2 :)
@MightyFlyRudy
well if you find the issue in the code.... it is a feature I think... I don't know where I should have introduced this behaviour but Sorken says that it came up in 2.2 :-(
I think it is a random time interval there since the beginning, as I took over the code I don't want to change that.
@Cyberin
let's wait for the RB... they are doing a lot of changes and bug fixes atm to hunt down "ghosts"..
I'm testing your dev build for 1.2.3, updated bukkit and all...the forges don't always seem to stay lit after the first piece of fuel is used, sometimes they do, but the majority of time they turn off.
I have a chest full of cobble and coal, but each forge only cooks 8 cobble, then it turns itself off.
After checking the ones that are off they all have 1 piece of coal in them, and one stone in the completed section of the forge screen. (my output box is not full)
Some of the forges are also throwing out pieces of coal. I can't quite place when/why this is happening...but it happens a lot.
@DonRedhorse
The file you linked is working fine for me on CraftBukkit Build #2034. The furnaces do take a few punches to light sometimes, is that a bug or an intended feature?
ok.. there is a link in the op for 2.7 which should work with 1.2.3... I can't test though, please let me know
I will be trying to update dwarfforge in the next couple of days.. need to figure out where the code went in minecraft server
Also please note... there will be a feature freeze till the future of bukkit has become clearer.
I will only update bugs and make the plugin work with RB.
Also do to the fact that bukkit finds it funny to cram a lot of changes into the RB's just before they release them don't except any update to happen on the next day.