neoforge-121.8[[oshi.util.FileUtil/]: No oshi.architecture.properties file found from ClassLoader cpw.mods.modlauncher.TransformingClassLoader@7e83992]
neoforge:1.21.8-21.8.35 architectury:17.0.8 not long after the msg is in the console the game just kicks you from world and after you try to go back to worlds they not there doesn't matter if new world or old once you gen anew chunk it just dies off and you have to force close the game by ending the task
not sure if neoforge or archi or a dependant of archi since it doesnt give me much to go on Logs:
confirmed without architectury no freeze ups or crashes after more thne a hour of playing and exploring
tested without these mods turned on and everything is smooth no lock ups ect
Same problem here with Chococraft 0.14.1 or 0.14.0 1.21.8 neoforge REI also requires the Architectury dependency, I don't see any problems as long as Chococraft is disabled. Also tested in a new world freshly created without any other mods than Chococraft and architectury and the disconnection still occurs.
So I think the problem is located on Chococraft and not Architectury.
oh okays i will test further does makesense anything that is world gen related
Can it be reproduced with just Chococraft and Architectury?
Can it be reproduced with just Chococraft and Architectury?
let me make a quick test folder
Can it be reproduced with just Chococraft and Architectury?
yes it can takes about 10 mins then kicks from world
New version is being built and should be up shortly
It was reading the wrong min and max group size and weight value. Meaning when it tried to spawn a Chocobo it's max might be below the minimum... which MC doesn't like :)
It was reading the wrong min and max group size and weight value. Meaning when it tried to spawn a Chocobo it's max might be below the minimum... which MC doesn't like :)
oh damm that is a big derp
It was reading the wrong min and max group size and weight value. Meaning when it tried to spawn a Chocobo it's max might be below the minimum... which MC doesn't like :)
tested with new versions and it seems to be fixed now