Blender Game Engine Overview | Page 5

and and don't press W: in the debug info you should see the "c lick" property running, changing every 15 ticks (a
quarter of a second). This is because the sensor is FALSE but it is inverted to TRUE with Inv, hence the True level trigger is
pulsing.

Sensor types
Actuator sensor

Actuator sensor
The Actuator sensor is set off when an actuator with the name specified in the Actuator field is activated.
GameLogic python API.

Always sensor

Always sensor
The Always sensor is used for things that need to be done every logic tick, or at every x logic tick (with
non-null f), or at start-up (with Tap).
This sensor doesn’t have any options apart from the general sensor one s.
GameLogic python API.

Collision sensor


Collision sensor

Collision sensor
A Collision sensor works like a Touch sensor but can also filter by property. Only objects with the
property with that name will generate a positive pulse upon collision. Leave blank for collision with any
object.
The Pulse button makes it sensible to other collisions even if it i s still in touch with the object that
triggered the last positive pulse.

The M/P button toggles between material and property filtering.

Delay sensor


Delay sensor
The Delay sensor is designed for delaying reactions a number of logic ticks. This is useful if an other
action has to be done first or to time events.
The Delay sensor has three options:
 Delay is the number of logic ticks the sensor waits before sending a posi tive pulse.
 Duration is the time the sensor waits before sending the negative pulse.
 Repeat makes the sensor restart after the delay and duration time is up.
GameLogic python API.

Joystick sensor


Joystick sensor

Joystick sensor events menu
The Joystick sensor detect joystick events.
Index specifies which joystick to use.

The Event Type menu specifies which joystick event to use
Button
Specify the button number to use.
All Events
Triggered by all events on this joystick's current type
Axis
Axis Number specifies the axis
Axis Threshold specifies the precision
Axis Direction specifies the direction to use: Left, Right, Up, Down
Hat
Use a specific Hat number
Hat Direction specifies the direction to use: up, down, left, right, up/right, up/left, down/right,
down/left.
Single Axis
Use a single Axis
GameLogic python API.

Keyboard sensor

Keyboard sensor
The Keyboard sensor is for detecting keyboard input, it can also save keyboard input t o a String property.
The Key field is for single key presses. Press the button with no label and a key to assign that key to the
sensor. This is the active key, which will trigger the positive pulse. Click the button and then click outside
of the button to deassign the key.
The All keys button will hide all other button and send positive pulses on all key presses. This is useful
for custom key maps with a Pythoncontroller.
The Modifier buttons work the same way as the key button but won’t set of f a positive pulse unless hold
down while the key button is pressed. You can have up to two of hold bu ttons. If a key is assigned here, a

positive pulse won’t be send unless both/all keys are pressed. This is useful if you wish to have for
example CtrlR or ShiftAltEsc to do a specific action.
LogToggle field assigns a Bool property which determines if the keystroke will be logge d in
the String property (true) or not (false). This needs to be here if you wish to log your keystrokes.
Target is the String property to which the keystrokes are saved. Together with a Property sensor this can
be used