Skip to content

[Bug] ProbeJS Legacy crashes in Forge 1.20.1 userdev because texture Accessor mixins use remapped field names without a refmap #6

@P-nutsK

Description

@P-nutsK

Environment

  • Minecraft: 1.20.1
  • Forge: 47.4.0
  • ProbeJS Legacy: curse maven probejs-legacy-956446:7615033
  • KubeJS: 2001.6.4-build.120
  • Java: 17
  • Environment: Forge userdev / named development runtime

What happens

The client crashes during mixin application:

text Mixin apply failed probejs_legacy.mixins.json:AccessTextureAtlas -> net.minecraft.client.renderer.texture.TextureAtlas InvalidAccessorException: No candidates were found matching f_118264_:Ljava/util/Map;

A similar failure also occurs for:

text probejs_legacy.mixins.json:AccessTextureManager f_118468_

Cause

probejs_legacy.mixins.json does not define a refmap, and no refmap file appears to be included in the published jar.

Because of this, accessor targets cannot be remapped correctly in Forge 1.20.1 named/userdev environments, causing mixin application to fail during startup.

Expected behavior

ProbeJS Legacy should boot correctly in Forge 1.20.1 userdev/named development environments.

Actual behavior

Mixin application fails because the accessor targets cannot be remapped in the development runtime.

Local workaround

Replacing the accessor targets with named field names allows the client to pass the crash point:

java @Accessor("texturesByName") Map<ResourceLocation, TextureAtlasSprite> getTexturesByName(); @Accessor("byPath") Map<ResourceLocation, AbstractTexture> getByPath();

Possible fix

Please check the published mixin/refmap configuration.

It appears the released artifact is missing the refmap needed for accessor remapping in named development environments.

This likely does not affect normal production/obfuscated launches, but it breaks Forge userdev environments that load ProbeJS Legacy at runtime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions