Character Contacts

Consumes rigid-body and character-to-character contact events generated by the managed controller.

The native bridge records Added, Persisted, and Removed events. jolt_update() drains them into fresh world and per-character arrays after all fixed steps have completed.

Event types#

Body contacts#

var contacts = player.get_contacts();
for (var i = 0; i < array_length(contacts); ++i) {
    var hit = contacts[i];
    show_debug_message(hit.entity);
}

Character-to-character contacts#

player.set_character_collision_mode(JOLT_CHARACTER_PUSH);
player.set_character_push_strength(50);

var pairs = player.get_character_contacts();

Layer-pair policy#

jolt_character_layers_set_mode(player_layer, enemy_layer, JOLT_CHARACTER_BLOCK);

The per-character modes and the symmetric layer-pair rule are resolved together. Both layers must belong to the same live world. Character collision processing is a serial brute-force list in the current implementation.

Transient pair events#

player.character_contact_entered()
player.character_contact_exited()
player.clear_contacts()
player.clear_character_contacts()
player.get_dropped_contact_count()

The managed arrays are replaced by the next jolt_update(). Copy any event data you need to retain.

Layers, readback and world diagnostics#

// Read after the central physics update.
var pairs = jolt_get_character_contacts();
var dropped = jolt_get_dropped_character_contact_count();
if (dropped > 0) show_debug_message("Character contact overflow: " + string(dropped));

The global pair array is not the per-character rigid-body contact array from player.get_contacts(). Treat event arrays as update snapshots and process them before the next update replaces them.

Verified operation contracts#

These contracts distinguish units, return values, errors and lifetime according to the current implementation. Check results: false, 0 and undefined can mean different things for different methods.