[1.12.1] Question about how the UniversalBucket models and textures work

[jabelar]

I was looking at the assets for Forge for the universal bucket and i'm a bit confused. If I follow the constructor for UniversalBucket I see it is called during the item registry event where it is given the registry name "bucketfilled". However, in the assets I can't find anything by that name. There is an model called bucket.json which contains:

{
    "parent": "item/generated",
    "textures": {
        "layer0": "forge:items/bucket_base"
    }
}

and there are three textures called bucket_base.png, bucket_cover.png, and bucket_fluid.png. But I don't see how the model above enables those other parts (i.e. making it look filled).

 

Also there is a blockstate json called dynbucket.json that contains:

{
  "forge_marker": 1,
  "variants": {
    "inventory": {
      "model": "forge:forgebucket",
      "textures": {
        "base": "forge:items/bucket_base",
        "fluid": "forge:items/bucket_fluid",
        "cover": "forge:items/bucket_cover"
      },
      "transform": "forge:default-item",
      "custom": {
        "fluid": "water",
        "flipGas": true
      }
    }
  }
}

but the weird thing about that is that it references a model called forge:forgebucket which doesn't exist (at least in these asset paths).

 

So what's going on -- none of these really match up. Is there some other asset directory for Forge? Or is UniversalBucket getting it's models and textures in another way?

[Draco18s]

forge:forgebucket would be a internally constructed code-model. It won't exist in the assets at all (fluid block models are done the same way).

[jabelar]

Nevermind, I see it has a custom model loader. I guess I missed it when I was looking through before...