PRO INVIGILATOR 2012
Are you a bad enough dude to stand calmly around for an extended period of time?
PROVE IT with PRO INVIGILATOR 2012.
Controls: Arrow Keys
Break line-of-sight between cheating students quickly for high score!
You are a hillbilly in an elevator. Shoot your opponent with the SHIFT key. Taunt your opponent with the SPACE BAR.
Points are earned while taunting. Defeat your opponent before they shoot you.
Created in about 2.5 hours for the Pirate Kart 5. Inspired by a name generated with the Video Game Name Generator. Sounds created with the AT&T text-to-speech website app.
Thanks for playing!
I just played through Electric Highways by Zykoveddy and I'm trying to put my thoughts together on it.
If anyone else happens to play it, let's discuss!
Cross the minefield as many times as possible for a high score!
The desert is the best labyrinth.
Oh look, I've gone and done a Star Soldier styled game engine.
It's pretty easy to destroy all of the targets but it's not really supposed to be a challenging game.
Use all the letter keys except z to leap about and collect yellow dots ...
As you know, one of the most prominent difficulties with mixing code and prose in Twine games is the handling of line breaks. If you have a bunch of macros interspersed in your prose, especially
<<if>> macros, then the temptation is to leave them on separate lines from the text, for readability. However, the line breaks adjacent to these macros end up appearing in the rendered passage.
<<silently>> macro is the 'official' solution...
<<silently>> <<set $hp -= 1>> <<set $dead = true>> <<endsilently>>Wrap up all of the macros in it and the line breaks will be suppressed. But, it seems to me to be a half-effective solution, requiring two large macro tags enclosing each block, and disallowing
<<print>>macros within it.
I've previously advocated a different solution, involving the TiddlyWiki comment syntax:
/% %/<<set $hp -= 1>>/% %/<<set $dead = true>>/% %/This has the advantage of allowing the use of
<<print>>macros. But it, too, is authorially and visually unwieldy, requiring both the end and beginning of lines to be tagged with one of two similar-looking tags.
However, I believe it's on the right track. Right now, my proposal is to directly borrow the syntax of the C language's preprocessor - a single backslash at the end of a line suppresses the line break:
<<set $hp -= 1>>\ <<set $dead = true>>\ You are \ <<if $hp gt 1>> hale <<else>> almost dead <<endif>>.In my opinion, this has much more convenience compared to the other two.
Obsolete script removed: use Twine 1.4
To recap, when you install this script:
You have \ twenty dollars....will be rendered as "
You have twenty dollars."
You have \ <<set $cash = "twenty">>\ <<print $cash>>\ dollars....will be rendered as "
You have twenty dollars."