Mystcraft Dense Ore Age Causing Client Disconnect

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

merfed

New Member
Jul 29, 2019
4
0
0
What OS are you running?
Win 7 Ultimatex64

Are you using minecraft hosting provider or a dedicated/local server not designed for minecraft?
Local

What version of FTB are you using? (Dont just say latest tell us the version)
1.0.5

Did you add any mods to the server pack?
Mo'Creatures and Metallurgy, even when disabled it will still produce this problem.

What are your server specs?
8gb Ram, 3.2ghz cput

A good detailed paragraph about the problem/B]
Anyone who connect to the server (besides myself) when entering a mystcraft age with dense ore's will cause a client crash. Either end of stream or more commonly internal exception: java.net.SocketTimeoutException:Read timed out.
 

Greedseed

New Member
Jul 29, 2019
1,107
0
0
Have noticed this as will with some of my beta testers. It seems some systems have issues with a high number of dence ore's

Keep in mind you added Metallurgy with will also generate more ore. You crash your client due to the huge amount of world gen it needs to handle ( Ore gen).
Also Mo'Creatures is not helping on the huge loads.
 

christophocles

New Member
Jul 29, 2019
10
0
0
Did you disable instability? Those blocks that consume the entire world make my clients disconnect from the overload. There's an option in the mystcraft config file to turn that specific block off.
 

Greedseed

New Member
Jul 29, 2019
1,107
0
0
Even instability disabled can it still crash you.

We had a test world:

Dense ore's: 10
Extra mods: None
Instability: Disabled (completely in config)

Still some players of my beta team crashed in that world. Others did not.

Its the ore generation most of the time. When you walk you will request and generate 256 by 16 by 16 chunks and normaly 8 all around you. So that is about 1228800 blocks you render. Normaly a smalelr amount would be ore. Most couble and dirt. Now you make it 10 times as complex to render the ore's.
 

beringtom

New Member
Jul 29, 2019
134
0
0
So what error did your clients get? log files from 2-3 of them, with system specs aswell would be a nice start... (post them in spoilers, or attach the txt files)
 

merfed

New Member
Jul 29, 2019
4
0
0
Have noticed this as will with some of my beta testers. It seems some systems have issues with a high number of dence ore's

Keep in mind you added Metallurgy with will also generate more ore. You crash your client due to the huge amount of world gen it needs to handle ( Ore gen).
Also Mo'Creatures is not helping on the huge loads.

Yeah it seems to be ore gen. I tested 3 ages with 3 dense ore's, 2 and then 1 dense ore symbols. The symbol with one only caused an occasional disconnect while the others caused instant, predictable disconnects every time. I'm sure metallurgy isn't helping, but the results are the same each time I disabled metallurgy and mo'creatures completely.

I'm going to see if it's an issue with my connection aswell, by moving to a dedicated server sometime this weekend.
 

Vauthil

New Member
Jul 29, 2019
1,491
-14
1
I had this issue repeatedly back in 1.3.2 as well with people with less-than-optimal latency connecting to my server (i.e. everybody in North America was fine -- my server is a dedicated one in Vancouver, BC -- while anybody Oceanic -- Australia, NZ, Singapore, et al. -- would enter the forced-stable multi-Dense Ores worlds and I'd basically have to retrieve them really fast with /tpx in the couple of seconds they could connect before getting disconnected again).

Carry away: you may have a better time with the dedicated server, but people with poor ping/connectivity will probably still have this problem. Even more fun is when you get a few of them doing it at 3am while you're actually sleeping for once and the rapid succession connect/disconnect finally makes the server give up and die (yes, it eventually does that, I had to finally institute an iptables connection throttle on that port because people wouldn't listen when I said "stop doing that").

How I don't have this happen now: I don't use Dense Ores, particularly not a metric crapton of them. Simple as that, really. (This go round I even opted to not Creative Mode in a Notebook for once; pro is actually having to discover symbols and some of the "holy crap" moments that brings, con is the whole let's-have-ghost-weather-on-the-overworld thing).