What does opis say about your mean tick time?
Also check the Handler tab for entities that aren't related to specific blocks.
Does any one know why the toast Will not take. i am doing the Barging Rights. and any thing that has to be smelted will not work. and the white glass is still Broken... sorry
Does any one know why the toast Will not take. i am doing the Barging Rights. and any thing that has to be smelted will not work. and the white glass is still Broken... sorry
The fluiduct seems to not be set to output.So it seems I cannot for the life of me pump life essence into my blood altar, I've tried every side and I've even tried both transfer pipes and fluiducts, I admittedly updated BM due to the very easily abusable dupe that is in the version shipped with the pack but even after rolling back, destroying and replacing the altar and all that jazz, nothing works.
Am I maybe doing something wrong? I checked to see if it was on a chunk boundary, it's not.
Check under Network and handlers. There is a rare bug in Blood Magic that I thought was solved. If its still there the Blood Altar will be spamming packets.
What anti-virus do you use. I had a problem with McAfee going particularly crazy when I ran minecraft scanning every packet going to/from the internal/external servers. Once I adjusted my anti-virus my problems cleared up. For McAfee, if you have one of the higher tier versions of it, there is a setting for "On Demand" scanning "Thoroughness" that you can adjust on a program by program basis.
- MCPC+ resetting the quest book
Looks like the Thermal Expansion grid tick handler is unusually high. What version of the pack are you running?
Possibly have a lot of "stuffed" Thermal Expansion item ducts. Most common cause is large arrays of crucibles being fed by igneous extruders with no place for the overflow of cobble to exit the pipes. Other culprits for "stuffed" ducts can be auto activators being over-fed items for sieving and planters that are constantly full of seeds/saplings..
There is no output setting for fluiducts....The fluiduct seems to not be set to output.
Try whacking the connection with a crescent hammer. You'd be surprised =)There is no output setting for fluiducts....
Looks like the Thermal Expansion grid tick handler is unusually high. What version of the pack are you running?
Possibly have a lot of "stuffed" Thermal Expansion item ducts. Most common cause is large arrays of crucibles being fed by igneous extruders with no place for the overflow of cobble to exit the pipes. Other culprits for "stuffed" ducts can be auto activators being over-fed items for sieving and planters that are constantly full of seeds/saplings..
I am running Agrarian Skies 2.1.4, I changed the config in TE so that pipes don't back stuff. I was curious if my 48 crucible array was the cause of the lag, so I created the exact same thing in a clean world. My ping in that world is normal, but the network is the same and and the Thermal Expansion Tick Handler is 120. So it's not the cause.
Besides that array I have no itemducts and only almost no fluiducts.
I am running Agrarian Skies 2.1.4, I changed the config in TE so that pipes don't back stuff. I was curious if my 48 crucible array was the cause of the lag, so I created the exact same thing in a clean world. My ping in that world is normal, but the network is the same and and the Thermal Expansion Tick Handler is 120. So it's not the cause.
Besides that array I have no itemducts and only almost no fluiducts.
If you are running 2.1.4 then there should have been no reason to modify the TE config. Can you elaborate on what you changed? Only other thing I can think of is providing a world download so I can load it up on my install and see if I can diagnose it that way.
I edited this line in the COFH config.
I:MaxItemsInStuffedDucts=0
That shouldn't be causing any lag, it just makes sure there is no buildup in itemducts.
If you really want to download my world and see if it is just as laggy for you, here you go. I've basically turned off and ripped apart a lot of the world trying to diagnose the problem, you probably should run it on peaceful because I removed my magnum torch to check that.