An error occurs when the number of enemies is more than 3 in tag mode

[netyzh]

Describe the bug

After defeating the first enemy, when you continue to attack the second one, some character's attack will lack hit sparks, and some moves will go awry.
It seems the problem happens when use codes enemy(0) and enemy(1).
However, versions in 0.99 or before the appearance of that config.ini should be normal.

To Reproduce

Character:https://www.mediafire.com/file/l1lsio682s0w8xl/Youmu.rar/file
Start a team versus
2p choose tag mode and select 4 character
Press 22d*2,do some damage,and press 26d to defeat first one
Continue to attack the second enemy.

Expected behavior

No response

Screenshots / Video

2025-02-04_13-38-17_x264.mp4

Engine Version (or source code date)

nightly

Operating system

Windows

Extra context or search terms

No response

[potsmugen]

The char is hardcoded to play against 1 or 2 enemies. I'm surprised it worked before because this needs engine workarounds in several places to work. But even with those workarounds it did not work in the expanded Simul mode, which shows how much of a losing battle it is to do those.

It's an issue similar to #2238 and I maintain what I said there.

To fix the char you need to expand the limit of 2 enemies. That means replace:

• NumEnemy = 2 with NumEnemy >= 2
• Enemy(0) with EnemyNear(0)
• Enemy(1) with EnemyNear(1)

It will still work in Mugen all the same.

[netyzh]

Problem in #2238 also works well in previous version.
I think if we should handle the code for "enemy" and "enemynear" separately?The tag mode uses the code from previous versions, while the simul mode uses the current code. Would it solve the problem without requiring any changes to the character's own code?

[potsmugen]

For this character, that would solve Tag but not Simul. But doesn't it sound confusing just to think about that? The priority should be having an engine that makes sense rather than one where no Mugen character needs to be modified under any circumstances, in my opinion.

[netyzh]

At least we can try to handle the part of #2238 better. This issue still seems to exist, and it cannot be simply resolved by modifying the character's code.Unless directly avoid using helpers to handle variables,this change can be significant or minor.

[potsmugen]

it cannot be simply resolved by modifying the character's code

Most things can. It's probably some variation of what I said above, if not the same. I can take a closer look if you want.