Awesome , too bad the lobsters didn't work out

The next version is available now
New Features:
- pause function
- popups when you attempt to buy something
- three different graphics modes
  - Abstract - only outlines, no sky - fastest on handheld
  - Medium - underground is not drawn
  - Full Everything is drawn
- new game-over screen
- a new track
- better performance on the handheld
- data is now stored in a variable to survive updates. To prevent cheating it's obfuscated

VV Download now VV

It would, if there was a physics engine in 3.1. Unfortunately it isn't available on 3.1 and it's essential for running the game. So basically there earliest supported version is OS3.2, because of the physics engine. It would be possible to include the physics engine via ndless, but that would be a lot of work only to add a feature, that's already available on newer versions that also support ndless. I'm sorry, but it won't work on OS 3.1

That's quite similar to what I do here. I don't use sprites for the background though. On of the most costly operations is to recalculate the positions of the vertices every frame. That's necessary though a blind mode would probably be quite funny But by disabling the soil it gains some performance. The abstract mode just avoids filling shapes, which makes it faster, too.

I know about on.save and on.restore. but data saved in these methods doesn't survive an update. That's not that tragic, when you don't update at all or your game doesn't depend on previous sessions. but if you unlock something and then there is an update with a lot of new features, or even a small bugfix update all your data is lost. That's what I tried to avoid by storing the data into a variable. It's still not easy to cheat, because the text in the variable in unreadable. And as I want to maintain the possibility of updating without users losing their progress I implemented it that way.

Hum, I'm not sure to understand what you mean...
By "update" you mean people downloading a new version of your tns, right ?

If so, then the "hcrdata" of the user wont' exist anymore since the .tns will be replaced by your file...

Or maybe what you mean is that people who update will have to copy/paste the lua code into their own tns file (which contains their hcrdata), and then, yes indeed only the lua code will be updated and the data will be still there

(Also, security by obscurity isn't really secure But yeah, it sure will prevent most cheaters I suppose ^^)

Also, just tested, it's pretty cool, good job.

He might mean a way to copy the file data from the file without opening the script editor, and then ability to paste it into a future version. (or something like that)

My main intention was not to prevent cheating. And yes, when the user updates the new file doesn't contain the variable anymore. But there are at least three ways of updating without data loss:
1: Use the script editor and copy-paste the new lua code into the old program. 2:Copy the page of the new version to the file of the old version. 3: Overwrite the var in the new file with the old state, close the file and reopen it. As I said my main intention was to provide a way to keep your old highscores and your unlocked cars and tracks. If you really want to cheat you can always do it. It's easier when the savestate is accessible but that's acceptable. The problem is that any kind of data saved via on.save will be bound its script. The only other way would probably be to let the user insert the old state directly in the script. That wouldn't be much more safe though. Obfuscation will prevent most attempts to cheating, but other methods won't ban cheating completely, too.

looks awesome! mind id i look at the code?

The project is open source (as are pretty much all nspire lua projects), so I'm sure he wouldn't have a problem with it.
Click Script Editor, Edit Script in the student software, while that document is open.