#❗-1-18-experimental
1 messages · Page 31 of 1
This happens whenever I load a chunk and the old chunks get overwritten with new generation
Can you provide more info or that was it?
I am going from 1.12 to 1.18, do I need to go through the versions in between?
You shouldn’t need to
@peak pulsar can you provide a small sample of your region file where those old to new chunk conversion is happening? You can DM me 
Okie I will go wake up the rat king. I mean spottedleaf
i am already here
😳
Protein is protein, right
you don't have an overworld?
That is from the overworld
I didn't have any issues with nether and end chunks since they didn't generate new terrain
is this during a force upgrade?
No
can i get more of the log
latest.log by @calm bone: https://paste.gg/44633891c92c470faf0e1433c83539ca
i see what might be the problem there
what's happening there is really dumb
can you test this for me, can you disable spawn loading in paper.yml (keep-spawn-loaded) and then teleport to your spawn and see if it happens
That fixed it, thanks!
ok but now the world is generating below y 0
I disabled that in the spigot config
i mean did you teleport to spawn to see?
yes
ok
entity tracker packets
there's a lot of them
uh i have no idea about the below zero gen stuff
i can test that locally
Well it’s not going to delete previously generated stuff, if you disabled it after already loading up the world.
I imagine if you didn’t disable it before even starting the server, the spawn chunks would have that retrogen done
I did
Is it not working cause of a paper change? It was just added to spigot, so I imagine they tested it there.
I don't
i suspect it's specifically not working for 1.12 and lower worlds
spigot's check their is pretty bad
there
we can fix that check
uh maybe no fix for that
spigot's config is actually really badly written 
can you stop spamming this channel with trash please
thanks
@peak pulsar I will fix the spawn loading stuff, really no idea about the spigot config though, might be able to work something
Ok, thanks
i can't produce the original spawn loading stuff actually
you're gonna need to give me more of the world, specifically the structure data
maybe more of the spawn too
It's fine I have the world working
And i just world edited out the stuff below y 0 since it was a small area
This is rather confusing, kinda suggests there is another RCE out there before the #108 build?
technically there is
but it's not one that can be abused without already have access
The rat king has saved the day @sudden bison
Well yea, at some point we'll see another 0day fresh exploit. but is making the switch from 107 to 108 as important as it was between #65 and #66 when log4j appeared initially?
yea thats why i got confused xD
there's been quite a few log4j updates between 66 & 108 already
Yea, so the sudden catclip made me wonder >.>
So basically, not to worry~~, we're still flying half a ship~~?
Log4JWOBS 
Can we just stop with the dum memes over even dummer "exploits"?
It's really boring
And has nothing to do with this channel
1.18.1 works fine. 
No, the new "exploit" isn't an issue for 99.999% of servers. An attacker would need to modify your log config file, at which point this exploit would be the least of your concerns
if it was an urgent update there would've been an announcement
okay sounds good, thank you! just really paranoid
Can you verify it’s server not sending? It can also be client not rendering as well.