Cylon Zap is an arcade-style game where a space station defends itself at all costs. Enemys, known as Cylon's, are constantly attacking the your base. You must shoot them before they dive (kamikaze-style) into your territory and land a strike.

The article for this game can be found on page 48 of Compute's Gazette Issue 2 (August 1983)

The continuation of TASing games from my all-time favorite magazine, Compute's Gazette. This makes my 57th TAS from this series.

I'm not sure how all this happened, but in the beginning I got a group of magazines from a subscription that my uncle initially started. Well, they sent a few at first...probably to make up for the ones that I missed, to get me interested more.

I can tell you this...this style of the game was very interesting to me; however, the controls and game plays drove me nuts! Since this was written in BASIC, it was slow and not were near responsive as other games that would show up later in the series.

There is no selection of difficulty, as it is a game of skill with random variations. There is no ending, but it loops over and over. The magazine article shows that the last increase in difficulty, comes after you score 50 points. At 60, you get an clear cut ending...only to go back and do it all over again.

BOTing was the only thing that I could think of for this game. It was so painful to go through the entire round of 60 points, that I finally sat down to write a custom BOT for this. What it ended up doing was finding the right RNG seed, which I then modified manually in some places to use the "Smart Bombs" and/or shoot Up/Down over Left/Right (Due to the enemy distances being shorter). Well, after a number of days...the BOT never could get past its fastest spot...so I ended it there.

There is something that is not so apparent, when TASing this game. When a human plays, they are holding the joystick and causing the game to run a bit slower. Because of that, the inputs have to be minimized so that the game can shoot ealier. This is one of the reasons why it was so hard to do this manually, so with the BOT...I designed it to apply 2 frames of a "shooting direction" until it actually fired. In a lot of cases, the shot wouldn't fire, until it was cleared of any previous shots. Also, a frame or two was recovered when the "non-working" inputs were removed.

Some of the things that were cleared up, in the BOTed version:

The BOT that I wrote was more like the one that I wrote for the game #8138: nymx & DrD2k9's C64 Mole Attack "maximum score" in 01:43.88, that DrD2k9 and I TASed.

ThunderAxe31: Claiming for judging.

ThunderAxe31: Accepting for publication.

fsvgm777: Replacing movie file with one that sets the re-record count to 0, due to the submission having botted rerecords (per current policy), and processing.