The reason Star Dodge and Dodge'em (and other games like them) work so well is because they use Disp " (no spaces following the quote) to scroll the screen. I also store the coordinates for the objects in a list that I index with another variable to handle collision detection. It's a really complex system, but it lets the game go really fast for TI Basic.
I don't mind if you modify any of my code, just please let me know about it. If you're just looking at it to understand how it works and applying that concept to something else, the no credit is required.
Thank you for acknowledging my suggestions.
Would a 16*8 matrix be too big? It would delete it when the game closes.
Also, what is the goal for the overall (non-running) size of each game? In-game RAM consumption?
I try and make each game between 200 and 400 bytes. They need to be around 300-350 bytes each (on average) in order for the gamepack to fit with all 48 games. To me it's a challenge for the games to be fun, fast, and small, and this is why I enjoy this project so much.
As for the RAM requirements for each game, just try not to go over 2300 bytes or so. Snake and Grass Snake use the same engine (I squeezed two games out of it to justify including it - it's one of the bigger games in the pack, but its size is divided by two as there are two games), and it requires two 128 element lists and one 8*16 matrix, for a total of 2357 bytes of RAM. They are, however, the fastest snake games programmed on the homescreen in TI Basic, and this is a fact I am very proud of. If RAM becomes an issue, though, I can save almost 600 bytes by compressing the two lists, at the cost of a little speed.
If you would like to make games for it, I will consider them for addition.
A Tron game is an awesome idea. I'd certainly like one in the gamepack, no matter who makes it (be it me or someone else).
Show Posts
I can't wait to try this with the ropes. 
My guess is it's the adapter.
