Bone Zone

Bone Zone

Mods
871k Downloads

[BUG] Console spam when logging into a server

katubug opened this issue ยท 1 comments

commented

Minecraft Version

1.20.1

Mod Version

3.0.3

Mod Loader

Forge

What environment are you running the mod in?

Dedicated Server

Issue Description

Hi, I keep having log spam when logging into my server. My character is wearing a Bone Zone helmet, not sure if that's relevant.

The error is along the lines of:

[16:56:12] [Server thread/ERROR] [ne.mi.fm.lo.RuntimeDistCleaner/DISTXFORM]: Attempted to load class net/minecraft/client/renderer/RenderType for invalid dist DEDICATED_SERVER
[16:56:12] [Server thread/WARN] [Radium Class Analysis/]: Radium Class Analysis Error: Class net.skeletoncrew.bonezone.block.CarcassBlock cannot be analysed, because getting declared methods crashes with RuntimeException: Attempted to load class net/minecraft/client/renderer/RenderType for invalid dist DEDICATED_SERVER. This is usually caused by modded entities declaring methods that have a return type or parameter type that is annotated with @OnlyIn(Dist.CLIENT). Loading the type is not possible, because it only exists in the CLIENT environment. The recommended fix is to annotate the method with this argument or return type with the same annotation. Lithium handles this error by assuming the class cannot be included in some optimizations.

Here are the full logs:
debug.log
latest.log

commented

Hello, unfortunately this is an issue with Radium and the message logged is not correct. Unfortunately the developers of Radium insist that this is everyone else's issue and have refused to fix this. I've heard from many players that the Canary mod does not have these issues so it that may be worth checking out instead.

To explain the issue in more depth, this mod does not load client side code on servers like Radium claims in this message. This issue is specifically caused by Radium attempting to analyze modded code in an unsafe way. They have intentionally chosen to spam you with this message rather than handling the issue appropriately. The solution they give of using '@onlyin(Dist.CLIENT)` goes against the best practices for developing Forge mods and multiple developers from the Forge team have advised against doing that.