[1.12] Recolour Item Texture at Startup

[Ommina]

OK.  I have a greyscale texture, and an RGB value.  At startup, I would like to create an item with the texture recoloured with the RGB value.  It is a pretty simple item otherwise.  Not armor, not a tool, no durability.

 

Right now I'm using IItemColor, and it's working just fine.  BUT, I'm feeling a lot of guilt over using it, as it is called every frame, and the colour really is fixed at startup.  It is not dynamic based on conditions (biome, phase of the moon, whatever).  If it is blue now, it's going to be blue later too.  As such, I'd really like to colour the item once, at startup, and be done with it, all without feeling like I am contributing to a drop in framerate -- however slight -- unnecessarily.

 

The closest I've found to achieve this is the forge dynamic bucket, but that seems to be well more than what I'm looking for.  Maybe I'm mistaken here.

 

I COULD just recolour it manually in an image editor and get on with my day, but I'd very much like to be able to tweak the RGB values without manually recolouring the textures each time I do so.

 

Any suggestions?  Is there a simpler example than the forge bucket that I can use to light my way?  Thanks.

[jabelar]

I don't think you need to feel guilty about the performance impact. With a modern computer, the GPU is capable of probably billions of such calculations. I assume that your item will be reasonably rare (a lot of the time probably not even rendering the item at all), and remember that only the items being rendered (i.e. in field of view) would even have an impact. So at most you're probably going to have a couple itemstacks in an inventory (and when viewing inventory frame rate isn't really as much of an issue even if performance dips), or maybe a couple items thrown on the ground. 

 

With modern programming (assuming you're using a full computer and not some resource-strapped embedded processor) it is best to use the proper logic and only deal with perf issues when they actually are an issue. I.e. profile the code and see if there is an actual problem. Of course you should not do stupid things like big loops, recursion, and such unless necessary. But otherwise you should just code for clean, well-structured code that uses the intended interfaces. Bug-free, maintainable code is the first priority.

[Animefan8888]

1 hour ago, Ommina said:

Any suggestions?  Is there a simpler example than the forge bucket that I can use to light my way?  Thanks.

No, there is not a simpler way to do this, though your overall code will look much simpler than forges dynamic bucket because you will only need to have one TextureAtlasSprite that applies the color to the texture. But I do agree with jabelar, it would be fine to just let the texture be generated every frame. And if it were to become a problem you could very easily switch over to the TextureAtlasSprite method.

[Draco18s]

Its likely just a vertex color operation that changes the color. Vertex color is super cheap. It's used for particle systems with hundreds of thousands of particles and it runs just fine, one or a dozen items, easy peasy.