Skip to content

Container

Ferdinand Calo edited this page Feb 15, 2021 · 5 revisions
# Data Overview
DataType: CONTAINER
File Ending: .container
Has Own Item: yes
Has TMT Model: yes

Config location: ./assets/<packid>/config/containers/<here>.container
Model location: net.fexcraft.mod.addon.<packid>.models.container.<here> OR CUSTOM

Containers are an relatively Unique feature of FVTM.
While other mods may add "shipping containers" only those in FVTM
are fully functional (as of my knowledge), place-able as blocks, transportable by vehicles
available in various sizes, capable to hold wast inventories of items or fluids.
Perhaps in the future able to store FE, pallets and other.

Containers are by default 3 blocks HEIGH and 3 blocks WIDE,
the LENGTH differs from 1 to 12 blocks.

Some examples are at HCP!


Here the overview of the Fields in a container json config file:

  • RegistryName - the registryname, should be packid:container_id
  • Addon - the addon the container is in, e.g. fvtm:gep
  • Name - optional name field
  • Description - can be either a string (supports line breaks \n) or string array
  • ContainerType - can be: MICRO(1blk), TINY(2blk), SMALL(3blk), MEDIUM(6blk), LARGE(12blk)
  • Texture - optional, one NamedResourceLocation - the container's texture
  • Textures - optional array of NamedResourceLocations - the container's textures
  • Primary - optional, default primary RGB color
  • Secondary - optional, default secondary RGB color
  • KeyType - optional, specific Key (Material) registry name to be spawned, default gep:key
  • InventoryType - currently available are FLUID and ITEM
  • InventorySize - inventory stacks or fluid(mB) capacity
  • FluidType - optional, default fluid in the Container may be defunct
  • ContentFilter - optional, ContentFilter ID, current available ones are: food
  • Model - the Model, check the wiki page on how to define it

This datatype creates an own Item, as such you will need to create a ItemModel JSON and supply a texture,
this is a vanilla/forge process, as such customisation and other is not matter of FVTM.
The expected path for the model will be /assets/<packid>/models/item/<containerid>.json
The usual path for the texture is /assets/<packid>/textures/items/<containerid>.png
For more info how the JSON should look, either take a look at GEP or vanilla minecraft.


This datatype OVERRIDES (unless changed in config) the default Item Rendering, as such the
vanilla JSON model may not get displayed, but instead a 3D representation if this Container's Model will be.