Server packs are sets of data files that determine how a world behaves; in an (hypothetical) multiplayer environment, all players must share the same set of server files.

Data is split into packs, each one being a folder under packs/PACK; objects defined inside them have names automatically prefixed by PACK..

[[TOC]]

Cell Types

Description of every type of cell that can be used in a world.

[NAME]
empty = false
solid = true
opaque = true
slow = false
drop = PACK.NAME
capacity = 0
interact = none
light = 0

The file contains any number of [NAME] sections, defining the cell type named PACK.NAME

Interaction

Interaction type determines how the cell responds to the player attempting to interact with it.

If interaction type is anything other than ‘none’ the crosshairs will change shape when hovering over the cell.

Mob Types

Description of every type of mob that can be used in a world.

[NAME]
size = 0.5 0.5
drop = PACK.NAME
solid = false
persistent = false
items = 0
interact = none
state = ...
signal = ...

The file contains any number of [NAME] sections, defining the mob type named PACK.NAME

Interaction

Interaction type determines how the mob responds to the player attempting to interact with it.

If interaction type is anything other than ‘none’ the crosshairs will change shape when hovering over the mob.

State

States determines mob behavior. State descriptions are lines of the form:

state = TASK FRAMES [then SUCCESS] [else FAILURE]

• ‘TASK’ determines what the mob is doing during that state.
• ‘FRAMES’ determines how long the state lasts.
• ‘SUCCESS’ is the state that follows this one if ‘TASK’ succeeds; if not specified, the mob goes back to the same state.
• ‘FAILURE’ is the state that follows this one if ‘TASK’ fails; if not specified, the mob goes back to the same state.

Valid tasks for mobs are:

Signal

Signals allow the mob state machine to jump states in response to an external condition. Signal descriptions are lines of the form:

signal = SIGNAL STATE

This would cause the mob to jump to ‘STATE’ in response to a signal of type ‘SIGNAL’ regardless of what it was doing at that moment.

Item Types

Description of every type of item that can be used in a world.

[NAME]
place = ...
spawn = ...

The file contains any number of [NAME] sections, defining the item type named PACK.NAME

Recipes

Description of the ways items can be crafted into different items

[BENCH]
result = item amount
from = item amount
from = item amount

The section name is not the name of the recipe (recipes do not have names), but the name of the bench block (full name of a cell declared on a cell_types.cfg file).

The bench block determines which cell (if any) must be interacted with to use the recipe. If the value is empty ([]) the recipe can be used from the default inventory.

Section names can and will repeat in the recipes file, each one defining a different recipe with the same bench.

Both result and from entries have values consisting on an item type name of the form PACK.NAME that must correspond to the section [NAME] at packs/PACK/item_types.cfg, and an optional integer that determines the amount of items of that type, and defaults to 1 if not specified.

World Generation

Equation describing how terrain height is calculated.

(+
 60
 (*
  (^ (* (+ 1 (noise 0.0625 1)) (noise 0.125 1)) 2)
  (+ 16 (noise 2 4) (noise 8 2)))
 (* -2 (< (abs (noise -1 1)) 0.2)))

The file contains only an expression; an expression is either:

• a number
• an parenthesis-enclosed, space-separated array whose first element is a function name, the rest of the elements being additional expressions.