Defining new collision constants/types?

[Pastaspace]

When it comes to collision types, you have all your basic ones, Prop, Scene, Character, Trigger, Debris, Projectile, LineOfSight, etc.

However, is it possible to define additional collision types, other than the defaults, and add them to the big table of existing collision types? If so, how?

[macklebee]

List of inherent types:

Collision.Prop = 1

Collision.Scene = 2

Collision.Character = 3

Collision.Trigger = 4

Collision.Debris = 5

Collision.Projectile = 6

Collision.LineOfSight = 7

 

List of possible responses:

Collision.None = 0

Collision.Collide = 1

Collision.Trigger = 4

 

With the following warning from Josh concerning using the constants and not the numerical values: "You really should stick to using the named constants. Technically, the values of these are allowed to change at any time, without breaking the spec."

 

Example of use in LUA:

Collision:SetResponse(type, type, response)

entity:SetCollisionType(type)

Collision:SetResponse(10, Collision.Character, Collision.Trigger)

Collision:SetResponse(10, Collision.Prop, Collision.Trigger)

self.entity:SetCollisionType(10)

[Roland]

It would be a good idea if Josh added a Collsion.User = 100 or something.

That way he could have he's own stuff below 100 and the users could have their over 100

 

Same goes for the Collsion.Trigger

[Aaron Symons]

Can we collide two triggers together using this? I attempted to do so without luck. I'm probably missing something.