Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
In the meantime, I believe a simple workaround is to have your loner command followed by a clearmove (which clears all movement bitflags, no other properties). That seems to get rid of the problem, the unwanted movement bitflag 29.
After that, you can (again) set whatever movement bitflags you want, using those movement mod commands that don’t take arguments (i.e. excluding the commands trample and tramplexsize which add "effects" – i.e. integer pairs – to the monster definition rather than setting any bitflags there).