ZenRowe

I'll make sure it gets eyes on it.

This should be fixed in a patch soon (If it hasn't already gone out), but if the chibi was just sitting in your inventory when you logged off or restarted the game, when you come back it might look like 0 exp. re-equip the chibi and it should update, if the patch hasn't gone out though it's not just a visual glitch, don't try to earn alpha exp on an equipped chibi showing 0 xp if it should have more, re-equip it first. If the fix has already gone out, then it should just be a visual glitch that will only affect unequipped chibis.

To that point Cedric would love to be able to do what I did here, but often when something goes wrong on that scale, the engineers are being scrambled to figure out the problem and then immediately hop on fixing it. There isn't always someone to give the information in full to Cedric so that he can give a more detailed update. The chain of communication just isn't always established that fast. In some cases, we just flat out can't talk about a particular issue until after it's fixed because people will take advantage of and abuse it (If that is already happening in a particular situation, we w

I think I understand where your confusion is coming from.
The change we made was fixing a bug in how mod data is merged in when you launch a game. it was resulting in that, for every single mod installed, the core color definitions were being duplicated. That duplication now no longer happens. ASB is doing assumed correction, and since you weren't using any mods that added new colors it's actually easy to figure out what the right color is in your case. It is mathematically consistent.
This bug was actually how people could breed for mutations of the dye colors (That's a whole other topic

I do understand that this inconvenienced a lot of people. I really do. That's why I have been spending my own free time trying to help people understand what happened (even at risk of getting in trouble for oversharing information) and to work on something to prevent it in the future and to try and possibly help find ways to make this less awful for those that were affected by it... all when I would normally be resting.
The change went through testing, but the test conditions that were necessary to have exposed this are not normal for any studio that I have ever interacted with.
Trying to

@IanHighlander @CyberAngel67
It is definitely an impressive tool.
But do you see the color indices there on the right?
Notice how they are all at 56 or less?
There are 56 color definitions in the core game currently. (And then the dye indices which are all 200+)
Inside of the tool itself they are all predefined to what color they represent. The amount of data that had to be sorted out and manually entered for this tool is insane.
The only thing the tool is loading from the creature data is that byte value itself:
This is the data I just copied from the tool itself (Dictionaries i

Just to double check before I opened my mouth, I downloaded that source, and while I haven't spent a ton of time looking through it I would say it's doing things in a similar manner to the mod I just linked. Except that in this tool, color indices and matching color definitions have been manually entered into dictionaries (and by the looks of it there are collections of value data for at least some mods that it can download from somewhere? I have never used this tool before, but I am assuming that is how it could be determining any offsets that would otherwise mismatch the index numbers).
He

Here is an option that should work pretty well for anyone that knows that none of the mods they had installed added any custom colors. https://steamcommunity.com/sharedfiles/filedetails/?id=1940481639
This mod will try to correct all of your dino colors. It works by making assumptions about what the color definitions array looked like for you before the update that caused this, so It's not suitable for us to do in the core game... but as an option, this should actually work pretty well for many.

The current plan is that we'll be adding an admin command that can be used to reapply the correct colors on tamed dinos (So that in the future any changes to the color definitions array either by us or by mods will be effectively non-destructive).
In addition, because we can't recover the colors lost from this occurrence (the only factual memory of what those colors were is in your head), those colors that were lost will get re-rolled for new mutation colors.
I don't have an ETA on when that will be available, but it's in the works already.

You only need to increase the max levels on your servers by 5 if you are overriding the exp ramp.
Basically if you have overridden the levels for custom experience ramps and levels the inclusion of the chibis push your max level down by 5.
Ascension, chibis, any max level modifers... they all take up the last set of levels, so if we add some mechanic that is meant to handle a higher max level and you don't have the new max levels in your exp ramp... this is what happens

Don't worry it doesn't break the feature of breeding color mutations itself, the problem is just that the array of colors went through a change that got things a little messed up.
We didn't remove any of the available colors, we just removed a ton of duplication that was occurring and making all these color reference inconsistent.

It's any mods. what was happening was that every single mod added was duplicating the color definitions in the array. so there were multiple instances of every color.
When breeding and the game chooses random color mutation it randomly pick

Yes, though you should be aware that making any changes to your active mods can still potentially cause this kind of issue for the time being.

After some investigation, I understand the cause of this...

Unfortunately, any colors lost from this update can't be automatically recovered ? .Dino colors, after their randomized selection, are saved to the creature and referenced by an index number only that is associated with a master array of colors. (No we can't change this unless you want your servers to slow to a crawl, string comparisons are resource expensive)

Unofficial servers (and singleplayer) that run mods are vulnerable to this issue and have always been, any change to the order of mods or anything that alt