Given the Pokemon definitions below, see that a defined Pokemon with no evolutions defined works fine (even without its preevolutions defined). See also that a Pokemon defined as evolving into a Pixelmon implemented Pokemon works fine (eg. Wigglytuff). See, finally, that replacing that same Pokemon with a Pokemon defined elsewhere causes a server crash (eg. Patamon).

This issue was introduced in 9.2.3, as 9.2.2 did not have it and the datapack functioned on server start up.

Note: I manually modified this file to reduce the size. If there are minor syntax problems, it is likely due to this fact. This error is NOT caused by syntax, which I have validated through a JSON validator.

Valid:


Valid:


Causes Server Crash:


The available crash log:

I've significantly trimmed down my test cases, and I'm still encountering the issue. The server can start normally if all added Pokemon have



but adding any evolution dependency of these Pokemon causes the crash.

Hi there, I can't seem to reproduce this on 9.2.4.
Can you double check on that version?
(Important to note evolving Pokemon is broken on 9.2.4 but I can start the server/world fine and use the custom species as normal)

I am receiving the same crash on 9.2.4. I can provide some test files, if necessary.

I think there is more to it than simply Fakemon having evolutions - perhaps something with how Pixelmon processes malformed Pokemon has changed, which instead of failing silently fails with a crash.

I say this because it functions if I do the following:
- Copy an existing Pokemon, such as Bulbasaur, twice.
- Rename, new dex#, new gen# for each of them
- Remove evolutions entirely for one
- Change the evolution for the other to the first

I am running into the issue with completely custom Pokemon (ie. those that were not copied and modified, but are proper JSON). These Pokemon were able to be loaded in 9.2.2 and 9.1.7, but cause a crash on 9.2.3 and 9.2.4. If you want to reproduce, the Digimon Datapack https://www.curseforge.com/minecraft/texture-packs/pixelmon-digimon-datapack

Whoops, left my message hanging. The Digimon datapack is an example of this. It loaded in previous versions and crashes now. It is quite large, but even cutting it down to a couple files can make it happen. I've been working on validation of this pack and have made various fixes (such as capitalization or typos of the To Pokemon in evolutions, removing non-existent moves, etc.) but have yet to get a version that functions on the latest versions.

Alright, here is a test that should reproduce it for you.

Poomon - basically an empty Fakemon that Newmon evolves into.


Working Newmon - it has an evolution to Poomon, but no conditions.


Broken Newmon - it has an evolution to Poomon with a condition and crashes on startup


The added condition for the broken Newmon should match up with Eevee's evolution into Leafeon (but the number is different).

Hi there, apologies for the delay. I'm going to take over with this issue

I was able to reproduce the issue described here - an evolution into a custom pokemon (which was defined in the same datapack) causes datapack validation to fail. In my own testing (which was done in a singleplayer, 9.2.5 environment), I found that even without a condition, the evolution to a custom species that isn't already loaded caused the datapack to fail validation.

I also noted that the datapack appeared to be getting cached once succesfully loaded for the first time. As a result I could load the evolved pokemon first in a completely seperate datapack, and then load the pre-evolution without issues (even if the evolved form was later removed).

Could you confirm if this is consistent with the behaviour experienced on your end?

Either way, I'll pass the information I've gathered so far to internal - thanks!