I guess we could make it private. It really doesn't matter to me, either way. Although, I'm not sure how to go about doing that... Spikeman?  

Yeah if you don't want the story spoiled, don't look at it!

Also my old work is now in the SVN so please check it out.

Edit: I just tried out the APP in the SVN and the grayscale looks AMAZING. Much better than Duck's kit in my opinion.

Edit 2: I have no idea what is and isn't allowed in APPs, can someone recommend somewhere to read about that?

This post has been edited by Spikeman on 9 Nov, 2007, 2:07

Thanks grendel!

@Spikeman:
wikiti can probably explain in more detail, but basically, no SMC is allowed.  That means no variables at all that are defined like
c1

ec2
or real SMC for modifying the code itself.

Also, you can't use PutS if your string is in flash because you have to change ROM pages, and when you change ROM pages, the pointer is no longer pointing to the string.

Generally speaking, code on one APP page has no access to code on another.  Mostly, RAM is used to pass stuff in between, registers, or the stack.  Passing parameters by code stream is impossible.  Passing by reference works to a certain degree, assuming data is near the location of the bcall.  Generally speaking, you want to put associated data w/ associated routines, instead of all of it at the end.

if you define data using .db, it's permanent, so stuff like sprites, constants, etc can be defined that way provided that the routines that use them won't have to modify them while they work.

Hope that helps

Ah okay, I was under the understanding that many bcalls and such were not allowed. In short, it's not as hard as I thought. I'm anxious to start working on something, where should I start?  

QuoteBegin-Spikeman+12 Nov, 2007, 6:37

 ya, we've been constantly updating and keeping in touch using googlecode and the SVN, so you could probably look there and here for any updates.

atm, Halifax and I are finalizing the text standard.  From what Jim e told me, using bcalls for text is generally bad in gs because interrupts are disabled (so no GS interrupt running).  I've tested it w/ my temporary appSafePuts routine, and it isn't as bad as he says.  However, it only comes in dark gray, since only one layer of gs is affected by the bcall.  Designing it from scratch looked like a good idea since the text is aligned 8x8 sprites, and we have the flexibility of 3 colors of text, as well as invisible text lol.

We've been laying some ground work for the most part.  When I get a chance, I'll organize all the map based events into categories, and we can probably discuss how to implement it in code.

For now, I'd just say check the SVN and the googlecode page, and get familiar with the code we've been working on now.  Probably get used to how to use RGP and graymapper, though it wasn't documented too well.

I suggest you get wabbitspasm, or SPASM and wabbitsign separately from revsoft.  We'll be using those instead of TASM and devpac8x.  We'll also be using wabbitemu for emulation, and I think that's already been included in the SVN.  

I think that's it for now.  Thanks so far

IDK Desolate was close enough for me to call it a RPG but this will be so much larger and have more things that desolate ever had.  

It has been a while since I saw tr1p1ea here O_O