December 12, 2019

Physics World – API Reference

By Nancy |

Physics World

These methods adjust the physics settings from the world menu. For more information, see the world options manual.

Function	Description
checkSphereCollision(position, radius, filter)	Checks if anything collides with the sphere at the given position with the given radius. Filter has these possible values: “kAll”, “kSensor”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, value from Asset Attribute, Entity.
disableDeactivation(value)	When a dynamic body is not moved for a few seconds, it will go into sleep mode. In sleep mode, the physics engine skips the body’s simulation. Sleep mode can be disabled with this method. By default, sleep mode is be enabled.
getSphereCollisions(position, radius, filter)	Returns colliders with a sphere at the given position with the given radius. Filter has these possible values: “kAll”, “kSensor”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, value from Asset Attribute, Entity.
rayTest(from, to, filter)	Returns physics bodies that collide with a ray between the two given Vec3 coordinates. The object returned has the properties bodies and sensors. Optional filter has these possible values: “kAll”, “kSensor”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, value from Asset Attribute, Entity.
setSubSteps(value)	Sets the value of the sub steps setting in the world options menu.
setTimeWarp(value)	Sets the value of the time warp setting in the world options menu.
subSteps()	Returns the value of sub steps from the world options menu.
timeWarp()	Returns the value of time warp from the world options menu.

checkSphereCollision(position, radius, filter)

Checks if anything collides with the sphere at the given position with the given radius. Filter has these possible values: “kAll”, “kSensor”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, value from Asset Attribute, entity.

Parameters

Vec3 position – the position of the sphere
number radius – the radius of the sphere
string filter – / AssetModel / Entity / optional: “kAll” the filter of items to look for

Returns

boolean true if there is a collision, false if not

↑ Back to top

disableDeactivation(value)

When a dynamic body is not moved for a few seconds, it will go into sleep mode. In sleep mode, the physics engine skips the body’s simulation. Sleep mode can be disabled with this method. By default, sleep mode is be enabled.

Parameters

boolean value – true to disable deactivation, false to enable it

↑ Back to top

getSphereCollisions(position, radius, filter)

Returns colliders with a sphere at the given position with the given radius. One use case for this method would be interating through all the colliders within a sphere and adding damage to them for an explosion. Filter has these possible values: “kAll”, “kSensor”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, “kGround”, value from Asset Attribute, entity.

Parameters

Vec3 position – the position of the sphere
number radius – the radius of the sphere
string filter – / AssetModel filter / Entity filter the filter of items to look for

Returns

Object with properties {bodies, sensors} – an array of bodies and an array of sensors within the sphere

↑ Back to top

rayTest(from, to, filter)

Returns physics bodies that collide with a ray between the two given Vec3 coordinates. Optionally takes a filter parameter which has these possible values: “kAll”, “kSensor”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, value from Asset Attribute, entity.

The object returned by this function has the properties {bodies, sensors} which are each arrays. The bodies and sensors objects have the properties {object, hitPoint}.

Parameters

Vec3 from – the starting coordinate
Vec3 to – the ending coordinate
string filter – / AssetModel filter / Entity filter the filter of items to look for

Returns

Object with properties {bodies, sensors}.

// choose an object as the Selected Character with ray testing. pt is where the user tapped.

let ray = cam.screenRay(pt);
let rtst = this.scene().physicsWorld().rayTest(
        ray.origin,
        ray.origin.add(ray.direction.scale(100))
    );
    
    for (let i = 0; i < rtst.bodies.length; ++i) {
        let hit = rtst.bodies[i];
        Settings.selectedCharacter = hit.object.parentEntity().name();
        return;
    }

↑ Back to top

setSubSteps(value)

Sets the value of the sub steps setting in the world options menu.

Parameters

number value – the new sub steps value

↑ Back to top

setTimeWarp(value)

Sets the value of the time warp setting in the world options menu.

Parameters

number value – the new time warp value

↑ Back to top

subSteps()

Returns the value of sub steps from the world options menu.

Returns

number the sub step value

↑ Back to top

timeWarp()

Returns the value of time warp from the world options menu.

Returns

number the time warp value

↑ Back to top

Did you find this page useful?

Please give it a rating:

September 18, 2019

0

Control Nodes – Buildbox 3 Manual

By Buildbox |

Control Nodes

These nodes allow you to attach a variety of controls to your asset, such as touch, swipe, keyboard buttons, and mouse controls.

For details on how to add a control node to a character or object in a game, see Adding, Editing, and Deleting Nodes.

Node	Icon	Description	Customizable?
Touch		Enables any connected nodes when the entire screen is activated by either the touch or release of a finger, or the click or release of the mouse.	No
Touch Move		Allows the player to change the position of the asset by dragging it across the screen with either a finger or mouse.	Yes
Touch Rotate		Allows the player to change the rotation of the asset by dragging it across the screen with either a finger or mouse.	Yes
Is Touched		Activates any connected nodes immediately when the player clicks or taps the screen.	Yes
Touch Path		Puts the asset on a continuous path moving forward, and allows the asset to be moved from side to side by dragging left or right across the screen using a finger or mouse.	Yes
4-Way Swipe		Allows the player to drag the screen in 4 directions, up, down, left, and right.	Yes
UI Button		Allows the player to click or tap a specified area on the screen to activate any connected nodes.	No
Keyboard Button		Assigns a button on the keyboard to activate any connected nodes.	No
Keyboard Move		Allows the WASD and Arrow keyboard buttons to enable any connected nodes.	No
Mouse Button		Assigns a Mouse Button that will activate any connected nodes.	No
Mouse Move		Allows the movement of the mouse to enable any connected nodes.	No
Mouse Scroll		Allows the scroll wheel of the mouse to enable any connected nodes.	No

July 17, 2020

0

Linking JavaScript Files – API Reference

By Justin Leon |

Linking JavaScript Files

The Buildbox JavaScript panel allows you to link a custom node script to a JavaScript file on your computer, allowing you to use an external text editor to update and change your custom node script. Whether you update the file in the Buildbox JavaScript panel or external editor, it will be updated in both locations

To access the JavaScript panel, on an asset’s node map, double-click a node or click its edit icon.

To link a file to the JavaScript panel, click Link File at the bottom-right of the JavaScript panel, and depending on whether you need to export the file from or import it to Buildbox, choose one of the following procedures below.

Export to File & Link

Select Export File & Link. The Save As window appears.
Select the location where you want to save the file.
Name the file and click Save.

A JavaScript file with the custom node script is now created locally on your computer and is linked to your custom node inside Buildbox.

Import from File & Link

Select Import from File & Link.
On your computer, navigate to the JavaScript file that contains your custom node script.
Click Open.

The script from your JavaScript file appears in the Buildbox JavaScript panel and is linked to your local file.

To avoid breaking the link to your JavaScript file, avoid moving or renaming the JavaScript file on your computer, or deleting the linked node in Buildbox,

After you link a JavaScript file to a node, click the icon at the bottom right of the JavaScript panel to view the following options:

Option	Description
Open Externally	Opens the linked JavaScript file using your default script editor.
Show in Folder	Opens the folder that contains the linked JavaScript file.
Export to File & Link	Creates and saves a JavaScript file that contains your custom node script locally on your computer and links the file to the Buildbox JavaScript panel.
Import from File & Link	Imports and creates a link to a JavaScript file from your computer to the Buildbox JavaScript panel.
Unlink	Unlinks the JavaScript file from the Buildbox JavaScript panel. The updates will no longer be synchronized.

Did you find this page useful?

Please give it a rating:

December 12, 2019

0

Physics Component – API Reference

By Nancy |

Physics Component

This component is used for processing physics. You can find the physics menu in the Start node. To access these functions, you can use this.entity().physics().

Function	Description
activateBody()	When the body type is “kDynamic” and “Always Active” is disabled, the body will become inactive after a short period of time. This function activates it again.
affectedAsset()	Returns the affected asset set for the physics component. This decides what type of assets this body can interact with.
angularDamping()	Returns the angular damping factor. Angular damping simulates drag; the higher the value, the more this entity will resist rotation.
angularVelocity()	Returns the current angular velocity value of the object.
clearVelocities()	Sets angular and linear velocity to zero.
collisionData()	Returns an object containing collision data for this entity. Optionally an Entity can be passed to get data about one entity specifically.
collisionGroup()	Returns the collision group of the object.
disableDeactivation(value)	A body will become inactive after a short period of time if left alone. If you disable deactivation, the body will always stay active. This is recommended for Linker entities.
friction()	Returns the body’s friction value.
gravity()	Returns the gravity value affecting the entity. If it hasn’t been adjusted for this entity, this method will return the gravity value of the Scene.
hasCollision(entity)	Returns true if the given entity collides with the current one.
isPhysics()	Returns true if physics is enabled on this entity, false if not.
linearDamping()	Returns the linear damping factor. Linear damping simulates drag; the higher the value, the more this entity will resist translation.
linearFactor()	Returns “position factor” of the physics component. The linear factor determines how the physics engine affects specific linear/position axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.
linearVelocity()	Returns the current linear velocity value of the entity.
mass()	Returns the mass value of the entity. This defaults to 1.
mesh()	Returns the collision shape mesh if assigned. Null if a mesh is not being used as the collision shape.
parentEntity()	Returns the entity that this physics component belongs to.
predictedPosition(time)	Returns the predicted position of the body based on the given time.
rebuildShape()	Call this function to update the physics collision shape. This should be done if you change the shape or scale of your Entity in code.
restitution()	Returns the “Bounce” value of the physics component. The higher the value, the higher the bounce upon collision.
setAffectedAsset(value)	Sets the affected asset for the physics component. This decides what type of assets this body can interact with. Possible values: “kAll”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, “kPath”, Asset.
setAngularDamping(value)	Sets the angular damping factor, range 0-1. Angular damping simulates drag; the higher the value, the more this entity will resist rotation.
setAngularFactor(x, y, z)	Sets the “rotation factor” of the object. This determines how the physics engine affects specific angular/rotation axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.
setAngularVelocity(x, y, z)	Sets the angular velocity value of the object.
setCollisionGroup(group)	Set the collision group of the entity.
setCreated(value)	Enables/disables everything that is connected to the “Start” node.
setFriction(value)	Sets the friction value for the body.
setGravity(x, y, z)	Sets gravity value affecting this entity. This will override the gravity value in the scene, and will not affect other objects.
setLinearDamping(value)	Sets the linear damping factor, range 0-1. Linear damping simulates drag; the higher the value, the more this entity will resist translation.
setLinearFactor(x, y, z)	Sets the “position factor” of the object. This determines how the physics engine affects specific linear/position axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.
setLinearVelocity(x, y, z)	Sets the linear velocity of the entity.
setMass(value)	Sets the mass of the entity. A mass of 0 will not be affected by gravity.
setMesh(mesh)	Sets the mesh of the collision shape from a MeshModel script attribute.
setMesh(name)	Sets the mesh of the collision shape based on the name of the mesh.
setPhysics(value)	Enables/disables physics.
setRestitution(value)	Sets the “Bounce” value of the physics component. The higher the value, the higher the bounce upon collision.
setShapePosition(x, y, z)	Sets the collision shape position of the object. Note: you must call rebuildShape() after calling this for the change to be reflected in game.
setShapeRotation(x, y, z)	Sets the collision shape rotation of the object. Note: you must call rebuildShape() after calling this for the change to be reflected in game.
setShapeScale(x, y, z)	Sets the collision shape scale of the object. Note: you must call rebuildShape() after calling this for the change to be reflected in game.
setShapeType(type)	Sets the shape type. Highly recommended to use “kHullShape” over “kMeshShape”.
setType(value)	Sets the type of the physics body.
shapePosition()	Returns the position of the collision shape.
shapeRotation()	Returns the rotation of the collision shape.
shapeScale()	Returns the scale of the collision shape.
shapeType()	Returns the shape type of the collision shape.
type()	Returns the type of the physics body.

activateBody()

When the body type is “kDynamic” and “Always Active” is disabled, the body will get inactive after a short period of time. This function activates it back.

↑ Back to top

affectedAsset()

Returns the affected asset set for the physics component. This decides what type of assets this body can interact with. Possible values: “kAll”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, “kPath”, Asset.

Returns

string / Asset – the asset or group of assets this body can interact with

↑ Back to top

angularDamping()

Returns the angular damping factor. Angular damping simulates drag; the higher the value, the more this entity will resist rotation.

Returns

number – the angular damping factor, range 0-1

↑ Back to top

angularFactor()

Returns the “rotation factor” of the physics component. The angular factor determines how the physics engine affects specific angular/rotation axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.

Returns

Vec3 the {x, y, z} components of the angular factor.

↑ Back to top

angularVelocity()

Returns the current angular velocity value of the object.

Returns

Vec3 the {x, y, z} components of the angular velocity.

↑ Back to top

clearVelocities()

Sets angular and linear velocity to zero.

↑ Back to top

collisionData()

Returns an object containing collision data for this entity. Optionally an Entity can be passed to get data about one entity specifically.

The returned object will have these properties (Data types in parenthesis). Keep in mind that a property is accessed like this: this.entity().physics().collisionData().totalImpulse;.

entity – the entity that’s being collided with (Entity)
totalImpulse – the total impulse from all collision points (number)
collisionPoints – an array of objects containing data about each point of collision (array of Objects). Each object in the array has these properties:
– impulse – the impulse from the collision point (number)
– normal – the normal of the collision point (Vec3)
– position – the position of the collision point (Vec3)

Parameters

Entity (optional) an entity to check collision data with the current entity

Returns

Object – data object containing the information listed above

↑ Back to top

collisionGroup()

Returns the collision group of the object.

Returns

string possible values: kNone, kCharacter, kEnemy, kPlatform, kCoin

↑ Back to top

disableDeactivation(value)

A body will become inactive after a short period of time if left alone. If you disable deactivation, the body will always stay active. This is recommended for Linker entities.

Parameters

boolean value – true to keep the entity always active, false to allow it to become inactive as normal

↑ Back to top

friction()

Returns the body’s friction value. This can also be seen in the Start node unless altered at runtime.

Returns

number the friction value of the body

↑ Back to top

gravity()

Returns the gravity value affecting the entity. If it hasn’t been adjusted for this entity, this method will return the gravity value of the Scene.

Returns

number the current gravity value of the entity.

↑ Back to top

hasCollision(entity)

Returns true if the given entity collides with the current one.

Parameters

Entity entity the entity to check for a collision with

Returns

boolean true if the entities are colliding, false if not.

↑ Back to top

isPhysics()

Returns true if physics is enabled, false if not.

Returns

boolean true if physics is enabled, false if not.

↑ Back to top

linearDamping()

Returns the linear damping factor. Linear damping simulates drag; the higher the value, the more this entity will resist translation. Default value: 0

Returns

number the linear damping, range 0-1.

↑ Back to top

linearFactor()

Returns “position factor” of the physics component. The linear factor determines how the physics engine affects specific linear/position axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.

Returns

Vec3 the {x, y, z} linear factor.

↑ Back to top

linearVelocity()

Returns the current linear velocity value of the entity.

Returns

Vec3 the {x, y, z} linear velocity of the entity.

↑ Back to top

mass()

Returns the mass value of the entity. This defaults to 1.

Returns

number the mass of the entity

↑ Back to top

mesh()

Returns the collision shape mesh if assigned. Null if a mesh is not being used as the collision shape.

Returns

MeshModel the object of the collision shape mesh

↑ Back to top

parentEntity()

Returns the entity that this physics component belongs to.

Returns

Entity the parent entity of the physics component

↑ Back to top

predictedPosition(time)

Returns the predicted position of the body based on the given time.

Parameters

number time – the number of seconds from now that you’d like to predict the position of the entity

Returns

Vec3 entity’s predicted {x, y, z} position after time based on its current Velocity.

↑ Back to top

rebuildShape()

Call this function to update the physics collision shape. This should be done if you change the shape or scale of your Entity in code.

↑ Back to top

restitution()

Returns the “Bounce” value of the physics component. The higher the value, the higher the bounce upon collision.

Returns

number the “Bounce” value of the physics component

↑ Back to top

setAffectedAsset(value)

Sets the affected asset for the physics component. This decides what type of assets this body can interact with. Possible values: “kAll”, “kEnemy”, “kPlatform”, “kCoin”, “kCharacter”, “kPath”, Asset.

Parameters

string value / Asset value – the asset or group of assets this body can interact with

↑ Back to top

setAngularDamping()

Sets the angular damping factor, range 0-1. Angular damping simulates drag; the higher the value, the more this entity will resist rotation.

Parameters

number value – the angular damping factor

↑ Back to top

setAngularFactor(x, y, z)

Sets the “rotation factor” of the object. This determines how the physics engine affects specific angular/rotation axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.

Parameters

number x – the x component of the new angular factor
number y – the y component of the new angular factor
number z – the z component of the new angular factor

↑ Back to top

setAngularVelocity(x, y, z)

Sets the angular velocity value of the object.

Parameters

number x – the x component of the new angular velocity
number y – the y component of the new angular velocity
number z – the z component of the new angular velocity

↑ Back to top

setCollisionGroup(group)

Set the collision group of the entity.

Parameters

string group – possible values: kNone, kCharacter, kEnemy, kPlatform, kCoin

↑ Back to top

setCreated(value)

Enables/disables everything that is connected to the “Start” node.

Parameters

boolean value – true to enable, false to disable

↑ Back to top

setFriction(value)

Sets the friction value for the body. This can also be changed in the Start node.

Parameters

number value – the new friction value

↑ Back to top

setGravity(x, y, z)

Sets gravity value affecting this entity. This will override the gravity value in the scene, and will not affect other objects.

Parameters

number x – the x component of the new gravity
number y – the y component of the new gravity
number z – the z component of the new gravity

↑ Back to top

setLinearDamping(value)

Sets the linear damping factor, range 0-1. Linear damping simulates drag; the higher the value, the more this entity will resist translation.

Parameters

number value – the linear damping factor

↑ Back to top

setLinearFactor(x, y, z)

Sets the “position factor” of the object. This determines how the physics engine affects specific linear/position axes. For instance of x=0, the physics engine will not calculate physics for that axis. If x=2.0, it will calculate physics magnified by 2.

Parameters

number x – the x component of the new linear factor
number y – the y component of the new linear factor
number z – the z component of the new linear factor

↑ Back to top

setLinearVelocity(x, y, z)

Sets the linear velocity of the entity.

Parameters

number x – the x component of the new linear velocity
number y – the y component of the new linear velocity
number z – the z component of the new linear velocity

↑ Back to top

setMass(value)

Sets the mass of the entity. A mass of 0 will not be affected by gravity.

Parameters

number value – the new mass of the entity

↑ Back to top

setMesh(mesh)

Sets the mesh of the collision shape from a MeshModel script attribute.

Parameters

MeshModel mesh – the new mesh for the collision shape

↑ Back to top

setMesh(name)

Sets the mesh of the collision shape based on the name of the mesh.

Parameters

string name – the new mesh for the collision shape

↑ Back to top

setPhysics(value)

Enables/disables physics.

Parameters

boolean value – true to enable physics, false to disable

↑ Back to top

setRestitution(value)

Sets the “Bounce” value of the physics component. The higher the value, the higher the bounce upon collision.

Parameters

number value – the new “Bounce” value

↑ Back to top

setShapePosition(x, y, z)

Sets the collision shape position of the object. Note: you must call rebuildShape() after calling this for the change to be reflected in game.

Parameters

number x – the x component of the new shape position
number y – the y component of the new shape position
number z – the z component of the new shape position

↑ Back to top

setShapeRotation(x, y, z)

Sets the collision shape rotation of the object. Note: you must call rebuildShape() after calling this for the change to be reflected in game.

Parameters

number x – the x component of the new shape rotation
number y – the y component of the new shape rotation
number z – the z component of the new shape rotation

↑ Back to top

setShapeScale(x, y, z)

Sets the collision shape scale of the object. Note: you must call rebuildShape() after calling this for the change to be reflected in game.

Parameters

number x – the x component of the new shape scale
number y – the y component of the new shape scale
number z – the z component of the new shape scale

↑ Back to top

setShapeType(type)

Sets the shape type. Highly recommended to use “kHullShape” over “kMeshShape”.

Parameters

string type – Possible values: “kCubeShape”, “kSphereShape”, “kCylinderShape”, “kHullShape”, “kMeshShape”.

↑ Back to top

setType(value)

Sets the type of the physics body.
kStatic – body is static and will never be moved but other objects can collide with it. Used for ground or walls in your game.
kDynamic – body is fully dynamic and can bounce off of other object and be affected by gravity.
kKinematic – body can be moved by directly setting position and rotation and will not react to other bodies collision or gravity. Used as obstacles or elevator platforms.
kNone – no physics enabled

Parameters

string type – Possible values: kStatic, kDynamic, kKinematic, kNone

↑ Back to top

shapePosition()

Returns the position of the collision shape.

Returns

Vec3 the {x, y, z} position of the collision shape

↑ Back to top

shapeRotation()

Returns the rotation of the collision shape.

Returns

Vec3 the {x, y, z} rotation of the collision shape

↑ Back to top

shapeScale()

Returns the scale of the collision shape.

Returns

Vec3 the {x, y, z} scale of the collision shape

↑ Back to top

shapeType()

Returns the shape type of the collision shape.

Returns

string Possible values: “kCubeShape”, “kSphereShape”, “kCylinderShape”, “kHullShape”, “kMeshShape”.

↑ Back to top

type()

Returns the type of the physics body. kStatic – body is static and will never be moved but other objects can collide with it. Used for ground or walls in your game.
kDynamic – body is fully dynamic and can bounce off of other object and be affected by gravity.
kKinematic – body can be moved by directly setting position and rotation and will not react to other bodies collision or gravity. Used as obstacles or elevator platforms.
kNone – no physics enabled

Returns

string Possible values: kStatic, kDynamic, kKinematic, kNone

let ph = this.entity().physics();
if(ph && ph.type() == 'kDynamic'){
  //Dynamic mode
}else{
  //Static or Kinematic mode
}

↑ Back to top

Did you find this page useful?

Please give it a rating:

July 16, 2020

0

Haptic Feedback Node – Buildbox 3 Manual

By Justin Leon |

Haptic Feedback Node

This action node activates a low or high vibration level on a mobile device.

This node contains two inputs that control different levels of the device vibration:

Low—activates a quick and light vibration.
High—activates a longer and more intense vibration.

If needed, type a custom name for this node in the name attribute.

October 13, 2019

0

Is Touched Node – Buildbox 3 Manual

By Elena Torres |

Is Touched Node

This control node activates at the precise moment when the user clicks the screen with a mouse or touches the screen with a finger.

Option	Description
Name	Type a custom name for this node, if needed.
Mode	AABB—Axis Aligned Bounding Box refers to the invisible bounding box on the screen that surrounds the asset and allows players to tap or click to activate the Touched output. Raycast—allows the player to tap or click the asset’s collision shape to activate the Touched output.
Send On Click	Select to allow the player to click or tap the asset.
Send On Move	Select to allow the player to drag across the screen and over the asset.

If needed, you can also customize this node. For details, see Customizing Nodes.

October 18, 2019

0

Camera Shake Node – Buildbox 3 Manual

By Justin Leon |

Camera Shake Node

This action node applies a continuous shake to the camera.

Option	Description
Name	Type a custom name for this node, if needed.
Speed	A numeric value that specifies how quickly the camera will shake.
Range	A numeric value that specifies how wide of a movement or rotation the shake will have.
Duration	Enter how long (in seconds) you want the camera to shake.
Position Shake	If checked, the shake will affect the camera’s position.
Rotation Shake	If checked, the shake will affect the camera’s rotation.
Reset on disable	If checked, the camera will revert back to its default position once the shake has been disabled.

If needed, you can also customize this node. For details, see Customizing Nodes.

October 14, 2019

0

Wave Node – Buildbox 3 Manual

By Justin Leon |

Wave Node

This movement node applies a continuous wave motion to the asset, which shifts in the specified direction and then returns to the point of origin at a consistent speed.

Name

Creates a custom name for this specific node.

Wave Speed

Enter a numeric value to specify the rate of motion. A higher number will result in the asset moving faster along each axis.

Enter a value in any of the range fields on the right to make the asset pick a random value.

The range value is both added and subtracted to create a minimum and maximum of possible outcomes.
For example, if you enter a value of 100 in the Wave Speed field and 50 in its range value field, a value between 50 and 150 will be selected during gameplay.
|50———-100———-150|

Wave Vector

Enter numeric values to specify the motion direction and distance along the axes.

Enter a value in any of the range fields on the right to make the asset pick a random value.

If needed, you can also customize this node. For details, see Customizing Nodes.

October 14, 2019

0

Jump Node – Buildbox 3 Manual

By Justin Leon |

Jump Node

This movement node launches a dynamic asset in a specified direction. See also Making Characters Jump.

This node requires the asset’s physics to be set to Dynamic.

Option	Description
Name	Type a custom name for this node, if needed.
Jump Force	Enter a numeric positive value in the Y axis field to change the jump height of the asset. Enter a numeric value in the X and Z axis fields to launch the asset in a specified direction. To make the Jump Force not affect a direction, delete the value in the axis fields until it displays none. Range values Enter a value in any of the range fields on the right to make the asset pick a random axis value. The range value is both added and subtracted to create a minimum and maximum of possible outcomes. For example, if you enter a value of 100 in the Y axis field and 50 in its range value field, a value between 50 and 150 will be selected during gameplay. \|50———-100———-150\|
Jump Limit	Enter the amount of times an asset is allowed to jump. The Reset input will reset the amount of times this asset has jumped.

If needed, you can also customize this node. For details, see Customizing Nodes.

April 8, 2020

0

Jump Brainbox – Buildbox 3 Manual

By Justin Leon |

Jump Brainbox

This physics Brainbox allows the player make an asset jump when they tap or click the screen.

After the player taps the screen, the asset will launch in the direction specified by the Jump Force attribute. After the asset reaches the full height, it will fall with the direction and force of gravity specified in the Gravity attribute of a 3D World.

Brainbox Attributes

After you add this Brainbox to an asset, you need to set the Physics to Dynamic and specify the Jump Force.

Attribute	Description
Jump Force	Enter a numeric positive value in the Y axis field to change the jump height of the asset. Enter a numeric value in the X and Z axis fields to launch the asset in a specified direction. To make the Jump Force not affect a direction, delete the value in the axis fields until it displays none.

Nodes in Brainbox group

After you add this Brainbox to an asset, a Keyboard Button and Jump node is added to the Node Map.