Generally this problem is solved by the corner being a very dangerous place to be, because it opens up longer and more damaging combos or more threatening mixups because they can't backdash away from the attack.  Usually midscreen combos are shorter and less advantageous on knockdown, and midscreen mixups have more counterplay because there's more screen space to use.

Another thing to consider is that being at close range means the offending player has access to their fastest, safest and cancelable normals for more reward on hit or block.  They don't have to play the neutral game anymore.  In fighting games where running away is a powerful strategy it's usually not so that a player can get their back to the wall in the corner, but so that they have sufficient space to be safe from their opponent and be in range to use their pokes.

The truth is I don't know how to say it, but I would like for example, a hypothetical CvS3 to add a Groove inspired by the Darkstalkers saga, because the latter has interesting mechanics, such as when you defeat your opponent, he revives and They move on to the next round, and more like that.

JasonThePhoenix said, February 26, 2024, 08:11:44 am

hitflag = FD                    ;Flags of conditions that move can hit

Have you tried "hitflag = D+"?? D is only for liedown state and + is for being hit when the enemy is in a gethit state (like 5100s) so then you get sure that if the enemy is down, you can hit it with the taunt. Also, just to be sure, add "fall = 1" to the Hitdef so you can be sure the enemy will got down when you hit with this

JasonThePhoenix said, March 28, 2024, 07:41:15 pm

Is the move idea possible in this engine? Should the move's hitbox start faster and last longer if it's supposed to catch grounded foes when they can be hit with OTGs, and aren't getting up invincibly yet?

Ideally the move should end right when the foe is getting up, so this character can't do this AND put out attacks to hit the foe as he's getting up, but this move is inconsistent. Sometimes it works, sometimes it fails to hit, sometimes it works and lets you act again before the foe is up.

I don't see why it wouldn't work. But like PlasmoidThunder mentioned you want to make sure the move CAN hit P2.
Also if you're trying to time a taunt to end based off of P2, I don't see that in your code. You'll need to check P2's state no and maybe anim.

If you're trying to not let P1 do the move a 2nd time while P2 is getting up, you could make a variable to watch when P2 isn't in a hitstate and reset the var to 0. Then the taunt sets it to 1.


But maybe the animation is too short?
I'd make the animation into 2 parts. Extend the hit, and then have the ending animation. You'd change to the end if the move hits or P2 gets up or due to time.

Considering how the only two attacks that can cause a knockdown are both melee attacks, I need to ask: does the character have any projectile attacks?

If not, you should be able to use a targetpoweradd controller (with triggers set up to detect if the enemy is in a liedown state) during the taunt state instead of a hitdef to achieve the intended effect. This has the benefit of not adding additional hitstun or resetting the opponent's hitstates, since you're not using a hitdef. Just make sure you use a variable as a flag that resets when the opponent is not in a knockdown state so you can't continually spam the Taunt to remove more power than intended.

If your character does have projectile moves, are they based on the projectile state controller or are they helper based? If they're the former, you should be able to use the same method as above; if the latter, you'll need to do the same thing, but add in a few complex workarounds to account for each helper projectile. The reason for this is that, when a projectile spawned by the projectile state controller hits an opponent, the root (that is, the player) owns the target, whereas with helper-based projectiles, the helper gains ownership of the target while the root (player) drops it, so using targetpoweradd won't work from the player's states in these situations unless you add in workarounds. This could involve using the targetpoweradd controller from inside the helper states while using trigger redirects to detect if the root (player) is in the taunt state.

JasonThePhoenix said, June 18, 2024, 02:14:08 am

Ikemen-Plus-Master. I don't see a version number anywhere in the program.

i'm sorry, but you have to use Ikemen GO for this.

Try changing the localcoord instead of x and y scale.
About the speed, no idea. Which version of Ikemen are you playing?

Try changing the Juggle = 1 to 0?
The givepower at -1000 might also be an issue? Like if P2 only has 400, mugen might not allow it to happen?

attr = S, NA     ; you might want to make it a special or a hyper?

Try changing the givepower to a smaller number and see if it works more often. Change some of these and keep testing to try and find what's stopping it from working. Use Ctrl+D and C to see the stuff too.

None of that will make a difference.

It's likely a juggle issue and/or the opponent becoming invulnerable; you can check the latter by viewing collisions with Ctrl+C, which will be cyan if they're inv.

Why is there talk for a frame data page if the character is unfinished? I think the focus should be on more important things, like how to fix infinites and stuff...
speaking of, after you used Burst (which doesn't make the enemy fall down), if you get cornered and get hit by a x,x (wait a bit) x,x etc. combo you can be defeated by an infinite.
Also yes, damage output is too high. And velocities are inconsistent, walking speed is too high and the jumps are too slow.

The Database has a strict uniform layout that doesn't include frame data, so not there either. It would be documented as a Kung Fu Man edit regardless, not its own character.

Dustloop, Supercombo, Mizuumi, etc. document actual games, not random MUGEN characters. You'll need to make your own resource for that.

use mediafire

Would probably help if the link wasn't dead.

Okay, now this is a funny concept for a joke character.