United StatesNo idea how this one works. It just happened when kept trying to jump up again. Of course it does not compare to that Bow glitch, but might as well post it.
Got a hilariously bugged damage bug with Large Sword. Destroyed Amon and the final boss. Use Large Sword's special attack (forward forward Attack) while getting hurt, but take damage while the special move is happening. Thinking this is because the invincibility wearing off messes with the move so the game still thinks you are using the move. You can use Fast Travel and it stays on. Die or reload and it goes away. You can even switch weapons and it stays on.
Well let me know if you are just going to use the longer video, or if you are creating a new video. Then I can review whichever.
If this is the same run you could use this. This does not have the video dropping that final section.
Were there any game crashes or game freezes where you had to restart a section?
Also what happened to the end of the video? There was a break there. Could you please include that?
removing softlock time to get you back to that spot you reloaded at.
17:11
18:04
53 seconds remove
= 1h 25m 39s
Hello! Could you give me timestamps for the locations of the soft locks? I noticed one around 17:20.
Due to the game having lots of softlocks on console and in the sake of fairness since PC version seems to not have softlocks anymore, the rules were modified to discount the time loss from those softlocks. Please list the timestamps for the softlocks!
Thanks! The game is extremely random and the opponents do some hard core input reading so not sure if these strats are even really viable for rta. Although some opponents do seem more aggressive than others like the final normal opponent Kayin. Duke is probably a good ring out candidate since his homing move kind of dooms him if he does it. I guess an RTA player would have to test to see if any of these strats commonly occur for these ring outs.
updated time
0:52 start
1:51:28
so without taking out the softlocks
1:50:36
remove 5:23
1:45:13
now add 20 seconds penalty for starting on 1-1
1:45:33
Great run!
Yea the second option with adding 20 seconds for those that start on 1-1 sounds better since the intro really is the beginning of the game.
For the softlock thinking about it more it really should be discounted. If for PC players they do not get softlocks yet console players do, it creates a time disparity and a sense of exclusion if they have to pay double for the game and the character completely upgraded on PC just to avoid softlocks. Furthermore, counting random softlocks against a runner would serve as a disincentive to speedrun the game. If this game was much much shorter and the softlocks less frequent it would be fine. But each final attempt is going to be over an hour long and for slower players nearly 2 hours. However I do remember what it was like before the updates where I would get at LEAST 1 softlock every single time. So for the sake of getting more people to even want to play the game, and as a sense of fairness I will be discounting softlock times.
So in light of that where is the softlock timestamp you encountered?
Thankfully with the new updates those softlocks went away for me on PC. See if there is a recent update you can get.
This looks very good, but there is one thing we should talk about. I had been assuming the game would be started from the beginning meaning the Intro, but you start on 1-1.
In the rules there is:
"Time begins on pressing on start of Intro level on Menu. Timing ends on start of credits. Single Segments only for this category."
However, realistically anyone running this game has beaten this game already and will not be on a fresh save so starting on 1-1 makes sense. But for those that actually want to start on the Intro to actually start at the beginning would be at a time disadvantage to those that start on 1-1.
I want to accept your run so maybe there are some adjustments or something we can do with the times. Do you have any thoughts on this? I could think we could remove the intro from the time currently, or maybe show two times. Thoughts?
In addition could you give me a timestamp where the softlock happens? I am thinking for softlocks we leave in the softlock video recorded evidence, but just remove the lost time as though the softlock or crash (if a crash happens) never occurred. Then no one would have to stress about something like that with this soft lock prone game.
There is some good extra info I posted on the game over there in the description for the submission.
While some planes are great for certain areas, I would like to try others. Is this even possible?
Does it mean all levels or what?
What does this error even mean and why is this relevant to speedrun.com?
Those large hives are incredibly vulnerable to mines which is strange. Makes for one extremely short mission and helps with the final mission.
