The Computer Crisis (Stupid-ass internal scripting test)

[ToasterApocalypse]

So, Vitellary has really done it this time, when he builds a computer to keep his lab safe. But this computer is a little too overprotective and denies access to everyone, including it's creator!

So now you, because you are, well, you, will go on a journey (Go through a space station and a lab) and destroy the computer!(optional for now.)

Oh and, INTERNAL SCRIPTING TEST GUISE

screenshots here




FUN FACT:
The computer boss fight takes up 14 rooms, most of them for the intro.

I just beat the fragment with 13 deaths
woop

[Bearboy]

when i start, viridian and victoria are unhappy. victoria walks in, then out, then viridian teleports.
wut

[ToasterApocalypse]

when i start, viridian and victoria are unhappy. victoria walks in, then out, then viridian teleports.
wut

ogm is ur mind ded yet

mien die at start

EDIT: Crap, I forgot to fix a few things (Blue text at miniboss, red text at end of computer boss)
I'll fix those and re-release.

OTHER EDIT: Yay fixed

[FIQ]

Just a FYI

Your method of executing internal scripts (by using say() with numbers over 5 - i.e. in boss1phase3end) will make the level only work in 2.1

[ToasterApocalypse]

Just a FYI

Your method of executing internal scripts (by using say() with numbers over 5 - i.e. in boss1phase3end) will make the level only work in 2.1

I don't know how to do it any other way so... yeah

[Dav999]

Confirmed: it doesn't work with 2.0. All you get is a text box with
position(center)
speak_active
squeak(terminal)
text(gray,0,114,33)
Then you get a couple of flashes, and if you walk left, you fall down and end up in a wall. So... 

To make it compatible with 2.0, you should use

Code Select Expand

say(-1)
text(1,0,0,4)
say(5)
(internal)
(internal)
(internal)
(internal)
text(1,0,0,4)
say(5)
(internal)
(internal)
(internal)
(internal)
text(1,0,0,4)
say(5)
etc.

Or something like that.

[Pyrite]

WHY IS THERE ONLY ONE CHECKPOINT IN ENEMY APPROACHES. I CAN'T LAND ON A TWO-BLOCK TERMINAL FROM A MOVING PLATFORM. I won.

[FIQ]

There's some really narrow platforms here and there and places that the slighest fail will make you die, which make the level both hard (which is OK), but also frustrating.

It was interesting thought, and I liked the idea!

[blue626]

To make it compatible with 2.0, you should use

Code Select Expand

say(-1)
text(1,0,0,4)
say(5)
(internal)
(internal)
(internal)
(internal)
text(1,0,0,4)
say(5)
(internal)
(internal)
(internal)
(internal)
text(1,0,0,4)
say(5)
etc.

Or something like that.

You could also use this code that someone found about a year ago and that I already mentioned before: VVVVVV's most POWERFUL script?. I'm not sure if it works in this case, though.

[Dav999]

To make it compatible with 2.0, you should use

Code Select Expand

say(-1)
text(1,0,0,4)
say(5)
(internal)
(internal)
(internal)
(internal)
text(1,0,0,4)
say(5)
(internal)
(internal)
(internal)
(internal)
text(1,0,0,4)
say(5)
etc.

Or something like that.

You could also use this code that someone found about a year ago and that I already mentioned before: VVVVVV's most POWERFUL script?. I'm not sure if it works in this case, though.

But then it ONLY works with 2.0, because say(6) messes up the parser in 2.0, but 2.1 users will just see a text box with six lines of code.

[avengah]

This crashes for me as soon as I use the terminal that would take off the computer boss's last piece of health. I'm using 2.1 final. I looked at the script and couldn't see why it'd crash (although say(46) is quite a high number, but other high valued say commands worked fine up to that point)...

[Hilbert]

...

[Hilbert]

... ...

[avengah]

I tried fixing it myself but I don't know much about internal scripting. I can say this, though: I changed the say(46) to say(45) and removed the play(16) command. Result: Instead of quitting instantly, I got a runtime error box and then it quit.

[Dav999]

Result: Instead of quitting instantly, I got a runtime error box and then it quit.

Progress!