DOCSEARCHbyAlgolia
Submit Docs

Inner Core API Documentation

website·Indexed 31 days ago

https://docs.inner-core.org/

Technical API reference for Inner Core, featuring detailed class hierarchies and interfaces for IndustrialCraft machines (such as NuclearReactor, SolarGenerator, and Macerator), UI element properties, callback functions, and recipe manipulation modules.

Tokens
409.5K
Snippets
3.2K
Records
4.2K
Agent score
52%

What's inside Inner Core

  1. Overview of Render.Transform interface

    The Render.Transform interface is used to perform geometric transformations on a specified render object. All transformation methods return a reference to the Transform instance, allowing for method chaining (sequential calls).

  2. Overview of Agriculture.CropTile

    The Agriculture.CropTile class is an interface passed to the TileEntity.registerPrototype function. It inherits from TileEntityBase and is used to manage the logic for crop-related tile entities, including growth cycles, terrain interaction, and item container management.

  3. Overview of the UpdatableScheduler module

    The UpdatableScheduler is an experimental module (introduced in version 3.1.1b127) designed to manage objects that need to update their state every tick. To prevent user interface freezes, the scheduler may limit the frequency of notifications if the number of active updatables becomes too high.

  4. Overview of the NativeTileEntity interface

    The NativeTileEntity interface provides access to native tile entities such as chests, hoppers, furnaces, and smelters. The specific type of the tile entity can be identified using the getType() method, which returns a constant from the ETileEntityType enum.

  5. Overview of Horizon Modding Kernel

    Horizon Modding Kernel is a flexible game modding launcher and mod loader for Minecraft: Bedrock Edition on Android devices. It provides a flexible API for creating stable modding environments and supports replacing game resources, adding new ones, and offers additional support for Unity and C/C++ applications. It maintains full backward compatibility with mods developed for Inner Core.

  6. Overview of ItemModel namespace

    The ItemModel namespace is used to change item models in the player's hand and/or inventory. If a block has an ICRender attribute, it is automatically applied as the item's model by default. This namespace has been available since version 2.0.2b20.

  7. Overview of available Callback interfaces

    The Callback module provides a wide array of interfaces to define the signature of callback functions for specific game events. Key event categories include:

    • Block Events: BlockChangedFunction, BreakBlockFunction, BuildBlockFunction, DestroyBlockFunction.
    • Entity Events: EntityDeathFunction, EntityHurtFunction, EntityInteractFunction, EntityFunction.
    • Player Events: PlayerAttackFunction, PlayerEatFunction, PlayerTickFunction, PlayerChangedDimensionFunction.
    • World/Dimension Events: DimensionLoadedFunction, DimensionUnloadedFunction, GenerateChunkFunction.
    • Item/Inventory Events: ItemUseFunction, ItemUsingCompleteFunction, ItemNameOverrideFunction.
    • System/UI Events: ConnectingToHostFunction, NativeGuiChangedFunction, SystemKeyEventDispatchedFunction.

  8. Overview of Inner Core event types

    Inner Core events are triggered by game actions or mods and are processed by both the server (world host) and clients. Events are categorized by their trigger source:

    • Construction and Destruction: Used for blocks and tiles to manage drops, tool durability, skill development, and block updates.
    • World Interactions: Covers item usage and interactions with blocks, tiles, and entities (e.g., fishing, eating, throwing snowballs, opening containers, projectile hits).
    • Entity and Player: Covers entity lifecycle and state changes, including spawning, taking damage, picking up items, player experience changes, despawning, and death.
    • Dimensions and World: Covers environmental events such as dimension travel, explosions, redstone usage, chunk generation, and dispenser drops.
    • Interface: Covers UI actions like opening/closing windows, container interaction, slot movement/selection, crafting, and item icon changes.
    • Server and Internal: Covers system-level events such as player joins, save file I/O, keystrokes, world selection, commands, loading, and server/player ticks.
    • Custom: Includes user-implemented events or integration events from other mods and libraries.

  9. Overview of BlockState

    A BlockState is a set of parameters used to store data permanently for blocks in the world. States can be requested by obtaining a block via BlockSource.getBlock and then using BlockState.hasState or BlockState.getState. They are used by the game engine, manually by developers, and within ICRender.BlockState conditions.

    Important Caveat: Do not use numeric identifiers for saving data inside containers; convert them to named identifiers first, as numeric IDs may change each time the world is entered.

  10. Overview of the Recipes module

    The Recipes module is used to create, manage, and manipulate crafting recipes for vanilla and custom workbenches. It supports shaped recipes (where item placement matters), shapeless recipes (where only ingredients matter), and furnace-specific recipes and fuels.

  11. Overview of the TagRegistry system

    The TagRegistry system allows developers to assign tags to objects and organize them into groups. This is primarily used for object searching and filtering. Tags can be added as primary tags, serialized via an object's _tags property, or dynamically generated using a Tag Factory.

  12. Overview of UI.WindowGroup

    The UI.WindowGroup class represents a group of several windows opened at the same time. It implements the IWindow interface. Common subclasses include UI.AdaptiveWindow and UI.StandardWindow.