You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Crash when any block using Colormatic style tint is present in chunk range
To Reproduce
Steps to reproduce the behavior:
open or start world
HaVE cONTINUITY V3.0.0beta4 loaded and active
chunk load finds a Patrix texture using tint for colour
Game Crashes
Expected behavior
Block should load with tint colour information as it does without Continuity loaded.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Win 11
Minecraft Version 1.20.1, & 1.20.2
Mod Version 0.1.675
Additional context
minimal mods loaded, colour loads fine without Continuity connected textures turned on.
also tried with older versions of loader and Indium, but you've tied it in to must be latest versions, cannot test with older version of Indium or older fabric loader/api etc.
Any progress on a fix for this? Patrix no longer needs Colormatic or Vanadium starting with 1.20.4, but my modpack crashes during game boot on that version, so I plan to stick to 1.20.1 until the next major MC release.
Describe the bug
Crash when any block using Colormatic style tint is present in chunk range
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Block should load with tint colour information as it does without Continuity loaded.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
minimal mods loaded, colour loads fine without Continuity connected textures turned on.
also tried with older versions of loader and Indium, but you've tied it in to must be latest versions, cannot test with older version of Indium or older fabric loader/api etc.
hopefully logs might help
latest.log
crash-2023-10-15_22.34.20-client.txt
The text was updated successfully, but these errors were encountered: