Qubica Wiki - User contributions [en]

Creating a Mod

2025-12-18T04:31:56Z

Shishkabob: /* Other folders */

Mods are a core part of Qubica and are extremely easy to make with the power of Lua.

== Locating the local mods folder ==

{| class="wikitable"
|+ Local mods folder location
|-
! Windows
|-
| C:\Users\YOUR_USERNAME\AppData\LocalLow\Tomahawk Interactive\Qubica\mods\
|}

Local mods are stored here.

== Creating the mod's folder structure ==
In your local mod's folder, create a folder with the name of your mod, this name won't be shown to the end-user. enter the folder and create <code>mod.json</code>, this contains the metadata about your mod.

The contents of <code>mod.json</code> should look something like:
<syntaxhighlight lang="json">
{
"name": "Indestructible Item",
"description": "All items now have infinite durability!",
}
</syntaxhighlight>

An icon for your mode can also be placed in this folder under <code>icon.png</code>

These are the only files that Qubica looks for in the root folder of your mod, however several other folders are check here.

=== Other folders ===
* <code>assets/</code> - Should contain you mod's textures, models, and sounds
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>scripts/</code> - Contains your Lua code.
* <code>binary/</code> - The only folder accessible through the Filesystem API.

== Defining a block ==
Blocks are defined in <code>your_mod_folder/data/blocks.json</code>. Create this file if you haven't yet.

Example of <code>blocks.json</code>:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"name": "Dirt",
"texture": "textures/blocks/dirt.png",
"textureRotation": 3,
"health": 5,
"toolCategories": ["shovel"]
},
{
"id": "qubica:stone",
"name": "Stone",
"texture": "textures/blocks/stone.png",
"textureRotation": 3,
"health": 8,
"toolCategories": ["pickaxe"]
}
]
</syntaxhighlight>

Reminder that the <code>texture</code> field is relative to your mod's assets folder.

=== Redefining a block ===
Blocks can also have the data modified by mods. This is done by simply defining a block with the same ID as an already existing block.

Example of a mod making a dirt block indestructible:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"health": -1
}
]
</syntaxhighlight>

Notice how only the health field is defined here, only fields redefined will replaced/added to the block's data.

== Texture replacements ==
Textures for blocks and items can be easily replaced by mods of a high priority, they just need to be placed in the same location, or have their <code>texture</code> field redefined to point to it's new location.

=== Hotloading ===
Once a texture has been loaded in game, it can be hotloaded, which allows you to see your changes instantly.

== Qubica is a mod ==
Qubica itself uses the same system for defining objects and loading textures as mods do, this allows you to easily replace data, textures, and add your own code.

== Mod Examples ==
Examples of different types of mods are available in the Qubica's install folder, including Qubica itself.

Creating a Mod

2025-12-18T01:07:38Z

Shishkabob: /* Locating the local mods folder */

Mods are a core part of Qubica and are extremely easy to make with the power of Lua.

== Locating the local mods folder ==

{| class="wikitable"
|+ Local mods folder location
|-
! Windows
|-
| C:\Users\YOUR_USERNAME\AppData\LocalLow\Tomahawk Interactive\Qubica\mods\
|}

Local mods are stored here.

== Creating the mod's folder structure ==
In your local mod's folder, create a folder with the name of your mod, this name won't be shown to the end-user. enter the folder and create <code>mod.json</code>, this contains the metadata about your mod.

The contents of <code>mod.json</code> should look something like:
<syntaxhighlight lang="json">
{
"name": "Indestructible Item",
"description": "All items now have infinite durability!",
}
</syntaxhighlight>

An icon for your mode can also be placed in this folder under <code>icon.png</code>

These are the only files that Qubica looks for in the root folder of your mod, however several other folders are check here.

=== Other folders ===
* <code>assets/</code> - Should contain you mod's textures, models, and sounds
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>scripts/</code> - Contains your Lua code.
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>binary/</code> - The only folder accessible through the Filesystem API.

== Defining a block ==
Blocks are defined in <code>your_mod_folder/data/blocks.json</code>. Create this file if you haven't yet.

Example of <code>blocks.json</code>:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"name": "Dirt",
"texture": "textures/blocks/dirt.png",
"textureRotation": 3,
"health": 5,
"toolCategories": ["shovel"]
},
{
"id": "qubica:stone",
"name": "Stone",
"texture": "textures/blocks/stone.png",
"textureRotation": 3,
"health": 8,
"toolCategories": ["pickaxe"]
}
]
</syntaxhighlight>

Reminder that the <code>texture</code> field is relative to your mod's assets folder.

=== Redefining a block ===
Blocks can also have the data modified by mods. This is done by simply defining a block with the same ID as an already existing block.

Example of a mod making a dirt block indestructible:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"health": -1
}
]
</syntaxhighlight>

Notice how only the health field is defined here, only fields redefined will replaced/added to the block's data.

== Texture replacements ==
Textures for blocks and items can be easily replaced by mods of a high priority, they just need to be placed in the same location, or have their <code>texture</code> field redefined to point to it's new location.

=== Hotloading ===
Once a texture has been loaded in game, it can be hotloaded, which allows you to see your changes instantly.

== Qubica is a mod ==
Qubica itself uses the same system for defining objects and loading textures as mods do, this allows you to easily replace data, textures, and add your own code.

== Mod Examples ==
Examples of different types of mods are available in the Qubica's install folder, including Qubica itself.

Creating a Mod

2025-12-18T00:25:54Z

Shishkabob: Shishkabob moved page Create a Mod to Creating a Mod: Misspelled title

Mods are a core part of Qubica and are extremely easy to make with the power of Lua.

== Locating the local mods folder ==

{| class="wikitable"
|+ Local mods folder location
|-
! Windows
|-
| C:\Users\shishkabob\AppData\LocalLow\Tomahawk Interactive\Qubica\mods\
|}

Local mods are stored here.

== Creating the mod's folder structure ==
In your local mod's folder, create a folder with the name of your mod, this name won't be shown to the end-user. enter the folder and create <code>mod.json</code>, this contains the metadata about your mod.

The contents of <code>mod.json</code> should look something like:
<syntaxhighlight lang="json">
{
"name": "Indestructible Item",
"description": "All items now have infinite durability!",
}
</syntaxhighlight>

An icon for your mode can also be placed in this folder under <code>icon.png</code>

These are the only files that Qubica looks for in the root folder of your mod, however several other folders are check here.

=== Other folders ===
* <code>assets/</code> - Should contain you mod's textures, models, and sounds
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>scripts/</code> - Contains your Lua code.
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>binary/</code> - The only folder accessible through the Filesystem API.

== Defining a block ==
Blocks are defined in <code>your_mod_folder/data/blocks.json</code>. Create this file if you haven't yet.

Example of <code>blocks.json</code>:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"name": "Dirt",
"texture": "textures/blocks/dirt.png",
"textureRotation": 3,
"health": 5,
"toolCategories": ["shovel"]
},
{
"id": "qubica:stone",
"name": "Stone",
"texture": "textures/blocks/stone.png",
"textureRotation": 3,
"health": 8,
"toolCategories": ["pickaxe"]
}
]
</syntaxhighlight>

Reminder that the <code>texture</code> field is relative to your mod's assets folder.

=== Redefining a block ===
Blocks can also have the data modified by mods. This is done by simply defining a block with the same ID as an already existing block.

Example of a mod making a dirt block indestructible:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"health": -1
}
]
</syntaxhighlight>

Notice how only the health field is defined here, only fields redefined will replaced/added to the block's data.

== Texture replacements ==
Textures for blocks and items can be easily replaced by mods of a high priority, they just need to be placed in the same location, or have their <code>texture</code> field redefined to point to it's new location.

=== Hotloading ===
Once a texture has been loaded in game, it can be hotloaded, which allows you to see your changes instantly.

== Qubica is a mod ==
Qubica itself uses the same system for defining objects and loading textures as mods do, this allows you to easily replace data, textures, and add your own code.

== Mod Examples ==
Examples of different types of mods are available in the Qubica's install folder, including Qubica itself.

File:Qubica-wiki-icon.png

2025-12-18T00:24:01Z

Shishkabob: Protected "File:Qubica-wiki-icon.png" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite))

File:Qubica-wiki-icon.png

2025-12-18T00:23:45Z

Shishkabob:

File:Qubica-icon.png

2025-12-18T00:19:14Z

Shishkabob: Protected "File:Qubica-icon.png" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [Upload=Allow only administrators] (indefinite))

File:Qubica-icon.png

2025-12-18T00:17:23Z

Shishkabob:

Creating a Mod

2025-12-18T00:05:37Z

Shishkabob: Created page with "Mods are a core part of Qubica and are extremely easy to make with the power of Lua. == Locating the local mods folder == {| class="wikitable" |+ Local mods folder location |- ! Windows |- | C:\Users\shishkabob\AppData\LocalLow\Tomahawk Interactive\Qubica\mods\ |} Local mods are stored here. == Creating the mod's folder structure == In your local mod's folder, create a folder with the name of your mod, this name won't be shown to the end-user. enter the folder and cr..."

Mods are a core part of Qubica and are extremely easy to make with the power of Lua.

== Locating the local mods folder ==

{| class="wikitable"
|+ Local mods folder location
|-
! Windows
|-
| C:\Users\shishkabob\AppData\LocalLow\Tomahawk Interactive\Qubica\mods\
|}

Local mods are stored here.

== Creating the mod's folder structure ==
In your local mod's folder, create a folder with the name of your mod, this name won't be shown to the end-user. enter the folder and create <code>mod.json</code>, this contains the metadata about your mod.

The contents of <code>mod.json</code> should look something like:
<syntaxhighlight lang="json">
{
"name": "Indestructible Item",
"description": "All items now have infinite durability!",
}
</syntaxhighlight>

An icon for your mode can also be placed in this folder under <code>icon.png</code>

These are the only files that Qubica looks for in the root folder of your mod, however several other folders are check here.

=== Other folders ===
* <code>assets/</code> - Should contain you mod's textures, models, and sounds
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>scripts/</code> - Contains your Lua code.
* <code>data/</code> - Definitions for blocks, items, clothes and crafting recipes.
* <code>binary/</code> - The only folder accessible through the Filesystem API.

== Defining a block ==
Blocks are defined in <code>your_mod_folder/data/blocks.json</code>. Create this file if you haven't yet.

Example of <code>blocks.json</code>:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"name": "Dirt",
"texture": "textures/blocks/dirt.png",
"textureRotation": 3,
"health": 5,
"toolCategories": ["shovel"]
},
{
"id": "qubica:stone",
"name": "Stone",
"texture": "textures/blocks/stone.png",
"textureRotation": 3,
"health": 8,
"toolCategories": ["pickaxe"]
}
]
</syntaxhighlight>

Reminder that the <code>texture</code> field is relative to your mod's assets folder.

=== Redefining a block ===
Blocks can also have the data modified by mods. This is done by simply defining a block with the same ID as an already existing block.

Example of a mod making a dirt block indestructible:
<syntaxhighlight lang="json">
[
{
"id": "qubica:dirt",
"health": -1
}
]
</syntaxhighlight>

Notice how only the health field is defined here, only fields redefined will replaced/added to the block's data.

== Texture replacements ==
Textures for blocks and items can be easily replaced by mods of a high priority, they just need to be placed in the same location, or have their <code>texture</code> field redefined to point to it's new location.

=== Hotloading ===
Once a texture has been loaded in game, it can be hotloaded, which allows you to see your changes instantly.

== Qubica is a mod ==
Qubica itself uses the same system for defining objects and loading textures as mods do, this allows you to easily replace data, textures, and add your own code.

== Mod Examples ==
Examples of different types of mods are available in the Qubica's install folder, including Qubica itself.

Main Page

2025-12-17T19:43:54Z

Shishkabob:

<strong>Welcome to the Qubica Wiki!</strong>

== Links ==
* [https://store.steampowered.com/app/2360800/Qubica/ Steam Page]
* [https://www.reddit.com/r/qubica/ Reddit]
* [https://discord.gg/Md7uE8SqcG Discord]
* [https://www.kickstarter.com/projects/tomahawkinteractive/qubica-a-25d-sandbox-adventure-inspired-by-the-blockheads Kickstarter]