The way ExtenderDragon v1 worked was by essentially categorising block textures and their stats into separate sprites, which it would then compile into one big sprite for storage and easier programming.
But there's an intermediate step that I could absolutely get around.
What if ExtD loaded from the Minecraft .jar itself? Finds all the atlases, relevant textures and generated the blocks it needs.
Obviously this'd still be done on my end - I don't expect users to do this - but that'd be so cool.
It goes without saying that I'd have to write exceptions and probably still whitelist blocks but it saves a lot of time from manually importing textures and writing block data.
0 comments