TI-PLOW: A Seasonal Game
You have not uploaded your program! Please edit the page to upload your program.
|
 |
||||||||||||||
|
Help Timmy the plow truck driver plow all the snow in the city. However, due to budget cuts, Timmy will lose his TI-PLOW features 100 hand-made levels for your enjoyment. Race against the clock to complete each level perfectly. Can you beat them all this season? |
|||||||||||||||
What the community thinks:
So it looks like you need to fix some bugs. I got to the end of #53, and it started to scroll into a bunch of letters, ASCII chars, and other stuff.
I would like to download your game again, but I will not until you fix your errors and bugs.
Make sure you are using a TI-84 Plus calculator, and not an 83+. I doubt there are any errors, those ASCII characters are most likely text sprites.
I am using a TI-84 Plus. Here is my TI-84 Plus Info:
You most likely pressed the [ON] key to stop the program, and then pressed 2 instead of 1. This will cause the calculator to scroll through the code until the point where you stopped it. The levels are encoded in a large string of seemingly random tokens, which would be similar to what you described.
If this is not what happened, please provide instructions on how to replicate the error.
TI-Plow was thoroughly tested, and there are currently no known bugs.
No, there was no on break error. Usually, you will press [CLEAR] to quit. But it not scroll in the code like your thinking. It showed no "PROGRAM:TIPLOW", and it started to scroll through it.. This is an example of what it showed:
1618984365468@#$ ← No run indicator at all.
65465498435465465
544#%&%@#*&^#!
566$#^@(#&$(*#&
35414765467546456
I am not 100% sure, but I think it started to scroll through the calculator machine coding.
Already beat the game with all +!!! To level 99!
Wow, good job. It's very challenging to get a + on the last level!
Oh and P.S., a few of my friends borrowed my calc to copy the code, because they were not able to connect to a computer, via calculator USB cable, (Using both TI-84 Pluses with 2.55MP) And somehow, I don't know how, but they hacked it using my PROGRAM:EDITLOCK (Which contains the Asm code), also udsed my PROGRAM:PRGMLOCK, (Which allows you to unlock any TI-Basic program, Assembly, MirageOS, etc.) ANd they put a few extra hundred levels of TI-Plow. 😐 😐 😐
Here is an example of the program PRGMLOCK
Where is prgmEDITLOCK?
prgmEDITLOCK is here:
Quote:
Don't copy people work and call it your own. It's pretty obvious that you got this from the Assembly Hex Codes page.
I'm having difficulty believing your claim:
1. The distribution version TI-PLOW isn't locked, so you shouldn't need a special program to unlock it.
2. The level encoding scheme would be pretty difficult to reverse engineer without understanding a large part of the code.
3. TI-PLOW is not designed to support more than 100 levels.
That said, it would be possible to substitute the existing levels for a different set of 100 levels if you were so inclined.
Lets say you have 19546 bytes of RAM. And you archive a list. (For ex: L₁) And it states it takes 12 bytes of RAM, right? And when your archive it, the calc now says 19548. It suppost to add 12 bytes instead of 2. It like its math for the memory functions are wrong??
I think the calculator still holds the variable names in RAM, even if the data associated with that variable is archived. So, having a bunch of stuff in the archive on your calculator can still take up some space in RAM and will degrade overall performance slightly.
When I execute the game, it keeps saying, "ERR:SYNTAX", and "ERR:VERSION", and "ERROR:LINK", and "ERR:BREAK". I did not pushthe on button at all. When it says ERR:BREAK, the message is inverted. (White text on black background). After it shows the ERR:BREAK, it freezes the screen. just like the bunny virus did. (Bunny virus:
The game works flawlessly for me
The root of this whole problem is probably the ERR:VERSION. Is your calculator a TI-84 Plus?
EDIT: I noticed that you do have an 84+. Probably some random error, I would suggest laying of the assembly hex codes that you create (if you put them on your calc) and use SourceCoder3 to test that out.