Mega thanks to iambian for getting that working was giving me a headache.

Anyway.

I Took what he had and changed some stuff around mostly making it use our PRNG routines so that we can rely on the fire spread in replays. I also made it feel a bit more natural by using the same PRNG output to limit the bullets travel time in a seemingly random fashion like fire



(note ignore the scoreboard i did not enable hex mode like Iambian so its all giberished )

Aww, look!  It's the cute Iambian shooting fire with his cyoot dragon breath.  Who's a cute little dragon?  You are. </Cooing>

It looks awesome!  Major props to you guys; I realize that it was really to code, but it looks amazing.  Excellent work!

Did someone say something about replays? What'll that do?

Replays are keystroke recordings that form up a movie of what you have done that game session. If you had a particularly awesome run but forgot to turn on the record feature of Wabbitemu, or if you're out on the road playing on a real TI-83 Plus, you can save what you did and have an automatic replay of it so you can show your friends how awesome you are.

After all. Vids or it didn't happen.

That is really frikin' tight.  How many can you you have saved at once?

Mega thanks to iambian for getting that working was giving me a headache.

Anyway.

I Took what he had and changed some stuff around mostly making it use our PRNG routines so that we can rely on the fire spread in replays. I also made it feel a bit more natural by using the same PRNG output to limit the bullets travel time in a seemingly random fashion like fire



(note ignore the scoreboard i did not enable hex mode like Iambian so its all giberished )

Lookin good geek!

Quote from: ztrumpet on October 28, 2011, 10:57:52 pm

Aww, look!  It's the cute Iambian shooting fire with his cyoot dragon breath.  Who's a cute little dragon?  You are. </Cooing>

It looks awesome!  Major props to you guys; I realize that it was really to code, but it looks amazing.  Excellent work!

Did someone say something about replays? What'll that do?

^_^ *happehfaic*
</nonproductivepost>

Replays are keystroke recordings that form up a movie of what you have done that game session. If you had a particularly awesome run but forgot to turn on the record feature of Wabbitemu, or if you're out on the road playing on a real TI-83 Plus, you can save what you did and have an automatic replay of it so you can show your friends how awesome you are.

After all. Vids or it didn't happen.

That's pretty awesome!

Wow, that would be awesome Is it okay if I use that replay feature in some of my programs if I ever feel up to it? That would be lovely for walk throughs and help features for games !

Ah, good point, so I should store a copy of the randseed, too... THanks much, I hadn't even thought of that!

Replays sound pretty cool.Does it store the key, and then how long it was pressed, or does it store whatever key is pressed each time through?

it stores what keys are pressed every game cycle then uses a modified RLE scheme to compress them on the fly. well thats the intent at least. to my knowledge not a lick of it has been coded. other important behind the scenes things to work on >.<

Not a real update, but I just want to share that after a natural disaster hampered the other side of the CaDan dev team (geekboy), we're getting back on track.

Tonight during HCWP, we hashed out yet another sprite routine to add to our already growing collection, which looks more like an actual clipped sprite routine than the others. This advancement was necessary for geekboy to start work on a secret character's shot type. (EDIT 2: This was also necessary to work in a primary shot type for the dragon. The flames you've seen was his secondary shot type.)

I also need to remind everyone that we have two slots open for the normal playable characters, and two slots open for the secret playable characters. Sorry Netham45, I decided to drop your pre-lobsterification variant, unless we are unable to get two normal playable characters in.

The next leg of the project beyond that is getting the decompression up and running and codifying CaDan's resource table. These two things are the things that allows CaDan to load level sets, so I cannot take that sort of thing lightly. This means that I'm going to be spending some quality time losing what's left of my hair... and mind... over this mess. You know, debugging and all that good business.

Self note: Create static resource entries and write script commands that rely on them. This way I won't have to figure out whether the script system or the resource loader went boom.

EDIT: While you're mulling over that, why don't you check out some eye candy that geekboy posted a while back that somehow got superseded by a posting I made involving high-accuracy shooting: http://ourl.ca/2637/255825 . If you look at it closely, you can see that it does indeed hit the upper bullet limit.