Default blockstates, block/item models and model patterns

[Alex Sim 0]

I don't know whether this has been asked before or whether this is possible or not, but it would be a nice feature for forge blocks without a blockstate to fallback to a signle-state blockstate with block/REGISTRY_NAME.json as default model, and blocks with no blockstate AND model to default to 'block/cube_all' as model and block/REGISTRY_NAME.png as texture

 

Same goes for items, with BlockItems defaulting to their correspective block's model, and normal items defaulting to 'item/generated' model with item/REGISTRY_NAME.png as texture

 

 

Also a more complicated addition would be having reusable models (EG: that provide textures as '${name}_top', '${name}_sides' and '${name}_bottom')

[LexManos 1519]

Just make your json files.

[Alex Sim 0]

10 minutes ago, LexManos said:

Just make your json files.

Having to make 3 json files for each block is only part of the problem: having 30+ files in a directory that all do the same thing gets kinda messy and unmanageable;

 

but whatever, I'll keep adding json files until this strikes you as an OK idea I guess

Edited August 15 by Alex Sim

[DaemonUmbra 358]

If you're in 1.13+, you shouldn't be doing this manually anyway. Look into the Data Generator system.

[Alex Sim 0]

15 minutes ago, DaemonUmbra said:

If you're in 1.13+, you shouldn't be doing this manually anyway. Look into the Data Generator system.

Any documentation / example source code?

[DaemonUmbra 358]

Not that I know of

[Big_Bad_E 9]

On 8/16/2019 at 1:26 PM, DaemonUmbra said:

Not that I know of

Is this a thing? What classes/methods do you use?

[DaemonUmbra 358]

Vanilla and Forge both use the system, however some generators that vanilla doesn't use need to be written (i.e. some things they already did manually ages ago so they didn't bother writing a generator)