We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have no knowledge of this, so if this is request is unreasonable, feel free to close this.
The MotionTypes currently available:
RULEUMT_Air = {Air = 16}, RULEUMT_Amphibious = LayerCaps[ 3 --[[0x01 | 0x02]] ], RULEUMT_AmphibiousFloating = LayerCaps[ 9 --[[0x01 | 0x08]] ], RULEUMT_Biped = LayerCaps[ 0x01 ], RULEUMT_Land = LayerCaps[ 0x01 ], RULEUMT_Hover = LayerCaps[ 9 --[[0x01 | 0x08]] ], RULEUMT_Water = LayerCaps[ 0x08 ], RULEUMT_SurfacingSub = LayerCaps[ 12 --[[0x04 | 0x08]] ], RULEUMT_None = {Sub = 4, Land = 1, Seabed = 2, Water = 8},
These are defined in the engine and we cannot change them, or add new ones at the moment.
The text was updated successfully, but these errors were encountered:
I'm fairly certain that this is out of scope. How units behave pathing-wise is woven into the engine.
Sorry, something went wrong.
No branches or pull requests
I have no knowledge of this, so if this is request is unreasonable, feel free to close this.
The MotionTypes currently available:
These are defined in the engine and we cannot change them, or add new ones at the moment.
The text was updated successfully, but these errors were encountered: