This mod adds chimney pipes, through which smoke from the fire or furnace goes up into the air.
REQUIRES ForgeEndertech library.
For greater immersion use with Pollution of the Realms.
Key features
- Lots of craftable chimneys from common building materials
- Variaty of smoke colors depending on the material of the chimney
- Particles collide and react to the wind
- Transparent chimneys for more exciting scenery
- Smoker block to generate any kind of smoke with gui configurable parameters
- Pumps to make smoke go down
- Vent ducts for connecting remote chimneys
Chimneys
Recipes
Connection Patterns
Tutorials
Advanced physics
- The more sources connected to the chimney, the more smoke you'll get
- Intensivity of the smoke depends on what obstacles and conductors it went through
- The variety of smoke colors depends on the sources and the path taken by the smoke
Customization
- Add custom smoke emitters
- Change smoke color, amount, intensivity, scale
- Use Smoker block to generate any kind of smoke with gui configurable parameters
- Create your own custom chimneys from any block you like
Modpacks
- Feel free to use the mod in any modpacks.
- You are allowed to use it without asking for permission.
Personally I don't really like the coloured smoke. Is there a way to disable it?
In reply to thafeeesh:
Yes, just set coloringFactor to 0 in config/adchimneys-client.toml
In reply to EnderLanky:
There's still occasionally a coloured particle.
This mod crashes my game on the loading screen every time. How do i fix this?
In reply to isaacaxy:
Make sure you have the correct version of ForgeEndertech installed (link for 1.12.2)
In reply to EnderLanky::
It still crashes. it goes to the thing where you can hit play to load the game and a little popup appears that says: The game crashed whilst initializing game
Error: java.lang.RuntimeException: Invalid id 4096 - maximum id range exceeded.
Exit Code: -1
In reply to isaacaxy:
Forge 1.12 only allows 4096 different blocks, and your modpack seems to exceed this limit. To fix this, either remove some mods that are using too many blocks or install NotEnoughIDs.
In reply to EnderLanky:
and im using this with Pollution of the Realms
I really enjoy how it looks to have a buncha engines chuffing away, I did notice one thing I cannot find an answer for. Is it possible to put a bend in a chimney?
For a more exact example, one of my preferred engine designs is a + shape, And while I can grab smoke from the bottoms and sides, if I try to grab from the top with a vent, it doesn't work, and I can't just go chimney->vent either it seems. For a better breakdown of what I am trying to do This is a slice of my engine block design.
Middle is the power cable, the two blue ones are pumping fuel, which leaves two blocks open for, well, chimneys in this case. Problem is the far right engine counts itself as if it has no output, and is sending clouds everywhere. I can expand wider of course to make it work, but I love keeping things compact.
Safe to say a bit open to ideas, but this feels like a little oversight as well that would be wonderful if fixed.
In reply to Famout:
No, you can't put a bend in a chimney. Why not place the following construction in front of the engine or replace the upper right vent with a chimney:
In reply to EnderLanky:
While not a bad idea, this design is made for scale, I put row after row of the engines in a line, so they would all need to be connected together, and right now the footprint per each slice is 1x3x3, and to properly exhaust it all it would need to be 1x3x4. All share the same fuel pipe, power pipe, but sadly not chimney. Plus bent chimney's are just nifty to look at.
So I'm trying to add custom chimney recipes for railcraft, and all of the recipes work but it won't localize or texture any of the items.
my config file for infernal bricks:
# Configuration file Chimney { CraftingRecipe { main { # Amount of output units. [range: 1 ~ 64, default: 8] I:amount=8 # Recipe components list. # Components should be represented by its ids. # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: [brick_infernal]] S:components < railcraft:brick_infernal > # Output unit id. # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: adchimneys:brick_infernal] S:output=adchimneys:brick_infernal # Shaped recipe pattern in format <nn nn> or <nnn nnn nnn>. # Where 'n' - number of recipe component (from 1 to 9). # Zero value (0) is for empty slot. # If pattern is empty, then recipe will be treated as shapeless. [default: 101 101 101] S:pattern=101 101 101 } } } Pump { CraftingRecipe { main { # Amount of output units. [range: 1 ~ 64, default: 4] I:amount=4 # Recipe components list. # Components should be represented by its ids. # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: [adchimneys:brick_infernal:1], [repeater], [blockCoal]] S:components < adchimneys:brick_infernal:1 repeater blockCoal > # Output unit id. # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: adchimneys:brick_infernal:2] S:output=adchimneys:brick_infernal:2 # Shaped recipe pattern in format <nn nn> or <nnn nnn nnn>. # Where 'n' - number of recipe component (from 1 to 9). # Zero value (0) is for empty slot. # If pattern is empty, then recipe will be treated as shapeless. [default: 121 232 121] S:pattern=121 232 121 } } } Vent { CraftingRecipe { main { # Amount of output units. [range: 1 ~ 64, default: 4] I:amount=4 # Recipe components list. # Components should be represented by its ids. # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: [adchimneys:brick_infernal]] S:components < adchimneys:brick_infernal > # Output unit id. # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: adchimneys:brick_infernal:1] S:output=adchimneys:brick_infernal:1 # Shaped recipe pattern in format <nn nn> or <nnn nnn nnn>. # Where 'n' - number of recipe component (from 1 to 9). # Zero value (0) is for empty slot. # If pattern is empty, then recipe will be treated as shapeless. [default: 101 000 101] S:pattern=101 000 101 } } } infernalBrick { # Defines a color in ARGB (Alpha, Red, Green, Blue) hex format (0xaarrggbb) which will be applied to the smoke. # The alpha channel of this color (aa) determines probability of applying (ff - always, 7f - 1/2, 00 - never). # [default: 0x00000000] S:color=0x11794334 # Set to 'false' if you don't need this unit. [default: true] B:enabled=true # Defines how many hits it takes to break the block. # -1 makes the block indestructible. [range: -1.0 ~ 3.4028235E38, default: 0.0] S:hardness=2.0 # Id is a basic unit (block or item) identifier in <modId:unitName:meta> format. # ModId can be omitted for vanilla items. Meta can be omitted too if it equals 0. # UnitName must be lowercase, words separated by '_', words order - from private to common (example: black_iron_ore). # Unit name will be automatically converted to ore dictionary name with reverse word order (example: oreIronBlack). # Use '*' char as meta value to specify all possible values. # To define multiple block states, you can use block properties instead of meta. The format is <modId:blockName:[prop1=value1, prop2=value2]> # Also you may use just ore dictionary name as full id. # [default: railcraft:brick_infernal] S:relatedBlockId=railcraft:brick_infernal # Defines the block resistance to explosions. [range: 0.0 ~ 3.4028235E38, default: 0.0] S:resistance=30.0 }is there something I'm doing wrong or is this a bug?
chimneys version 1.12.2-3.5.15.0
In reply to DUDEbehindDUDE:
Adding a config is not enough, you're gonna need to add and load a resource pack where you have specified all textures and localized strings (example).
In reply to EnderLanky:
Ah ok, so what exactly is the purpose of "S:relatedBlockId" at the end of the conflig file?
In reply to DUDEbehindDUDE:
To get the block properties such as material, hardness, resistance, etc., and apply them to the chimney.
so the advanced chimneys mod isn't working for me, i have ForgeEnderTech-1.12.2-4.5.4.0 and 1.12.2-3.5.15.0 for the chimneys mod. I've made sure the pumps have a lever on them for the redstone signal and still the pumps and vents don't suck up pollution. if anyone could help that would be greatly appreciated. Thanks
Update*
The pumps work if they are directly connected to the machine then to a chimney, but the pump and vents don't work together
In reply to robsobreezy:
Make sure you are using the latest version of PotR, because there was a bug with missing configs in previous version that prevented pollution from going through the vents.
Could you please make a compatibility with Industrial Foregoing? It seems that the pitiful generator doesn't pollute, I don't know about the other generators yet ¯\_(ツ)_/¯
I can't seem to find the recipe in jei or craft them in 1.12.2 pollution of the realms works fine
In reply to trainman513:
Make sure you have the correct version of the mod for 1.12