I am pretty sure that some mod is adding something to the (treasure?) inventory of the Nightmare that TheKentington did not foresee being possible. It's probably a conflict with another mod that you can not do anything about. This should get fixed though...
What is it, you use a Nightmare's inventory for? I am not very familiar with the content of TH I am afraid.
It's a horse upgrade, so you use the inventory for a saddle and horse armor. This issue is preventing me from putting a saddle on it, making it mostly useless. I'm not sure what could be adding something, but I did check and it happens both with the Nightmare that I created and with one created from a spawn egg, so it isn't something that my particular Nightmare has wrong with it.
If you take a blood sample from a leashed creature, cloning it clones the leash! (Which breaks and drops when you open the jar.)
Rollback Post to RevisionRollBack
I did some CraftTweaker scripts for Mystical Agriculture. They fill in a couple of small gaps in MA, and also let you make or duplicate not only vanilla plants, but the blocks, plants and wood from Quark and Biomes O'Plenty. Also spawn eggs for most vanilla mobs! The scripts are here on Github.
i know the crash says "at codechicken.wirelessredstone.addons.WRAddonEventHandler.serverTick(WRAddonEventHandler.java:52)" but even with that mod removed my custom modpack still crashes with only this mod, without it my pack works with no problem.
The Meaning of Life, the Universe, and Everything.
Join Date:
9/4/2013
Posts:
45
Member Details
zenth_ , same way really, if you look at the normal golems, the stronger a golem is the slower it is. strong gives better carry capacity. think all powder golems have only one upgrade, even if you use it on a block of thaumium to make a bootleg thaumium golem. if you attach a core you can pick it up and give it the advanced golem upgrade.
zenth_ , same way really, if you look at the normal golems, the stronger a golem is the slower it is. strong gives better carry capacity. think all powder golems have only one upgrade, even if you use it on a block of thaumium to make a bootleg thaumium golem. if you attach a core you can pick it up and give it the advanced golem upgrade.
The part about upgrade capacity is false. I've had Obsidian Totam Golems and Bookshelf Golems that had two upgrade slots. I'm not sure what determines it though.
Uh... This might be a goofy question but what's up with the Vortex Attenuators? I can't seem to get them to work. Even if I somehow clear blocks like transduction amplifiers out in time before a vortex goes haywire (which is easier said than done with four of them as well as the stabilizers and tranducers, believe me) and have nothing in the way of the six attenuators, they don't seem to do anything to it. And once the vortex starts to swallow stuff there's nothing I can do to stop it, especially since it tends to swallow the attenuators while they're active and often doesn't stay open as long as advertised.
I have all the research and 6 attenuators backed by redstone blocks every time; is it random chance or what?? I have yet to make a single one work.
Uh... This might be a goofy question but what's up with the Vortex Attenuators? I can't seem to get them to work. Even if I somehow clear blocks like transduction amplifiers out in time before a vortex goes haywire (which is easier said than done with four of them as well as the stabilizers and tranducers, believe me) and have nothing in the way of the six attenuators, they don't seem to do anything to it. And once the vortex starts to swallow stuff there's nothing I can do to stop it, especially since it tends to swallow the attenuators while they're active and often doesn't stay open as long as advertised.
I have all the research and 6 attenuators backed by redstone blocks every time; is it random chance or what?? I have yet to make a single one work.
First, make sure you use levers to power the Transduction Amps and the Transducer. The reason for this is that the Vortex immediately swallows the blocks surrounding it in a three-by-three cube, so Redstone Blocks often get in the way.
Second, make sure that there are as many blocks in the Vortex's range as possible, that way it won't eat the Attenuators in time for them to work. I've found the easiest way to do this is my making walls entirely encasing the setup one block behind the Attenuators.
Third, make sure the Attenuators are the right distance away from the Vortex. Their must be at most eight blocks and at least two blocks between them and the Node itself (Not the Trans Amps or anything else).
If you are still confused, I can show you a picture of the setup I always use, which is as compact as possible and has never failed on me.
First, make sure you use levers to power the Transduction Amps and the Transducer. The reason for this is that the Vortex immediately swallows the blocks surrounding it in a three-by-three cube, so Redstone Blocks often get in the way.
Second, make sure that there are as many blocks in the Vortex's range as possible, that way it won't eat the Attenuators in time for them to work. I've found the easiest way to do this is my making walls entirely encasing the setup one block behind the Attenuators.
Third, make sure the Attenuators are the right distance away from the Vortex. Their must be at most eight blocks and at least two blocks between them and the Node itself (Not the Trans Amps or anything else).
If you are still confused, I can show you a picture of the setup I always use, which is as compact as possible and has never failed on me.
I suppose a lever would help; I'll just have to remember to build an obsidian wall around it all later.. Pretty much every lan or server bit I hold tends to devolve into people trying to blow me up
I have pocket planes spawning in my overworld, is there anything I do to fix this?
Yes, its a Biomes O' Plenty conflict. Because Thaumic Horizon's config isn't available yet, you have to go into the BoP confing, find the biome with the Id 69, and change it to something that doesn't interfere with other biomes. To make sure it doesn't, you can dump a list of all biomes with NEI
First, make sure you use levers to power the Transduction Amps and the Transducer. The reason for this is that the Vortex immediately swallows the blocks surrounding it in a three-by-three cube, so Redstone Blocks often get in the way.
Second, make sure that there are as many blocks in the Vortex's range as possible, that way it won't eat the Attenuators in time for them to work. I've found the easiest way to do this is my making walls entirely encasing the setup one block behind the Attenuators.
Third, make sure the Attenuators are the right distance away from the Vortex. Their must be at most eight blocks and at least two blocks between them and the Node itself (Not the Trans Amps or anything else).
If you are still confused, I can show you a picture of the setup I always use, which is as compact as possible and has never failed on me.
I am trying the same thing and pictures would really help.
I am trying the same thing and pictures would really help.
Here you go:
Exterior View:
Note that I used warded glass in this picture for the walls, you would actually want to use stone or stick it in a cave or something.
Side Attenuator:
This is the structure of the Attenuators on the side, pattern is: Node, Amplifier, Lever, Attenuator, Redstone Block. The top one is similar, except vertical.
Bottom Attenuator:
The bottom Attenuator pattern is: Node, Stabilizer, Air, Attenuator, Redstone Block.
Post Vortexation:
Proof of success (I placed a couple of blocks for it to eat while it was being created, because it can't actually eat warded glass).
There is of course a non-zero chance of it failing, but always keep extra Attenuators and Redstone Blocks on hand, I recommend a form of flight to counteract the sucking action of the Vortex, and for each edible block you place in the vicinity, your chances of success increase. I personally have never failed to the point of the Vortex collapsing into flux.
Unfortunately I don't have the server-side log, but here's what I've got:
[10:27:05] [Netty Client IO #2/ERROR] [FML/]: NetworkDispatcher exception
io.netty.handler.codec.DecoderException: java.io.IOException: The received string length is longer than maximum allowed (37 > 32)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:263) ~[ByteToMessageDecoder.class:?]
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:131) ~[ByteToMessageDecoder.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:337) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:323) [DefaultChannelHandlerContext.class:?]
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:173) [ByteToMessageDecoder.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:337) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:323) [DefaultChannelHandlerContext.class:?]
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103) [MessageToMessageDecoder.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:337) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:323) [DefaultChannelHandlerContext.class:?]
at io.netty.handler.timeout.ReadTimeoutHandler.channelRead(ReadTimeoutHandler.java:149) [ReadTimeoutHandler.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelRead(DefaultChannelHandlerContext.java:337) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelRead(DefaultChannelHandlerContext.java:323) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:785) [DefaultChannelPipeline.class:?]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:100) [AbstractNioByteChannel$NioByteUnsafe.class:?]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:480) [NioEventLoop.class:?]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:447) [NioEventLoop.class:?]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:341) [NioEventLoop.class:?]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) [SingleThreadEventExecutor$2.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_40]
Caused by: java.io.IOException: The received string length is longer than maximum allowed (37 > 32)
at net.minecraft.network.PacketBuffer.func_150789_c(SourceFile:134) ~[et.class:?]
at net.minecraft.network.play.server.S2DPacketOpenWindow.func_148837_a(SourceFile:58) ~[gn.class:?]
at net.minecraft.util.MessageDeserializer.decode(SourceFile:40) ~[ez.class:?]
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:232) ~[ByteToMessageDecoder.class:?]
... 19 more
[10:27:05] [Netty Client IO #2/INFO] [THAUMCRAFT/]: Restoring client configs.
[10:27:05] [Netty Client IO #2/INFO] [Galacticraft/]: Unregistered Dimension: -30
[10:27:05] [Netty Client IO #2/INFO] [Galacticraft/]: Unregistered Dimension: -29
[10:27:05] [Netty Client IO #2/INFO] [Galacticraft/]: Unregistered Dimension: -28
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Disconnect from server: Unregistering RFTools dimensions
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 2
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 3
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 4
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 5
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 6
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 8
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 9
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 10
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 11
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 12
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 13
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 14
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 15
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 16
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 17
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 18
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 19
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 20
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 21
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 22
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 23
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 24
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 25
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 26
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 27
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 28
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 29
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 30
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 31
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 32
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 33
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 34
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 35
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 36
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 37
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 38
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 39
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 40
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 41
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 42
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 43
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 44
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 45
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 46
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 47
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 48
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 49
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 50
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 53
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 54
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 55
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 56
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 59
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 61
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 62
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 63
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 64
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 65
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 66
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 67
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 68
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 69
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 70
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 71
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 72
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 73
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 74
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 75
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 76
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 77
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 78
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 79
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 80
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 81
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 82
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 83
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 84
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 85
[10:27:05] [Netty Client IO #2/INFO] [mcjty.rftools.RFTools/]: Unregister dimension: 86
[10:27:05] [Netty Client IO #2/ERROR] [FML/]: NetworkDispatcher exception
io.netty.handler.codec.DecoderException: java.io.IOException: Packet was larger than I expected, found 3 bytes extra whilst reading packet 2
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:263) ~[ByteToMessageDecoder.class:?]
at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:196) ~[ByteToMessageDecoder.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelInactive(DefaultChannelHandlerContext.java:237) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelInactive(DefaultChannelHandlerContext.java:223) [DefaultChannelHandlerContext.class:?]
at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:214) [ByteToMessageDecoder.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelInactive(DefaultChannelHandlerContext.java:237) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelInactive(DefaultChannelHandlerContext.java:223) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.ChannelInboundHandlerAdapter.channelInactive(ChannelInboundHandlerAdapter.java:75) [ChannelInboundHandlerAdapter.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelInactive(DefaultChannelHandlerContext.java:237) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelInactive(DefaultChannelHandlerContext.java:223) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.ChannelInboundHandlerAdapter.channelInactive(ChannelInboundHandlerAdapter.java:75) [ChannelInboundHandlerAdapter.class:?]
at io.netty.handler.timeout.ReadTimeoutHandler.channelInactive(ReadTimeoutHandler.java:143) [ReadTimeoutHandler.class:?]
at io.netty.channel.DefaultChannelHandlerContext.invokeChannelInactive(DefaultChannelHandlerContext.java:237) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelHandlerContext.fireChannelInactive(DefaultChannelHandlerContext.java:223) [DefaultChannelHandlerContext.class:?]
at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:767) [DefaultChannelPipeline.class:?]
at io.netty.channel.AbstractChannel$AbstractUnsafe$5.run(AbstractChannel.java:558) [AbstractChannel$AbstractUnsafe$5.class:?]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:354) [SingleThreadEventExecutor.class:?]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:348) [NioEventLoop.class:?]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) [SingleThreadEventExecutor$2.class:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_40]
Caused by: java.io.IOException: Packet was larger than I expected, found 3 bytes extra whilst reading packet 2
at net.minecraft.util.MessageDeserializer.decode(SourceFile:42) ~[ez.class:?]
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:232) ~[ByteToMessageDecoder.class:?]
... 19 more
[10:27:05] [Client thread/DEBUG] [FML/]: Reverting to frozen data state.
[10:27:05] [Client thread/INFO] [FML/]: Applying holder lookups
[10:27:05] [Client thread/INFO] [FML/]: Holder lookups applied
[10:27:07] [Client thread/INFO] [Mekanism/]: VoiceServer: Stopping client connection...
[10:27:07] [Client thread/INFO] [Mekanism/]: Finished loading Cardboard Box blacklist (loaded 0 entries)
[10:27:07] [Client thread/INFO] [Mekanism/]: Reloaded config.
I'm fairly certain that everything prior to that is just loading in. If you need more, let me know.
This sounds like an awesome add-on. I'll definitely check this one out.
It's a horse upgrade, so you use the inventory for a saddle and horse armor. This issue is preventing me from putting a saddle on it, making it mostly useless. I'm not sure what could be adding something, but I did check and it happens both with the Nightmare that I created and with one created from a spawn egg, so it isn't something that my particular Nightmare has wrong with it.
If you take a blood sample from a leashed creature, cloning it clones the leash! (Which breaks and drops when you open the jar.)
i'm getting a crash with this mod installed.
http://pastebin.com/wEAB4bNB
here's my fml_client_latest.log, its too big for pastebin: http://puu.sh/jMC2J/e1978f0bce.log
i know the crash says "at codechicken.wirelessredstone.addons.WRAddonEventHandler.serverTick(WRAddonEventHandler.java:52)" but even with that mod removed my custom modpack still crashes with only this mod, without it my pack works with no problem.
any idea what it could be?
remove mods until it stops. note the mod you removed last.
it says different things every time. something about openmods/fakeplayer can come up and another crash could be scala something.
i cant find ant mod showcases for this mod
zenth_ , same way really, if you look at the normal golems, the stronger a golem is the slower it is. strong gives better carry capacity. think all powder golems have only one upgrade, even if you use it on a block of thaumium to make a bootleg thaumium golem. if you attach a core you can pick it up and give it the advanced golem upgrade.
The part about upgrade capacity is false. I've had Obsidian Totam Golems and Bookshelf Golems that had two upgrade slots. I'm not sure what determines it though.
what would instilled loyalty even do to a golem?
Make them follow you, I assume? That would be a pain to get working for every golem type (unless it makes it one type that does the following.)
Profile pic by Cheshirette c:
Unless he completely made his own mob class for golems they should all just have a tame setting that makes them follow like a wolf
Current Mod: Armerger | Light Drafter
Uh... This might be a goofy question but what's up with the Vortex Attenuators? I can't seem to get them to work. Even if I somehow clear blocks like transduction amplifiers out in time before a vortex goes haywire (which is easier said than done with four of them as well as the stabilizers and tranducers, believe me) and have nothing in the way of the six attenuators, they don't seem to do anything to it. And once the vortex starts to swallow stuff there's nothing I can do to stop it, especially since it tends to swallow the attenuators while they're active and often doesn't stay open as long as advertised.
I have all the research and 6 attenuators backed by redstone blocks every time; is it random chance or what?? I have yet to make a single one work.
First, make sure you use levers to power the Transduction Amps and the Transducer. The reason for this is that the Vortex immediately swallows the blocks surrounding it in a three-by-three cube, so Redstone Blocks often get in the way.
Second, make sure that there are as many blocks in the Vortex's range as possible, that way it won't eat the Attenuators in time for them to work. I've found the easiest way to do this is my making walls entirely encasing the setup one block behind the Attenuators.
Third, make sure the Attenuators are the right distance away from the Vortex. Their must be at most eight blocks and at least two blocks between them and the Node itself (Not the Trans Amps or anything else).
If you are still confused, I can show you a picture of the setup I always use, which is as compact as possible and has never failed on me.
I suppose a lever would help; I'll just have to remember to build an obsidian wall around it all later.. Pretty much every lan or server bit I hold tends to devolve into people trying to blow me up
I have pocket planes spawning in my overworld, is there anything I do to fix this?
Yes, its a Biomes O' Plenty conflict. Because Thaumic Horizon's config isn't available yet, you have to go into the BoP confing, find the biome with the Id 69, and change it to something that doesn't interfere with other biomes. To make sure it doesn't, you can dump a list of all biomes with NEI
I am trying the same thing and pictures would really help.
Here you go:
Exterior View:
Note that I used warded glass in this picture for the walls, you would actually want to use stone or stick it in a cave or something.
Side Attenuator:
This is the structure of the Attenuators on the side, pattern is: Node, Amplifier, Lever, Attenuator, Redstone Block. The top one is similar, except vertical.
Bottom Attenuator:
The bottom Attenuator pattern is: Node, Stabilizer, Air, Attenuator, Redstone Block.
Post Vortexation:
Proof of success (I placed a couple of blocks for it to eat while it was being created, because it can't actually eat warded glass).
There is of course a non-zero chance of it failing, but always keep extra Attenuators and Redstone Blocks on hand, I recommend a form of flight to counteract the sucking action of the Vortex, and for each edible block you place in the vicinity, your chances of success increase. I personally have never failed to the point of the Vortex collapsing into flux.