Skip to content
New issue

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

MM/MO/MU tags #397

Open
katajakasa opened this issue Aug 13, 2021 · 1 comment
Open

MM/MO/MU tags #397

katajakasa opened this issue Aug 13, 2021 · 1 comment
Projects

Comments

@katajakasa
Copy link
Member

katajakasa commented Aug 13, 2021

Find out what these do.

MM selects an animation ID, and then MO/MU operate on that selection. It is possible to chain these, eg. mm16mu1mm22mo etc. MM tag must always be used before using mo/mu.

  • MM takes argument, animation id
  • MO does not take an argument, sets some internal flag. Possibly operates on other HAR ?
  • MU disables the selected animation for then next ticks (<1024).

MO and MU have different behaviors if current animation is DAMAGE type.

@katajakasa katajakasa added this to Todo in Tags Aug 13, 2021
@katajakasa katajakasa moved this from Todo to Manual testing needed in Tags Aug 13, 2021
@katajakasa
Copy link
Member Author

After poking at the MO flag, I couldn't find any effect for it either in binary or by trying the flag. Perhaps it's just not used ? It is anyways only used by chronos, so probably not a priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Tags
Manual testing needed
Development

No branches or pull requests

1 participant