Importing of models in non-minecraft namespaces
Posted: 09 Nov 2016, 00:10
(This might not necessarily be a bug, just an overlook during the development of CS)
A lesser-known but handy feature in resource packs is the use of custom namespaces, to organize resources based on what's using it. For instance, all Minecraft resources are in the assets/minecraft directory within the resource pack, therefore, making all resources fall into the minecraft namespace. You can, however, make your own namespace by making a folder next to assets/minecraft with your own name. This is referred to by the resource files with the namespace, followed by a colon, and then the path from there. (e.g custom:textures/blocks/cheese).
This is used the most for mod development, as all assets are stored under the mod's namespace.
However, Cubik Studio doesn't seem to handle namespaces correctly. For instance, it can't seem to find textures from other namespaces, while the game can. Cubik Studio doesn't correctly recognize model parents from non-minecraft namespaces, even if the child model the parent model are in the same namespace, and just interprets the parent as an empty model with no elements. I use this quite a bit to separate minecraft assets from my own, and I'm sure people working on mods will surely run into this problem, too.
A lesser-known but handy feature in resource packs is the use of custom namespaces, to organize resources based on what's using it. For instance, all Minecraft resources are in the assets/minecraft directory within the resource pack, therefore, making all resources fall into the minecraft namespace. You can, however, make your own namespace by making a folder next to assets/minecraft with your own name. This is referred to by the resource files with the namespace, followed by a colon, and then the path from there. (e.g custom:textures/blocks/cheese).
This is used the most for mod development, as all assets are stored under the mod's namespace.
However, Cubik Studio doesn't seem to handle namespaces correctly. For instance, it can't seem to find textures from other namespaces, while the game can. Cubik Studio doesn't correctly recognize model parents from non-minecraft namespaces, even if the child model the parent model are in the same namespace, and just interprets the parent as an empty model with no elements. I use this quite a bit to separate minecraft assets from my own, and I'm sure people working on mods will surely run into this problem, too.