Introduction to Integration

There are a number of ways to interact with EtiMod externally to enhance the communication and behavior between EtiMod and your mod. This page outlines all possible methods of doing so, and serves as a navigation portal for the applicable pages.

IMC (Inter-Mod Communication)
IMC is performed far in the Forge late loading phase (after all mods have fully initialized), and allows mods to send data to each other. This can be used for any last minute registry of custom information.

In EtiMod, IMC can be used for the following purposes:
 * Requesting spirits use a certain sound type when walking or falling onto or within a block you created.

The following pages outline content related to IMC:
 * IMC Methods
 * IMCRegistryError

Realtime Data
Some methods provided by IMC will supply instances of Consumers or Functions that can be used to interface with EtiMod without needing to explicitly install an API to your development environment - an addition that I am sure is welcome in many modders' books. These API providing methods in IMC tend to start with the word "request", and can be found on IMC Methods. The intent of these methods is to provide the caller with a Consumer or Function that can be cached independently and be used to interface with EtiMod at any time past IMC propagation.

Data Types
There are a number of values EtiMod will use, most of these are internal but some are used by you as a developer. For your convenience, these will not require an API or a dependency on EtiMod to use, as they are serializable and deserializable to and from strings.

The following pages outline the information you may need to use:
 * Block to Material Bindings
 * SpiritMaterial Enum