Manual override of the failsafe check on win and time-over poses. #2890
Unanswered
Orochikyocr
asked this question in
Feature Request
Replies: 2 comments
-
|
As it is supposed to work. 2025-11-17.17-14-50.mp4Stuck at custom stateno or in state 0, but after being redirected from custom state. 2025-11-17.17-09-25.mp4 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm not sure if it's what's needed for this particular case, but I'll add a parameter to unhardcode that delay in my next PR, since we're always unhardcoding things anyway. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
https://discord.com/channels/233345562261323776/282927929548210177/1440115514528764055
Im been porting SVP to Ikemen Go, but instead of the custom Winscreen that comes with it (it does not work anyway), I wanted to use the Ikemen Go native winscreen.
I was able to take off all those helpers related to the custom WinScreen, but Ikemen Go's win screen takes up to 20 seconds to show up after the match is over. Meanwhile, you get a fading white screen(a visual effect emulating the KOF 2002 white screen on matchover K.O.)
Only after the failsafe check activates the character winpose, the win screen appears after 2 or 3 seconds more.
Took me two days, like 12 hours, just to realize what was happening.
Ikemen Go or neither Mugen likes to be interrupted with changestate sctrls during roundstate 3 that send the character to the expected state numbers in those circumstances (state 0, state 180). Even if you manually set the character to state 0 or state 180, you must wait 15 seconds.
Describe the solution you'd like
An option in config.ini to manually override those 15 seconds of the failsafe check for the Winpose.
Additional context
Many characters have issues at the round and match endings. I know, probably badly coded, but what can one do?
Managing this timer could help those with builds with many badly coded but unique characters that get stuck in roundstate -3.
In my case, this is not bad coding; they broke roundstate -3 on purpose, despite roundnotover existing since Winmugen, to have time to show their custom winscreen.
As I said, I spent two days on this, although this project is just for my friend and me to have fun with this full game.
Search terms
No response
Beta Was this translation helpful? Give feedback.
All reactions