Dragon Mounts: Legacy

Dragon Mounts: Legacy

20M Downloads

[Datapack Problem] Custom Breed Egg is Missing Model/Texture

Peekofwar opened this issue · 3 comments

commented

I made a datapack that successfully implements a custom dragon breed with a custom texture, however the egg block is missing its model and textures... I don't understand why. I made a copy of the Aether texture and replaced aether in the filenames to skye.

I would also like to know how to change the creative-spawn egg colors.

2022-09-23_20 56 14

│   pack.mcmeta
│
└───data
    └───dragonmounts
        ├───dragonmounts
        │   └───dragon_breeds
        │           skye.json
        │
        └───loot_modifiers
            └───dragonmounts
                └───skye
                    └───chests
                            simple_dungeon.json
│   pack.mcmeta
│   pack.png
│
└───assets
    └───dragonmounts
        ├───lang
        │       en_us.json
        │
        ├───models
        │   └───dragon_eggs
        │           skye_dragon_egg.json
        │
        └───textures
            ├───block
            │       skye_dragon_egg.png
            │       skye_dragon_egg.png.mcmeta
            │
            └───entity
                └───dragon
                    └───skye
                            body.png
                            glow.png
                            saddle.png

skye_dragon_egg.json

{
  "parent": "minecraft:block/dragon_egg",
  "textures": {
    "particle": "dragonmounts:block/skye_dragon_egg",
    "all": "dragonmounts:block/skye_dragon_egg"
  }
}

dragonmounts_skyethedragon_pack.zip

commented

Yeah just tested this… and everything seems to be in order in your end. I suspect theres a problem with resources not being seen on the forge end. Mustve broke in a later version. Will look into it. Thank you for reporting 👍

commented

Possible issue: The event used to register the block models uses an the ModelRegistryEvent, which is a mod bus event. It's possible that we are only registering models under the dragon mounts resource name rather than ALL resource pack names.

Honestly, I was never a fan of this solution anyway, so I'll be looking into something different.

commented

After further investigation, it seems that this issue has been resolved on forge's end.
It turns out that non-mod resource packs were not being included in the resource managers and therefore Dragon Mounts was not finding custom dragon egg models to add to the rendering cache.

That being said, the solution here is to update your forge version for the respected game version. Both 1.18.2 and 1.19.2 have had releases containing the fix.