-
Notifications
You must be signed in to change notification settings - Fork 420
Model Definition Files
The model definition file for a mod provides the physical shape of custom blocks, when those physical shapes are something other than a simple solid cube. Consequently, if the custom blocks for a mod only consist of simple solid cubes, a model definition file may not be needed for the mod.
In all cases, the models defined in the model definition file provide a set of surfaces, or patches, that textures defined in the Texture Definition Files are rendered upon. Since the textures are defined separately from the models, models for blocks with common shapes can easily be reused (e.g. the model for a stair block can be the same for any type of stair block, as the differences in how these stairs are rendered are only which textures are applied to the model for each different block).
There are a variety of methods for defining models, ranging from very simple to quite complex (up to and including custom rendering code provided by add-on Java classes). As always, the simpler methods also tend to be the more efficient.
In general, the 'modname:', 'version:', 'cfgfile:', 'var:' and other module configuration related lines should be consistent between the Model Definition File and its corresponding Texture Definition File. See Common Features for Texture and Model Definition Files for details on these commonly defined lines. Inconsistencies here can lead to problems with rendering (due to textures being applied without a corresponding model) or loading errors (due to models being used without required textures being supplied).
- To define a simple cuboid model - a rectangular prism where one or more of the dimensions is less than the size of a full block - see Defining Cuboid Models.
- To use existing custom model renderer - stairs, fences/walls, glass panes/iron fences - see Using Custom Block Renderers.
- To define a volumetric model - a shape represented as a 3D grid of smaller cubes - see Defining Volumetric Models.
- To define patch based models - a collection of arbitrary surfaces to have textures applied - see Defining Patch Models.
- To create new custom model renderer classes - see Coding Custom Block Renderers.
- Base Plugin Settings
- Web Setup
- Storage Setup
- HD Map Configuration
- World and template settings
- Guides
- Advanced Map Configuration
- Component Configuration
- Configuration of worlds
- Exporting World Data in Wavefront OBJ Format
- External Webserver Advanced
- Support for Minecraft Servers other than CraftBukkit
- Support for MinecraftForge based mods
- Support for Tekkit
- Custom Block Definitions
- Model Definition Files
- Texture Definition Files
- Defining a Block using a Custom Block Renderer
- Defining a Block using a Volumetric Model
- Defining a Cuboid Block
- Defining a Simple Block
- Defining Cuboid Models
- Defining Volumetric Models
- Special texture file types
- Using custom block renderers
- Incompatible mods