Glitch of LBA2 that unlocks an alternate end, the bad end.

[XXStranger]

Did anyone know of this LBA2 bug? It is about unlocking the Final Bad in which the Moon destroys Twinsun using a bug that is activated by placing a Nitro Mecha Penguin just when we are going to activate the end of the game.

Here I leave a video:

YouTube

I'm sorry I can not put it in the bugs post but I have no permission to write there.

[Necdilzor]

That's really odd. I think the meka penguin is the most evil character in LBA haha
It's very nice that you found out about it, I definitely haven't seen it before.

[gravel22]

That is actually really funny

[Floppy]

Schrödinger's planet

[kash]

It's the superposition principle; the game is completed and failed a the same time like in Schrödinger's cat paradox where the cat is both alive and dead until someone opens the box.

[Floppy]

Yep, that's it. Thank you kash!

[Zink]

Originally Posted by MrQuetch

I'm surprised the game checks for whether you're alive or not, it shouldn't care now that the game has been beaten by the player. Most games simply would not care anymore.

I think this is because the scene of reunion with Zeelichians is made as a regular Scene, so the engine still works in full, and checks for Twinsen's life amount. To make the game ignore Twinsen's life after certain point, they would have to make some engine hack for just one scene. Or a special script command/game flag. It's obvious noone supposed you could get to that scene with zero life points, so they didn't bother.

Originally Posted by MrQuetch

It's interesting that someone finally mentions something I did years ago. Quite cool though. I'm sorry you guys didn't know about it. Yup, very strange bug.

It's interesting someone mentioned my video of it, and asked if MBN knew about it, despite the fact that the video mentions the MBN, and that you have found the bug

[Lightwing]

This made me laugh out loud at work!

Looks like they had two types of event triggers for the end scene which were independent of each other. The "location" trigger which checks if you've beaten FF and assumes you're alive if you're standing on spot X. And a "zero health bar" trigger, which actually checks your health status before activating a cutscene. However, the bad cutscene plays after "Twinsen falls to the ground" animation finishes, while the good cutscene plays immediately. Hence the order of cutscenes.

Good lesson in programming. You should never have two independent triggers for a single decision point. Still funny though.

[Polaris]

Nice performance

[Homeless]

Originally Posted by MrQuetch

We know that Fred is a far better programmer than this, but why? It must've been one of the other scripters using his tools. Yeah, it is a very strange problem to have.

Pshaw! Always blaming the little guy.

Seriously though, this is hilarious. Great find.