Hello,

 

In 1.7.10 I used an

ISBRH

to render the vanilla stone block, then rendering an overlay on the stone texture and dynamically color the overlay based on the block's metadata. Now I am wondering if it is possible to do something like that using the new model system in 1.8, or do I have to make all the textures by hand for each possible state?

 

- larsgerrits

Like a multipass render with color passed only in the second pass?

Look at the vanilla

grass

model, it overlays a texture on each side that's coloured from

BlockGrass#colorMultiplier

. The important part is the

tintindex

value for each quad, which tells Minecraft to colour it (this is passed as the

renderPass

argument).

Wow, I totally forgot about the grass block...

 

Also, right now there is this in the log:

[17:16:21] [Client thread/ERROR] [FML]: Model definition for location minetech:ores#metal=nickel not found
[17:16:21] [Client thread/ERROR] [FML]: Model definition for location minetech:ores#metal=lead not found
[17:16:21] [Client thread/ERROR] [FML]: Model definition for location minetech:ores#metal=tin not found
[17:16:21] [Client thread/ERROR] [FML]: Model definition for location minetech:ores#metal=copper not found
[17:16:21] [Client thread/ERROR] [FML]: Model definition for location minetech:ores#inventory not found
[17:16:21] [Client thread/ERROR] [FML]: Model definition for location minetech:ores#metal=aluminium not found

I want every block to use the same texture, but only change it's color using the

colorMultiplier

method. So I looked around, and I think I have to use 'state mappers' to point every

IBlockState

to the same model instead of it looking for all different models in the blockstate file. Am I right in that? If so, how do I use those 'state mappers'?

If you want every variant to use the same model with a different colour multiplier, you can either use Forge's blockstates format and specify the model in the

defaults

section or register a state mapper (which maps each

IBlockState

to a blockstates file and variant specified by a

ModelResourceLocation

).

 

To create a state mapper that ignores a specific property, create an instance of

StateMap.Builder

, call

StateMap.Builder#ignore

with the property and then call

StateMap.Builder#build

to create the

StateMap

. To register a state mapper, call

ModelLoader#setCustomStateMapper

in preInit.

 

I have various examples of Forge's blockstates format here.

 

I have some examples of state mappers that ignore properties here.

Thanks, it all works now!