Instead of e-mailing it to nate (dunno if he's still here), why not send it here?
"I thought a couple theories:
1: The Charge + Move-Jump might cause to push him into part of the wall, by a pixel, causing him to freeze.
2: Getting hit by a Charge + Move-Jump beam, and hitting the player possibly freezes him.
3: Being in the spot where he instantly gets jump-charged, causing him to hit the player, and getting shot, making the boss, or mini-boss supposedly think he's hurt, causing a loop in the process, stopping him from moving, or something like that.
4: Somehow, when samus gets hit by the enemy, her charge beam hits forward, and also pushing her back. When that happened, it caused Imago to think something was blocking him, causing him the freeze, like a collision. More than two beams hit him, aswell as other things hit, causing the sprite to overload, freezing him.
I'm gonna give more detail to #3:
Now, my guess what, that by using the arrow keys to find out by each frame, i saw him jump with a charged blast, making the enemy think he made it to both edges. By some bug, caused in many of em, it causes the enemy to loop it's actions, like saying it thinks it's dead, or something. It probably thinks it is either dead, or made it to the right hole, causing him to loop his normal action, but not move. This is another part of my theory. These are theories on how the glitch happens, so i might be wrong, or right. I cannot know.
Sorry, but this is actually fascinating how this glitch happened from the movie. It's quite difficult looking, but if my theories are correct, then heck, i found out how the glitch works."
I was pretty fascinated how this glitch happened, so i clicked the quicktime thing and used the arrow keys to see frame by frame.
~Hug
"I thought a couple theories:
1: The Charge + Move-Jump might cause to push him into part of the wall, by a pixel, causing him to freeze.
2: Getting hit by a Charge + Move-Jump beam, and hitting the player possibly freezes him.
3: Being in the spot where he instantly gets jump-charged, causing him to hit the player, and getting shot, making the boss, or mini-boss supposedly think he's hurt, causing a loop in the process, stopping him from moving, or something like that.
4: Somehow, when samus gets hit by the enemy, her charge beam hits forward, and also pushing her back. When that happened, it caused Imago to think something was blocking him, causing him the freeze, like a collision. More than two beams hit him, aswell as other things hit, causing the sprite to overload, freezing him.
I'm gonna give more detail to #3:
Now, my guess what, that by using the arrow keys to find out by each frame, i saw him jump with a charged blast, making the enemy think he made it to both edges. By some bug, caused in many of em, it causes the enemy to loop it's actions, like saying it thinks it's dead, or something. It probably thinks it is either dead, or made it to the right hole, causing him to loop his normal action, but not move. This is another part of my theory. These are theories on how the glitch happens, so i might be wrong, or right. I cannot know.
Sorry, but this is actually fascinating how this glitch happened from the movie. It's quite difficult looking, but if my theories are correct, then heck, i found out how the glitch works."
I was pretty fascinated how this glitch happened, so i clicked the quicktime thing and used the arrow keys to see frame by frame.
~Hug
Thread title: