@ParametersAreNonnullByDefault
See: Description
| Interface | Description |
|---|---|
| ClientExtInitializer | |
| ExtInitializer | |
| FontRendererAPI |
API entry point for access to the tiny font renderer used on execution
modules, for example.
|
| InfraredAPI |
API entry point for spawning
InfraredPackets and related tasks. |
| ManualClientAPI |
This API allows interfacing with the in-game manual of TIS-3D.
|
| ManualCommonAPI |
This API allows interfacing with the in-game manual of TIS-3D.
|
| ModuleAPI |
API entry point for registering
ModuleProviders and other
module related tasks. |
| SerialAPI |
API entry point for registering
SerialInterfaceProviders and other
module related tasks. |
| Class | Description |
|---|---|
| BundledRedstoneAPI |
API entry point for TIS-3D specific bundled redstone events.
|
| ClientAPI | |
| CommonAPI |
| Enum | Description |
|---|---|
| FontRendererAPI.Font |
Font type; small font is found on eg.
|
Anyway. This is the place to go if you'd like to register custom modules for
TIS-3D, extending its functionality. To do so, implement a module using the
Module interface, as well as a provider
using the ModuleProvider interface, then
register the provider with TIS-3D via ModuleAPI.addProvider(li.cil.tis3d.api.module.ModuleProvider).
The provider will then be queried by TIS-3D when an item is used on a casing, and if it works the module created by the provider will be used. See the module's interface and the provider's interface to see how you can interact with the casing and other modules.