[BUG] Newest update today made problem worse

Question

[BUG] Newest update today made problem worse

itsdinkd opened this issue 3 years ago · 10 comments

itsdinkd commented 3 years ago

So I turned on the server and immediately got spammed... a lot.... of this https://pastebin.com/bBGHYdDS

I never received this message in console 2 updates ago.. weird.

DaFuqs · Answer 1 · 2021-11-07T19:45:37.000Z

Can you upload your pack as a multimc instance or something similar? That would help a ton.

itsdinkd · Answer 2 · 2021-11-07T20:43:38.000Z

https://pastebin.com/3EWUH4XM Here is the logs from my 2nd server. This latest update, and the last, effectively killed chest loot tables and stopped chests from generating into the world in new chunks. Look at all that spam generated in 2 seconds.

My modpack can be found at https://www.curseforge.com/minecraft/modpacks/another-quality-modpack-2

DaFuqs · Answer 3 · 2021-11-07T21:32:48.000Z

I will look into it tomorrow. In the meantime using the old version will work fine. red2blue ***@***.***> schrieb am So., 7. Nov. 2021, 21:43:

…

https://pastebin.com/3EWUH4XM Here is the logs from my 2nd server. This latest update, and the last, effectively killed chest loot tables and stopped chests from generating into the world in new chunks. My modpack can be found at https://www.curseforge.com/minecraft/modpacks/another-quality-modpack-2 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJUQSWMO4LYAS52BNAD4SDUK3QIJANCNFSM5HRB7EOA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

itsdinkd · Answer 4 · 2021-11-08T16:36:32.000Z

which version is the working old version? prior to 2.0?

DaFuqs · Answer 5 · 2021-11-08T18:06:25.000Z

The one you only had occasional issues with was 2.1.0.

I tried and tried, but could not recreate the error messages from the log you were posting. Can you send a complete startup log? The only way I can imagine the errors triggering is with Loot Crate Block Entities to register at all. If yes, there could be a stacktrace there.

I tried with:
Client: AQM2 [v2.9.5a] Hotfix (newest one on curseforge)
Server: AQM2-2.9.5a.zip (the newest one linked on the discord)
changing the version of LootCrates to 2.2.0
and then flying, teleporting and walking all around the place. Crates seemed to generate normally, NBT data fully intact and functional. Are you using a newer, dev vesion of the pack?

itsdinkd · Answer 6 · 2021-11-08T19:55:11.000Z

I deleted the mod because it was giving insane lag with those messages ^. now I'm getting spammed [WARN] (class_2586) Skipping BlockEntity with id lootcrates:chest_loot_crate_block_entity

Nope, I'm using the version you downloaded. Are you running a dedicated server or just going into single player?

Maybe try running it with 2.1.2, generating chunks, structures, etc, then upgrade to 2.2.0

DaFuqs · Answer 7 · 2021-11-08T20:13:44.000Z

Those warning messages are the vanilla way to tell you there was stuff in a saved chunk that it dis not recognize anymore (deleted a mod, or by downgrading a 1.17 world to 1.16). There is nothing to worry about, since you know what the cause of the message is. Once every chunk where loot crates did exist before are loaded once no new messages of that type will appear (since the obsolete data has all been removed) I was using the client pack via multi mc and joined onto the dedicated server, with a few restarts to make sure. I will try your suggestion. Definitely worth a try! red2blue ***@***.***> schrieb am Mo., 8. Nov. 2021, 20:55:

…

I deleted the mod because it was giving insane lag with those messages ^. now I'm getting spammed [WARN] (class_2586) Skipping BlockEntity with id lootcrates:chest_loot_crate_block_entity Nope, I'm using the version you downloaded. every people gave me their logs and it happened to them as well. Are you running a dedicated server or just going into single player? Maybe try running it with 2.1.2, generating chunks, structures, etc, then upgrade to 2.2.0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGJUQSVVUXE7GR3FTFHXGKTULATKTANCNFSM5HRB7EOA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

itsdinkd · Answer 8 · 2021-11-09T00:47:59.000Z

gotcha. yeah I recommend running it on a server. it doesn't do it in single player.

…

On Mon, Nov 8, 2021, 12:13 PM DaFuqs ***@***.***> wrote: Those warning messages are the vanilla way to tell you there was stuff in a saved chunk that it dis not recognize anymore (deleted a mod, or by downgrading a 1.17 world to 1.16). There is nothing to worry about, since you know what the cause of the message is. Once every chunk where loot crates did exist before are loaded once no new messages of that type will appear (since the obsolete data has all been removed) I was using the client pack via multi mc and joined onto the dedicated server, with a few restarts to make sure. I will try your suggestion. Definitely worth a try! red2blue ***@***.***> schrieb am Mo., 8. Nov. 2021, 20:55: > I deleted the mod because it was giving insane lag with those messages ^. > now I'm getting spammed [WARN] (class_2586) Skipping BlockEntity with id > lootcrates:chest_loot_crate_block_entity > > Nope, I'm using the version you downloaded. every people gave me their > logs and it happened to them as well. Are you running a dedicated server or > just going into single player? > > Maybe try running it with 2.1.2, generating chunks, structures, etc, then > upgrade to 2.2.0 > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#25 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AGJUQSVVUXE7GR3FTFHXGKTULATKTANCNFSM5HRB7EOA > > . > Triage notifications on the go with GitHub Mobile for iOS > < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > > or Android > < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub >. > > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIL5CKCNZCCDMD7GGZDBQDLULAVQFANCNFSM5HRB7EOA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

DaFuqs · Answer 9 · 2021-11-09T17:31:11.000Z

I tried a world upgrade with LootCrates 1.5.0 (the last 1.x version), and 2.0.1 both on dedicated server. Both had no issues, sadly.

The last thing, that I could imagine, is the config. That definitely would be a thing happening at startup. Could you please try deleting the config files
LootCrates.json5
LootCratesWorldgenSettings.json5

and check if the issue persists?

itsdinkd · Answer 10 · 2021-11-09T20:36:16.000Z

I can try it but I'm concerned about this vanilla message getting spammed. it's been three days now and both servers are constantly getting spammed with it in console. there isn't a time we're there aren't people playing on the servers. it should be done by now. I guarantee the same.message is happening for the same chests, especially at the rate it's firing these messages in console.

…

On Tue, Nov 9, 2021, 9:31 AM DaFuqs ***@***.***> wrote: I tried a world upgrade with LootCrates 1.5.0 (the last 1.x version), and 2.0.1 both on dedicated server. Both had no issues, sadly. The last thing, that I could imagine, is the config. That definitely would be a thing happening at startup. Could you please try deleting the config files LootCrates.json5 LootCratesWorldgenSettings.json5 and check if the issue persists? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIL5CKC5DBH5OEXJ7OEXCP3ULFLGVANCNFSM5HRB7EOA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

Share to