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
Custom palettes on some characters are broken in the 1.12.1 indev. This example uses Klonoa as the skin with a broken palette, and Gwimbly as the character with the working palette.
Reproduction / Suspicion
Steps to reproduce the issue:
Go to 'Character Select'
Select a character with a preset palette (I.E. Klonoa)
Suspicion of root of the issue:
Some form of deprecation
Expected behavior
Character should have a custom palette
Screenshots
Gwimbly in the new indev with preset palette on.
Ditto, but with preset palette off.
Klonoa, also in the 1.12.1 indev. The palette isn't recognized here.
Klonoa in 1.9.1. Here, his palette is recognized.
Character Select Packs
CS Packs active:
[CS] Klonoa
[CS] Gwimbly
Additional context
There are more mods with non-functional palettes, including Pizza Pack and Brian Griffin (from my testing.) This whole problem could've been caused by deprecating something in the API.
The text was updated successfully, but these errors were encountered:
Describe the bug
Custom palettes on some characters are broken in the 1.12.1 indev. This example uses Klonoa as the skin with a broken palette, and Gwimbly as the character with the working palette.
Reproduction / Suspicion
Steps to reproduce the issue:
Suspicion of root of the issue:
Some form of deprecation
Expected behavior
Character should have a custom palette
Screenshots
Gwimbly in the new indev with preset palette on.
Ditto, but with preset palette off.
Klonoa, also in the 1.12.1 indev. The palette isn't recognized here.
Klonoa in 1.9.1. Here, his palette is recognized.
Character Select Packs
CS Packs active:
Additional context
There are more mods with non-functional palettes, including Pizza Pack and Brian Griffin (from my testing.) This whole problem could've been caused by deprecating something in the API.
The text was updated successfully, but these errors were encountered: