I don't know what exactly about Selene 1.17.7 crashes the servers, but it is explicitly stated to be a bug on Selene's end. Here is the crash rapport so you can take a look.

also are the ones that are having this issue using everycompat too? What about snowy spirit? I need to figure out if it's even a supplementaries issue. I did try to load up a world with the buggy versions and the load it up with today's version and everything got remapped fine so I'm not sure

I only use Supplementaries. Also, I'm sorry, I didn't get a crash log because I manually closed it that session. Sorry :(

I get a hang when loading a single player world with Selene Lib 1.17.7. There's no crash log because the game becomes unresponsive and has to be force killed. I think the last version I loaded the 2 worlds I have to test with was 1.17.5. I have these Selene Lib dependencies:

• Immersive Weathering 1.2.11
• Supplementaries 1.4.5

should be a world that has had one of the 1.17.0+ versions (I dont remember exactly when it was introduced but was very recent). Also thanks :D

[18:34:57] [main/WARN] [ne.mi.co.ForgeHooks/WP]: This world was saved with mod selene version 1.18.2-1.17.3 and it is now at version 1.18.2-1.17.7, things may not work well
[18:34:57] [main/WARN] [ne.mi.co.ForgeHooks/WP]: This world was saved with mod supplementaries version 1.18.2-1.4.2 and it is now at version 1.18.2-1.4.5, things may not work well

And then it stops loading. No crash report or anything. Even if I let it sit for a while, nothing happens.

logs_latest(1).log
Same thing happens to me, Selene locks the server loading. This only happens with version 1.17.7, if on 1.17.6, this doesn't happen.

Guys I need to know if this happens with or without supplementaries/IW as those are the ones that register stuff dynamically

Guys I need to know if this happens with or without supplementaries/IW as those are the ones that register stuff dynamically

I think I tested it without Supplementaries once, and it worked fine that one time, but it also caused all of the Supplementaries things to disappear once I loaded Supplementaries back in.

Guys I need to know if this happens with or without supplementaries/IW as those are the ones that register stuff dynamically

I run both Supplementaries and Immersive Weathering. My server loads (With an old world) only when running supplementaries 1.4.4 and Selene Lib 1.17.6. Once I slap in the new version of Selene and Supplemtaries it buckles.

Could any of you that has had this issue send me a world file to test this? Seems like it might be something to do with a specific state of it since I tried downgrading, placing some blocks including signs and upgrading and it loaded up fine

Could any of you that has had this issue send me a world file to test this? Seems like it might be something to do with a specific state of it since I tried downgrading, placing some blocks including signs and upgrading and it loaded up fine

I can do that. Where would you like me to send it privately?

Guys I need to know if this happens with or without supplementaries/IW as those are the ones that register stuff dynamically

I think I tested it without Supplementaries once, and it worked fine that one time, but it also caused all of the Supplementaries things to disappear once I loaded Supplementaries back in.

Okay, I created a new world and tested it again without Supplementaries, but it still crashes. I'm not sure how to send the world-file, but I don't think it matters because my problem is not limited to a single world.

Guys I need to know if this happens with or without supplementaries/IW as those are the ones that register stuff dynamically

I think I tested it without Supplementaries once, and it worked fine that one time, but it also caused all of the Supplementaries things to disappear once I loaded Supplementaries back in.

Okay, I created a new world and tested it again without Supplementaries, but it still crashes. I'm not sure how to send the world-file, but I don't think it matters because my problem is not limited to a single world.

Even with the version I published yesterday? Crashing on a new world isnt the issue being discussed here tho and its likely just mismatched mod versions

e would you like me to send it privat

well I already got another one from another user so there's no need but thanks anyways

I would back port to 1.17.5 for now. I can't even create a single player world with 1.17.7.

nice at least that's working. I assume it was on a new world tho. For issue with existing worlds I have published a new supplementaries version that should handle the remapping correctly. Still that shouldnt change the outcome of this issue...

I'm going to go ahead and test it on our hosted server with an old world and I will also let you know how it goes. Give me about 10 minutes.

nice at least that's working. I assume it was on a new world tho.
For issue with existing worlds I have published a new supplementaries version that should handle the remapping correctly. Still that shouldnt change the outcome of this issue...

should be a world that has had one of the 1.17.0+ versions (I dont remember exactly when it was introduced but was very recent). Also thanks :D

also are the ones that are having this issue using everycompat too? What about snowy spirit? I need to figure out if it's even a supplementaries issue. I did try to load up a world with the buggy versions and the load it up with today's version and everything got remapped fine so I'm not sure

Yes, indeed, seems like your Id fix broke the id system and softlocks the server
2022-06-13-4.log

I don't know what exactly about Selene 1.17.7 crashes the servers, but it is explicitly stated to be a bug on Selene's end. Here is the crash rapport so you can take a look.

For this is just outdated dependencies. Check if both this and supplementaries are updated. Also check if you do not have duplicate mods in your mod folder

I would back port to 1.17.5 for now. I can't even create a single player world with 1.17.7.

I cant replicate this. You too check if all mods are up to date and send me a crash report

I would back port to 1.17.5 for now. I can't even create a single player world with 1.17.7.

I cant replicate this. You too check if all mods are up to date and send me a crash report

I'm not crashing, using the new version of both sup/selene, I am unable to use axes on wood type items. They are all marked "no tool" although, I'm not too sure if it's your mod BUT since the newest update for selene is to fix it, I am assuming so. It's only server side, can't recreate it client side.

Yes, indeed, seems like your Id fix broke the id system and softlocks the server 2022-06-13-4.log

I'm not sure about this one. It's a diff issue as the 2 above. The buggy version I had up for a week indeed made some blocks get regisrtered with an incorrect id and when they reverted pack those blocks were no longer getting registered. What you see there on the logs is supplementaries catching all those blocks that are no longer registered and remapping them all to their oak variant. This is intended behavior for when one uninstall a mods that adds a wood type. Of course it's less desirable here and I'll quickly push out an update so that they get remapped to their original block so no blocks are lost. Anyways I'm not seeing errors there, forge is complaining that more than one item is mapped to the same id but that is not an error and as I've said its expected behavior. Log seems to be cut off tho, could you send me another one where you do not kill it so soon?

t crashing, using the new version of both sup/selene, I am unable to use axes on wood type items. They are all marked "no tool" although, I'm not too sure if it's your m

hm I'm not touching axes or vanilla logs in the slightest. Also what does this have to do with not being able to create a single player world?

t crashing, using the new version of both sup/selene, I am unable to use axes on wood type items. They are all marked "no tool" although, I'm not too sure if it's your m

hm I'm not touching axes or vanilla logs in the slightest. Also what does this have to do with not being able to create a single player world?

It does not have anything to do with my crashing issue. I resolved it by back porting. It's all wood types not just vanilla. I just brought it up since we are already here and someone mentioned ID's. \ I planned on doing some tests before posting an actual ticket. I apologize for bringing it up here.

so any issue "resolved" by back porting isn't resolved in my book. If there are problem with the latest version then that's a bug and github here is for me to fix those. Can you send me a log file from when you tried to open a world with the newest version?

so any issue "resolved" by back porting isn't resolved in my book. If there are problem with the latest version then that's a bug and github here is for me to fix those. Can you send me a log file from when you tried to open a world with the newest version?

Just updated to the newest version of supplementaries and selene and I am no longer crashing when loading into a singleplayer world. I'm going to go ahead and load up a server and report my findings.

I don't know what exactly about Selene 1.17.7 crashes the servers, but it is explicitly stated to be a bug on Selene's end. Here is the crash rapport so you can take a look.

For this is just outdated dependencies. Check if both this and supplementaries are updated. Also check if you do not have duplicate mods in your mod folder

For me, updating both Supplementaries and Selene Library didn't fix anything. Whenever I try to enter my single player world, it gets stuck on the data loading screen, and instantly stops responding. I also don't have any duplicates in my mod folder.

Yes, indeed, seems like your Id fix broke the id system and softlocks the server 2022-06-13-4.log

I'm not sure about this one. It's a diff issue as the 2 above. The buggy version I had up for a week indeed made some blocks get regisrtered with an incorrect id and when they reverted pack those blocks were no longer getting registered. What you see there on the logs is supplementaries catching all those blocks that are no longer registered and remapping them all to their oak variant. This is intended behavior for when one uninstall a mods that adds a wood type. Of course it's less desirable here and I'll quickly push out an update so that they get remapped to their original block so no blocks are lost. Anyways I'm not seeing errors there, forge is complaining that more than one item is mapped to the same id but that is not an error and as I've said its expected behavior. Log seems to be cut off tho, could you send me another one where you do not kill it so soon?

Oh, i did not kill it, it killed itself. That's the furthest the server will go. Reverted back to 1.17.6 and everything is fine

uck on the data loading screen, and instantly stops responding

well that's another issue than the last one (which was a crash caused by outdated supp), likely the same other guys are having here. send me the log anyways so I can see at which phase it's hanging up

Yes, indeed, seems like your Id fix broke the id system and softlocks the server 2022-06-13-4.log

I'm not sure about this one. It's a diff issue as the 2 above. The buggy version I had up for a week indeed made some blocks get regisrtered with an incorrect id and when they reverted pack those blocks were no longer getting registered. What you see there on the logs is supplementaries catching all those blocks that are no longer registered and remapping them all to their oak variant. This is intended behavior for when one uninstall a mods that adds a wood type. Of course it's less desirable here and I'll quickly push out an update so that they get remapped to their original block so no blocks are lost. Anyways I'm not seeing errors there, forge is complaining that more than one item is mapped to the same id but that is not an error and as I've said its expected behavior. Log seems to be cut off tho, could you send me another one where you do not kill it so soon?

Oh, i did not kill it, it killed itself. That's the furthest the server will go. Reverted back to 1.17.6 and everything is fine

that is very weird that it did that. It usually at least gives an error message. Can you test if making a new server with the newest version & then downgrading has the same effect?

so any issue "resolved" by back porting isn't resolved in my book. If there are problem with the latest version then that's a bug and github here is for me to fix those. Can you send me a log file from when you tried to open a world with the newest version?

Server + Client working perfectly with new update :)!