The Frantic Fisherman (Compute's Gazette)
Idly floating in your boat, waiting for the fish to bite, is a fine way to relax. In this game, however, an angler's dream becomes a nightmare when sharks get the notion that you're the bait and thunderclouds threaten you with gargantuam raindrops. It's good you remembered to bring your shark swatter and an umbrella.
The article for this game can be found on page 58 of Compute's Gazette Issue 12 (June 1984
Why TAS This Game?
The continuation of TASing games from my all-time favorite magazine, Compute's Gazette. This makes my 64th TAS from this series.
This was a packed magazine and I just can't remember what I went for first. I do know this...it was during the time before my C64 arrive, so I quickly started working on my Vic-20 instead. I really liked this game because it had really good graphics (Vic-20 version only). As for the others, in that issue, they were not as good...yet they had better game play.
As I played this game, I quickly got bored with it...as it became very monotonous and I discarded it very quickly.
Game Difficulty and Ending
There is only one kind of difficulty available here, and that is the speed of which the game plays. To change it, you just select one of the "Function" keys. I choose the fastest selection (F7), because it makes for the fastest TAS.
Effort In TASing (BOTed)
After I found out that a "Maximum Score" run was the only possibility, I decided to BOT this game. There was no way that I was going to put tons of time in crafting these inputs. Especially since I saw that it was going to be hours long. So...I modified my AI architectured BOT to sense when to apply inputs for a given situation. Every input of this game was created by this BOT, which took about 4 to 8 hours to run (I don't know, because I wasn't in front of it and I was too lazy to add a time stamp of completion). Many problems were detected, which meant I had to go back and re-run this a few times. Once I got this to a submit-able state...I noticed another detail that needed to be addressed.
This game started breaking, the longer it ran. The score started changing colors, the "Lives" indicator was pumping out PETSCII characters, and the screen started to disappear. Well, I realized that when the "Lives" indiator rolled over from 255 to 0 (being an 8-bit value)...the game ended, as if it detected no lives remaining. This was when I discovered that the maximum score can change, if I were to loose lives in preventing this glitch from occurring. DrD2k9 and I talked about this and he had a statement that I think covers this situation. Please wait for his comments in the discussion thread.
Human Comparison
Please note that this run was done on normal speed.
Darkman425: Claiming for judging.
Darkman425: This submission avoids deaths as otherwise this results in an infinite scoring loop that, assuming there isn't some score that also crashes the game, delays the end point of the game ending via crashing. Thus not dying makes sense in this case for game completion via maximum score. A small part I noticed is that a water droplet is blocked for 50 points to the crash rather than hitting a shark for 75 points. Due to how sharks spawn 2 at a time, barring the one shark at the very start of the submission, it doesn't seem possible to end the game with 25 more points. Nice botting on an incredibly repetitive game!
Accepting to Standard.
despoa: Processing...