Some MUGEN characters specify multiple command inputs for a move like this:
[State -1, Multiple Moves via &&]
type = ChangeState
triggerall = command = "x" && command = "y"
However, Iguana can only parse the first statement and ignores everything afterwards:
Found move: {Multiple Moves via && [command="x"&&command="y"]}
...
Reading move: Multiple Moves via &&
Tokenizing string: x
Tokenized: x
One solution would be to internally split trigger strings using && as a delimiter. Problem is the current control flow of scrape_moves() doesn't really have an obvious place to slip that in, so a slight refactor might be needed first.
Some MUGEN characters specify multiple command inputs for a move like this:
However, Iguana can only parse the first statement and ignores everything afterwards:
One solution would be to internally split trigger strings using
&&as a delimiter. Problem is the current control flow ofscrape_moves()doesn't really have an obvious place to slip that in, so a slight refactor might be needed first.