llCollisionFilter

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

CollisionFilter

llCollisionFilter

Summary

Function: llCollisionFilter( string name, key id, integer accept );

110	Function ID
0.0	Forced Delay
10.0	Energy

Sets the collision filter, exclusively or inclusively.

• string	name	–	filter for specific object name or avatar legacy name
• key	id	–	filter by group, avatar or object UUID
• integer	accept	–	TRUE only process collisions that match, FALSE instead excludes matches

If accept == TRUE, only accept collisions with objects name AND id (either is optional), otherwise with objects not name AND id
If name or id are blank they are not used to filter incoming messages (or you could say they match everything). If id is an invalid key or a null key, it is considered blank.

Caveats

All Issues ~ Search JIRA for related Bugs

Examples

Stop filtering: <lsl>llCollisionFilter("", NULL_KEY, TRUE);</lsl> Filter out all collisions: <lsl>llCollisionFilter("", NULL_KEY, FALSE);</lsl> This script, placed in a wearable object, detects a collision when the person wearing it collides with an object named "Post":

• 1st instance :

an object named "Post" has several child prims named "Object" . The prim named "Post" hits the scripted object or scripted prim , the collision will be detected

• 2nd instance :

an object named "Post" has several child prims named "Object" . A child prim named "Object" hits the scripted object or scripted prim, the collision will be detected

• 3rd instance :

an object named "Object" has several child prims named "Post" . A prim named "Post" hits the scripted object or scripted prim, the collision will not be detected

<lsl>default {

   state_entry()
   {
       llCollisionFilter("Post","",TRUE);
   }

   collision_start(integer total_number)
   {
       llSay(0, "OUCH!");
   }

}</lsl>

See Also

Events

•	collision_start
•	collision
•	collision_end

Functions

•	llPassCollisions
•	llVolumeDetect

Deep Notes

Search JIRA for related Issues

Signature
function void llCollisionFilter( string name, key id, integer accept );