Difference between FxBrickAlwaysObjectType and FxBrickObjectType?

[Lugnut]

^subject

i'm referring to typemasks, btw.

[Ad Bot]

[elm]

I think it has to do with rendering, and stuff like that. AlwaysObjectType will be even non rendering bricks as the other one will be brick that are rendered. Someone correct me if i am wrong.

[Ipquarx]

I'm not sure, but I would use the always type just in case :p

[Chrono]

always doesn't care if the brick is fakekilled or not
other one only works if the brick isn't fakekilled

[Nitramtj]

More specifically, FxBrickAlwaysObjectType will detect bricks with raycasting disabled, while FxBrickObjectType will only detect those with raycasting enabled.

[Treynolds416]

More specifically, FxBrickAlwaysObjectType will detect bricks with raycasting disabled, while FxBrickObjectType will only detect those with raycasting enabled.

You beat me by literally a second with almost the exact same statement :(

[jes00]

Well this is useful information. I didn't know the difference before so I just used them both.

[Mold]

What do you use them for btw?

[jes00]

What do you use them for btw?

Raycasts.

[Headcrab Zombie]

Raycasts.

And container searches

[Xalos]

And container searches

Strictly speaking, the container raycast is a container search, it's just that it's a... cast ray.