[BUG] EV ores don't drop XP
Jeuvke opened this issue ยท 18 comments
What went wrong?
Things like redstone ore or diamond ore in other blocks don't drop any XP when mined.
Platform
Forge
Version
0.6.2
Logs and Screenshots
No response
Provide your logs, please. I don't think forge made any breaking changes on their end, but logs would help narrow down the cause.
Ah, this is on a dedicated server; that's the sort of important information you need to include. Server logs, please; possibly client logs down the road, but I doubt they're necessary here.
It's pretty big because of log spam, but here it is:
https://gist.github.com/Jeuvke/a27d43aca7f6b104fc311622c91750a3
This is the default config that comes with the bliss mod pack, I guess I'll report it there.
Oh yeah, that modpack has known issues in its EV configs. Not sure why they haven't fixed it yet as I yell at them in the log. Regardless, I'm not sure that's the cause of this issue; I'll look into it a bit more and see what I can figure out.
Can confirm that this is a bug with just EV and vanilla on forge 1.18.2. Not sure what's going on; I'll take a look at it before the final 1.18.2 release.
And it says "if we loaded this config, it would crash the game". Which I thought would imply that said config should be fixed.
Oh yeah, that modpack has known issues in its EV configs. Not sure why they haven't fixed it yet as I yell at them in the log. Regardless, I'm not sure that's the cause of this issue; I'll look into it a bit more and see what I can figure out.
Because your error message is entirely undescriptive and ends up printing in the middle of a bunch of known acceptable errors in mixins. It doesn't even specify which mod is causing it.
Regardless, the lack of XP drops is a separate issue, unrelated to the bad config in the modpack. It should be fixed in the next 1.18.2 release, once I finish tracking down the exact cause.
Logging menus often cut out data; it is best never to rely on them, and look at the raw log instead. From the fact that your logging menu cut this out, you're likely missing a ton of other information about what things are logging which messages.
I think Curseforge's launch process uses a weird custom logging config, if this was launched through that. They also make the debug.log not appear by default for some weird reason.
Ah, that would make sense. Unfortunately, there's nothing mod authors can do about that; the system most of us use to mark what thing is logging the messages is pretty standardized, and if CF is cutting out that information that seems like a major issue.