Skip to content

[Bug] When installed alongside Geckolib, conflicts occur causing,the Arcane Lock spell to fail, resulting in the inability to lock chests. #900

@OoRmikooO

Description

@OoRmikooO

Is there an existing issue for this?

  • I have searched the existing issues

Observed behaviour

Forge Version: 14.23.5.2847

Mods & Versions Involved:

  • Electroblob's Wizardry: 4.3.15

  • GeckoLib 3: 3.0.30

Issue Description:

When both Geckolib 3 and Wizardry are installed, the visual effects (purple particles & glowing outline) of the Arcane Lock spell do NOT appear on containers placed after Geckolib has loaded. However, the spell's functionality (locking the container, playing sound, giving chat message) works perfectly. This issue does not occur with either mod installed alone.

This is a client-side rendering issue only and does not affect game logic.

Crucial Observation / Clue:

The effect does correctly appear on containers that existed in the world before Geckolib's render systems were fully initialized (e.g., containers placed in a world created before Geckolib was installed, or the very first container placed in a fresh world). This strongly suggests a conflict in renderer registration order, event listener priority, or a similar client-side hook that affects newly created/placed block entities.

Expected behaviour

normal rendering spell

Steps to reproduce

Steps to Reproduce (in a clean environment):

  1. Install only Electroblob's Wizardry 4.3.15 and GeckoLib 3.0.30 on Minecraft 1.12.2 with Forge 14.23.5.2847.

  2. Launch the game and create a brand new world.

  3. Place a container (e.g., a Chest).

  4. Cast the Arcane Lock spell on it.

  5. Expected Result: The container should show the persistent purple arcane lock visual effects.

  6. Actual Result: No visual effects appear on the container (though it is functionally locked).

Additional Notes:

  • Tested in a completely clean world with no other mods, ruling out data corruption or conflicts with other mods.

  • The "new vs old container" behavior points directly to a client-side rendering compatibility issue.

Crashlog

No response

Environment (Singleplayer/Server, etc.)

Singleplayer

Mod version

4.3.15

Minecraft version

1.12.2

Forge version

1.12.2 -14.23.5.2847

Other mods

Geckolib
geckolib-forge-1.12.2-3.0.31.jar

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs TriagebugAnything that isn't working how it's supposed to

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions