Knuckle Cracker Wiki

The name that will be shown to the player.

When true, the unit remains in the inventory at an amount of “0” even when all are built.

When true, this unit will not appear in the editor's table of units to build.

The max energy ammo for the unit.

The starting enery ammo for the unit.

The max AC ammo for the unit.

The starting AC ammo for the unit [build 46 and later].

When true, this unit acts as a portal for packets.

When true, this unit acts as an apex ship.

When true, this unit is treated as an enemy (non player) unit.

The cost, in green packets, to collect this unit. When greater than 0, this unit becomes collectable.

Whether or not a unit is selectable by the player.

Whether or not a unit can be moved by the player. In this instance, it means dematerialization based movement.

Used for legality of placement for movable units. When units are in different move layers, they do not collide and can be stacked.

When true, the unit is controlled by the physics engine.

When the unit has physics, this controls the rigid body constraints. The int is treated as a bit field with bit 0 meaning to freeze x-axis motion, bit 1 meaning to freeze y-axis motion, and bit 2 meaning to freeze rotation. Multiple bits can be set at the same time. So “7” would freeze all motion and rotation. “4” would freeze just rotation, etc.

The scale at which gravity affects the unit when the unit has physics enabled. 1 is the default.

How a unit rotates/flips when moving. 0 = NONE, 1 = FLIP, 2 = FOURWAY.

When true, the unit will auto destroy when the pixel count is too low. The “DeadFraction” is the maximum allowed amount of dead pixels.

A fraction (0 to 1 range) that specifies the maximum dead pixel amount allowed on a unit before it self destructs, when destroyonhealth is true.

An optional health that can be used to track damage on a unit. Not related to the pixel count. When the internalHealth starts greater than 0 and is then damaged down to 0, the unit is destroyed.

The max optional health.

The regeneration rate of the optional health per game update.

The damage that occurs to the optional health when over creeper.

The damage that occurs to the optional health when over AC.

The damage that occurs to the optional health when over a bot.

When true, enemy units like phantoms and bots will ignore this unit.

When true, a dark ray will damage the unit.

When true, exploding sand will damage the unit.

When true, the unit can be nullified.

When true, the unit acts as a rift inhibitor objective.

When true, the unit acts as an IXE core objective.

The cell range to look for an anchor point. When non-zero, the unit will attempt to anchor itself to land in this range. If not fould, placement of the unit will be illegal.

The distance an anchor will attempt to maintain between the anchor and the anchor cell.

What to do when an anchor cell is lost. 0 = destroy unit, 1 = remove anchor, 2 ignore and keep anchor.

When true, the unit can manage the mouse drawn move paths. Used by the spirit ship, for instance.

When true, the player can destroy the unit.

When true, the player can toggle the build supply for the unit.

When true, the player can toggle the ammo supply for the unit.

When true, a physics controlled unit will not collide with other units.

The amount of ammo to automatically add to the unit each game frame.

The amount of AC ammo to automatically add to the unit each game frame.

The game frame ammo request rate. Default is 6.

The game frame AC ammo request rate. Default is 6.

When false, the unit won't request ammo or AC ammo. Defaults to true.

The game objective type for the unit. The types are: 0 = NONE, 1 = IXE_CORE, 2 = INHIBITOR, 3 = ITEM, 4 = EMITTER, 5 = CREEPER, 6 = SPECIAL, 7 = MISSION

Similar to autoAmmo, except added in the late game update.

The type of physics 'material] to use. The types are: 0 = NONE, 1 = LOW_FRICTION, 2 = NO_FRICTION.

The name of another unit type to destroy when this unit is destroyed.

When true, will activate any inactive ixe cores on the map when this unit is destroyed.

When true, will show a bar for the internal health.

The position of the internal health bar.

When true, the unit will visually sort behind the creeper.

The visual sorting order.

Creates a text label on the unit.

The rotation of the part.

Whether the part should rotate when the part is flipped.

If the part should be built already.

If creeper damages the part.

If AC damages the part.

If bots damages the part.

The maximum amount of energy the unit can store for energy dispatch.

An array of three values for energy production. Min production (starting production), max production, and ramp time in game updates.

If the part causes digitalis to grow.

The rate at which creeper damages each pixel of a part. Default is 10000.

The rate at whcih part pixels heal when damaged and not under creeper. Default is 10000.

The game updates it takes to regrow a part pixel. Default is 500.

Whether sand damages the pixels of this part.

If Sand Particles can damage the part.

When true, a unit with a show_range will always show the range with a range circle.

The range to reveal FOW (fog of war).

For physics controlled units, the unit will be frozen if this is true and the part is over blocking sand.

For physics controlled units will apply a force upwards when over a sand that is a liquid.

The physics drag for the whole unit when this part is over a liquid sand.

The default drag on the whole unit.

The layer that determins what shots hit the part. 0 = Default, 1 = Shot_Hits1, 2 = ShotHits2

The upgrade gems awarded when the part is destroyed with destroy actions enabled.

The physics collider for the part. The type can be “none”, “circle”, “box”, “capsule”. For “none” there are no additional args. For “circle” and additional arg of “radius”:float is supported. For “box” two addional args are supported “width”:float, and “height”:float. For “capsule” three addional args are supported “width”:float, “height”:float, and “direction”:“horizontal”|“vertical”.

The path name for the image to use for the parts pixels.

The pivot for the part. 0.5,0.5 is the center.

The visual sorting order used for the parts pixels.

The exclusion mask for the parts collider.

The x,y, scale of the part.

The path to an image that contains frames of an animation.

A list of RPL scripts to attach to the part. Each {script} consists of a “name”:“scriptname” field and then any name:value args to be passed into the script.

A list of controllers to attach to the part. Each {controller} consists of a “name”:“controllername” field and then any nam:value args to be passwed into the script.

A list of sub parts. Each {part} consists of a “name”:“part_json”, “position”:[float,float], “rotation”: float, “sortingorder”:int, “active”:bool.