-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make textures clearly belong to blocks #37
Comments
Would it be useful to have blocks 'owning' their textures via having the textures split into separate files? I'm not sure what difficulties that could bring into the rendering setup logic, but I know minecraft uses separate files for each texture and allows blocks and items to 'inherit' the textures and models of other blocks/items. I'm not suggesting we take the same organizational route minecraft has taken (in fact, I'd argue vehemently against it), but splitting textures into separate files seems like a win for modularity. |
True. |
This may be useful:
|
Enhancement for #2
Right now, there are like 3 different places where we import/define textures.
It will involve some digging into pyglet, but we definitely need to de-duplicate that.
I'm imagining a "texture" object, that has textures for more then one block.
Blocks return coordinates and a reference to their texture in it.
I think heightmaps could lead to some very interesting effects, and in the future we might want to support dynamic textures (maps) or layered textures (signs).
But we don't need a perfect solution off the bat. Just a quick system for defining a texture in one place, and having the renderer read them.
The text was updated successfully, but these errors were encountered: