Datapack Data Types

All jsons for miapi can have the field load_condition to prevent their loading. this condition is evaluated on reload on the server. see Conditions for more details

Modules

• a seperate Json found in miapi/modules
• requires a unique filenname/path for each converter file
• The API does not include any pre-built modules.
• Modules are not included within the API itself, but instead are outsourced to the addons to add.
• Modules need to be added to data/miapi/modules/anyPathOrNameFromHere.json
• Examples of modules can be found here.
• Modules require the field of name, names should be unqiue to the module and are used to identify the module
• the rest of the Json is a Map of Properties

Synergies

• a seperate JSON found in miapi/synergies
• requires a unique filenname/path for each converter file
• used to augment modules under certain conditions
• Examples of synergies can be found here.

Modular Converters

• a seperate JSON found in miapi/modular_converter
• requires a unique filenname/path for each converter file
• used to convert other items into modular Items
• Examples of Modular Converters can be found here.

Create Options

• a seperate JSON found in miapi/create_options
• requires a unique filenname/path for each converter file
• Gives create options on the Plus button in the GUI
• Examples of Create Options can be found here.

Materials

• a seperate JSON found in miapi/materials
• requires a unique filenname/path for each converter file
• The API offers a diverse range of materials.
• Materials are loosely defined JSON files that serve as references for module statistics.
• Materials need to be added to data/miapi/materials/anyPathOrNameFromHere.json
• Full list of materials can be found here.
• In addition Materials are generated at Runtime to increase Mod-Compatibility