World Gen bug with SOTS and AWG

[primal folio]

Generated a world with a large size, 64392 x 18212 blocks, I think the issue arises because of the size, not because of an incompatible world gen feature, all logs provided, would like to figure out what is going on

Had a similar bug with Thorium, direwolf has given me a beta version of Thorium with a fix for the bug in that mod
Hopefully we can do something about it for Thorium

Actually, I have no idea if SOTS is responsible for this at all, I did only try this on one seed, the seed of...1
Will do more testing, on seed number 2 this time

Will also try seed 1 without any extra mods added

[copper lodge]

As the title of the post implies, this is a result of crossmodding

[primal folio]

I am also unsure if it is the issue of cross modding, random crash, AWG world gen, it could be any multitude of things that could cause it

Blaming it on just "Cross mod" is a bit futile, like yea, obviously there's some cross mod going on, but is it the fault of Calmity? Thorium? SOTS? Fargo? AWG? I don't know

But I am trying the generation, same seed, on the same world size, without any extra mods

If it still has the same issue with only AWG installed, then it's a fault of one of those two mods, I am already in contact with the dev of AWG, so the only other possible issue would be Calamity, so I'm just covering my bases here

Why X

[pliant apex]

Advance Worldgen is not supported yet

please wait til after Sunken Sea Overhaul

[primal folio]

Cool, but that doesn't really answer any questions
Is this a Calamity issue, AWG, Thorium, SOTS?

[pliant apex]

the issue happens due to issues on worldgen with several things in Calamity, we know and have been dealing with em while changing worldgen for the next big update

[pliant apex]

Cal + AWG

its only an issue when both mods are combined

[primal folio]

There is a known workaround for that, just putting a 2 at the end of the world length fixes it

[pliant apex]

altho this log tells that more stuff is having issues

[pliant apex]

which is not a guaranteed fix

[primal folio]

Is there anything the AWG dev should know?

[pliant apex]

people have already pestered him to death

[primal folio]

It's worked 99% of the time for 2x large world sizes

[pliant apex]

and we even got a pull request that fixes some of the issues

but more stuff needs to be changed apparently

[primal folio]

Aha

So, tldr, it's being handled

[pliant apex]

with the new SSO gen it works fine

but we cant release that yet

[primal folio]

And of course that's an internal build that I can't bug test on correct?

[pliant apex]

yes

[primal folio]

And there's no chance I could become a bug tester?

Cuz lemme tell you
If something can break
I WILL break it

[pliant apex]

i will still need to check why Sots and fargos failed to gen tho

[primal folio]

You gon' handle that then?

[pliant apex]

you already failed point 1

so no

[primal folio]

Lemme guess
Asking to become a tester

[pliant apex]

correct

[primal folio]

Sheisse

Alright, well, I'm still generating the world without SOTS and stuff, just Cal and AWG, and then I will generate one more world with a different seed, and send my logs, just in case something else pops up. y'never know

[pliant apex]

rn im on my phone, to check the log files I will need to get to my laptop, so wait about 5 hours maybe

[primal folio]

Das okie

[pliant apex]

that would be helpful

[primal folio]

Takes about 30 minutes to generate ONE world

I don't want to disable anything for fear that one tiny thing could fuck it up
Also, tangent, I hate when the ice biome generates like that

Also as another note
Bug reporting seems waaaay more friendly now than it used to be
Had I reported this a year ago, I would have been told "Turn off the other mods"
Glad to see things have changed :3

[pliant apex]

the latter is mostly due to having other mods not known to have conflicts, or just not showing that you will help in any way.

You are doing well and followed every rule and are even volunteering to help us investigate the issue

If you came here demanding a solution (which happens very often on other reports) then yes we would have told you to turn mods off

[primal folio]

Time to try another seed

Here we go again

[primal folio]

Wait, there are rules?

[primal folio]

This is gonna take a long time

Found a new bug

Will try seed 3 now

[pliant apex]

#1052330262492631071 <— the rules

[primal folio]

Read

Generating a new world, again, again, again

[primal folio]

Same thing, every time

@pliant apexMight I ask
How are we sure this bug won't happen on the new build?

Shall I give you my exact world gen specifications so that you can test it?

[pliant apex]

I already tested it months ago

[primal folio]

With an absurdly large world?

[pliant apex]

Brimstone crags had an issue and I think that is solved in public but sulphur sea is the other part and that is not on public yet and we did change a bunch of stuff on it

[primal folio]

I'd feel better if I can give you the specifications, and you test it out :3

[pliant apex]

#calamity-update-talk message

[pliant apex]

i could take a look on the dev build again

[primal folio]

Oh neat, but that does look smaller

Well, I always do
Both Ores, Crimruption
64392 x 18212 (because of Brimmy Generation being wonky)

So, if you're willing to test that, that would be neat :3

[pliant apex]

brim crags gen is already fixed next patch

[primal folio]

Yay

[primal folio]

Now it's crashing 100% of the time on the jungle temple

[pliant apex]

Maybe multiple mods are modifying it?

[primal folio]

Mmm, no, even with just Cal and AWG is does it, on the same seed