YesNoOk
avatar

Third tag partner (p5/p6) unnaffected by certain custom states (Read 2190 times)

Started by Master0fFaster, April 22, 2025, 09:57:43 pm
Share this topic:
Third tag partner (p5/p6) unnaffected by certain custom states
#1  April 22, 2025, 09:57:43 pm
  • avatar
  • *
As the subject says, I've been testing a bunch of things and, for some unknown reason, a few specific custom states don't seem to be working when the target is the third tag partner, aka p5 and p6.
So far only one character has this problem, but I've removed any code that mentioned any player ID, numpartner, etc. which either did nothing or it disabled the custom state entirely.
This sounds like it'd be a known issue, but I can't seem to find any information about it.
Any ideas of what may be causing this?
Last Edit: April 22, 2025, 10:32:05 pm by Master0fFaster
Re: Third tag partner (p5/p6) unnaffected by certain custom states
#2  April 24, 2025, 04:53:55 am
  • *****
  • Shame on you!
    • USA
vVv Gouken718 vVv
Re: Third tag partner (p5/p6) unnaffected by certain custom states
#3  April 24, 2025, 10:49:07 pm
  • avatar
  • *
Sadly it didn't work. Changed the code according to said technique and it still somehow does the same as when I used p2stateno, P5 and P6 still don't get put into the state.
The triggers being used here are P1's own states and the target's stateno != [150, 155]
Re: Third tag partner (p5/p6) unnaffected by certain custom states
#4  April 24, 2025, 11:48:57 pm
  • avatar
  • *
Nevermind, there were a lot of enemy triggers. The problem is that said "enemy" triggers in the statedef for the custom states don't seem to allow "PlayerID(Var(x))" without completely graying out what it is looking for, namely backedgebodydist and animelement. I've even tried rephrasing the code for P2 instead of enemy but that doesn't seem doable either. Tried enemyNear too, just in case.
Last Edit: April 25, 2025, 12:52:57 am by Master0fFaster
Re: Third tag partner (p5/p6) unnaffected by certain custom states
#5  April 25, 2025, 11:30:13 am
  • ******
    • Portugal
    • network.mugenguild.com/pots/
I assume you're using Ikemen since you're talking about players 5 and 6. There's a very high chance the chars just never accounted for facing more than two enemies. Not that they needed to in Mugen. I think normally this could be solved by replacing "enemy" with "enemynear".

Also you almost gave me a heart attack but I just confirmed that "playerID(var)" is working. At least on a basic level.

You can help with Ikemen GO's development by trying out the latest development build and reporting any bugs on GitHub.
My Mugen and Ikemen content can also be found here.
Re: Third tag partner (p5/p6) unnaffected by certain custom states
#6  April 25, 2025, 12:10:38 pm
  • avatar
  • *
Yeah no, that whole "playerID(var)" works, the problem is that what follows after doesn't go with it. One of the original lines of code is
trigger1 = enemy(prevstateno%10),animelem = 12, >= 0
And as I said, i've tried changing "enemy(prevstateno%10)" to "enemyNear" and to "playerID(var(X))", enemyNear changing nothing and playerID seemingly being completely incompatible with the rest of the line

And yeah, It is Ikemen, wasn't too aware of how far the differences between the two go