Author uses the non-final build for the title much like with this other submission... Final version carries this information: SHA1:AAF893AE99D80AAA280ACE408E99313B2140B972 MD5:079F2159449E1F47B94A4BF907203CC4 Author is using: SHA1:68D17036F1EA13330E598B49E57A1E4DF926E2C3 MD5:CE76EA0DE5AEA02136FA42334C97D173 Which is weird considering your wiki comment. There are differences, so every stall that the author does, canprobablybe avoided. Even if the author started the game a frame or two late. Abstained vote, purely from the stalling that the author had to do.
1) You can start the game 5 frames earlier (on frame 352) and clear the intro text faster (on frame 375). This will get into the first stage faster. 2) As you've already mentioned in the submission notes, killing unnecessary enemies adds time to the run due to the end-stage score tally. You kill an unnecessary enemy in stage 1. This can be removed and improve the time. 3) It's not intuitive, but in the Space-Shooter stages shooting actually delays the end of the stage. I'm not sure exactly why this is the case, but I'm guessing that shooting somehow affects the game's autoscroll code. So I'd recommend eliminating all shooting in these stages (except the final one which obviously require shots at the end to finish). 4) There are also a couple places where movement optimization can be improved (jumping over one of the volcanoes in stage 2 for example).
enderpal7. I've come across a couple details that will improve this run. None of them, at this point, would result in rejection. But I wanted to check with you and see if you wanted to implement these things before this submission is fully judged. Specifically: 1) You can start the game 5 frames earlier (on frame 352) and clear the intro text faster (on frame 375). This will get into the first stage faster. 2) As you've already mentioned in the submission notes, killing unnecessary enemies adds time to the run due to the end-stage score tally. You kill an unnecessary enemy in stage 1. This can be removed and improve the time. 3) It's not intuitive, but in the Space-Shooter stages shooting actually delays the end of the stage. I'm not sure exactly why this is the case, but I'm guessing that shooting somehow affects the game's autoscroll code. So I'd recommend eliminating all shooting in these stages (except the final one which obviously require shots at the end to finish). 4) There are also a couple places where movement optimization can be improved (jumping over one of the volcanoes in stage 2 for example). Unfortunately, changing the above stuff will impact movement sync so some movement improvements may not still be valid after resyncing. Hitboxes are weird in this game. Just let me know if you want to update the run before it's judged, or if you want it judged as is.
Thank you so much for taking over from my WIP. This is about as much optimization as I hoped there would be. I just wish I could better understand how those ledge boosts worked.
Just out of curiosity: are the following loops harder? Apparently the enemies move a little faster. (don't worry, this isn't a problem for the acceptability of this submission)
I was watching through this one and noticed stopping to kick the dogs in stage 1. I tested out if it was possible to just jump past them and sure enough I was able to get through. Not sure if this would mess with the timing of other obstacles later in the game, though. User movie #638055139421385179
In the majority of Ghost n Goblins games, constantly jumping is slightly faster than normal running. Do you know if that’s the case in this game too?
