So I spent basically all day working on my game. Trying to make it be "flashy" free. At times I got so frustrated that I vowed never to code again, but usually ended up doing it again. I started shortly after I got up at 8am, worked non-stop until 12:30pm. Went to the record store. Came back home at 2 and worked until 4 or so. So that's 6 hours of coding today. Until that magical moment happened when everything started working great and no more flashes on the screen. I admit I had to cheat a little by doing the Odyssey 2 equivalent of "drawscreen" twice slowing everything down, and to make up for it I sped up the i's movement. But it apparently needed it or else it wouldn't act so stubborn. Now that I'm finally happy with what I have, the next work on this will be the second 2k. I used up 1,738 bytes, so the first 2k is almost all used up. And I don't want to break the code by adding more stuff than it can handle. I already broke the game a few times today. It was not fun trying to repair it. So one may wonder why I code at all if I get so frustrated with it. I mean, nobody's forcing me to make Odyssey 2 games, and I'm not getting paid to do this. My mom asked me that. I had no answer for her. I guess it's for the thrill of finishing a game, that moment when you look back and say "It's done. I can't improve this thing any more. And I'm sick of this, so I'm going to do something else for a change." What I was trying to do is make a Zelda-like game for the Odyssey 2. Its version of the Atari 2600's "Adventure." Because there are no adventure-like games for the Odyssey 2. I don't know how long to make this game, though. I want it to be complete-able in one sitting, but not so horribly long.