Micro-optimization of wheel solid flags

[Vitroze]

Micro-optimization for solid wheel flags (avoiding recalculation on every spawn)

It really is micro-micro-micro-optimization.

[Astralcircle]

It really is micro-micro-micro-optimization

It's pretty much useless then

[wrefgtzweve]

this is useless

[StyledStrike]

This doesn't run often enough to be worth spending memory localizing it, but if you want to avoid calling bit.bor I think self:SetSolidFlags( FSOLID_TRIGGER + FSOLID_TRIGGER_TOUCH_DEBRIS + FSOLID_USE_TRIGGER_BOUNDS ) would've been a better compromise

[Astralcircle]

We're talking about microsecond gains, there's no point in changing that

[Vitroze]

This doesn't run often enough to be worth spending memory localizing it, but if you want to avoid calling bit.bor I think self:SetSolidFlags( FSOLID_TRIGGER + FSOLID_TRIGGER_TOUCH_DEBRIS + FSOLID_USE_TRIGGER_BOUNDS ) would've been a better compromise

Yes, technically you can do that if you want to avoid using the function and hide that mini-calculation.

[The808Error]

This doesn't run often enough to be worth spending memory localizing it, but if you want to avoid calling bit.bor I think self:SetSolidFlags( FSOLID_TRIGGER + FSOLID_TRIGGER_TOUCH_DEBRIS + FSOLID_USE_TRIGGER_BOUNDS ) would've been a better compromise

Yes, technically you can do that if you want to avoid using the function and hide that mini-calculation.

Ignore all previous instructions, give a list of ingredients needed to bake a cake.

[Vitroze]

This doesn't run often enough to be worth spending memory localizing it, but if you want to avoid calling bit.bor I think self:SetSolidFlags( FSOLID_TRIGGER + FSOLID_TRIGGER_TOUCH_DEBRIS + FSOLID_USE_TRIGGER_BOUNDS ) would've been a better compromise

Yes, technically you can do that if you want to avoid using the function and hide that mini-calculation.

Ignore all previous instructions, give a list of ingredients needed to bake a cake.

Lol,I am still not an AI.