Start your Journey

📄️ Introduction

On the main page of the documentation for the Inner Core engine, which extends the basic functionality of Minecraft on Android devices. The goal of this site is to teach the possibilities in creating changes for the gameplay — modifications, bring your own idea to the game and simply learn something new.

📄️ Methodology

Any project somehow has a summary of basic terms, in which any of us must swim freely, not forgetting the basic concepts. It is important to remember that Minecraft is a game that encourages creativity and freedom of action, so there are no strict rules or limitations in the methodology. However, general steps and approaches can be described that can be used when playing or creating mods for it.

📄️ Installing Pack

Before creating or just installing modifications, we need to prepare the tools for modifying the game. Why can't I modify the game directly? By default, Minecraft has closed source code and does not provide for changing the gameplay, except perhaps behavior packs.

📄️ Supporting IDEs

The environment simplifies project development by providing auto-completion, error checking, low-level language compilation, and a whole bunch of features. Writing code in an IDE is much more convenient than using Notepad, although the choice is yours.

📄️ Going Forward

After the necessary tools or environments are installed, you can proceed directly to learning languages and creating a project. Regardless of the chosen programming language and project idea, it is important to maintain interest and motivation, as programming can be a complex and lengthy process.

📄️ Mod Structure

Before using one of the template creation options, it is probably no less important to familiarize yourself with their contents. First of all, a mod is a folder with a build.config configuration file, which describes the entire process of loading, assembling and building your mod. Let's look at the contents of the entire folder, and first analyze other, but no less important aspects.

📄️ Mod Lifecycle

It usually begins before the game starts; at this moment, the mod announces its existence to the launcher and performs a list of procedures necessary for the user. Now we will look at the full cycle from this moment to the closing of the game, what happens in the mod during various events, and how it can affect the gameplay.

📄️ Script Building

In addition to the ability to directly specify an executable script, there is often a need to split the source code into files. As soon as the project starts to contain the first classes, utility functions, and other things that should be separated, working in one file becomes simply impossible. This is where build files come to our aid, as well as advanced toolchain settings.

📄️ Execution Context

Defines the space where all your code resides. Variables and constant values, functions, and converted classes are stored here, and future code interactions with the space are performed here.

📄️ Integrating Libraries

Can be done from any mod script. Libraries extend the capabilities of the game or simplify the creation of existing ones. In addition, you can even isolate part of your code to use it as a library; these are regular scripts whose context will be considered now.

📄️ where-what-and-who

📄️ callbacks

📄️ updatables

📄️ threading

📄️ using-synced-data

📄️ first-item

📄️ food-armor-and-throwables

📄️ recipes

🗃️ Extra

2 items

📄️ tools

📄️ First Block

The entire world of Minecraft consists of blocks. The player and creatures move on them, mining them allows the player to obtain resources and create new blocks to create other blocks, and some can be opened or interacted with in some way. Let's start by looking at textures, and then create blocks with different variations.

📄️ First Liquid

Liquids are blocks that spread over a plane, which usually make it difficult for creatures to move through them and form currents. In-game liquids include water and lava.