maybe try to mask the sprite. the character has a whitespace surrounding him

Yeah that might be a good idea. I think that might be a bit slow for basic/xLIB, though.

Masking isn't too much of a slow down with xLib. In fact, that's what I'm doing in Sky's Story. I draw the map layer, and then mask and OR the player, and there isn't too much of a difference then when i just use overwrite.

Ah ok I see. I never experimented with masking but I worried that drawing many sprites per frame slowed things down. I'm glad it doesn't.

Maybe I failed to mention it, but I'm switching over to Axe(The reason why programming battle engine takes forever because I'm trying to figure out how to store list to appvar)
EDIT: That video that SD posted was long time ago stuff
All my stuffs were gone so I started new one from scratch with Axe

Ah ok I see. If you don't feel comfortable with the code size limit in Axe, remember that you still can split your Axe game in sub programs and use a BASIC launcher with XCOPY or Resource and call routines when needed. In any case, though, make sure most stuff including enemy data and NPC convos are stored as data, not hard-coded. That way your code is smaller.

Just please make frequent backups, though. Axe can crash a lot more often since there's no error checking at all during execution.

Currently, no.
You'll have to use appvars or other external vars for more space.

You can store the data to external appvars or programs and archive those. Then you can keep the entire 16 KB for code. Alternatively you can split the game in sub-programs in Axe and run them using a BASIC program. Don't give up on the project, though. It looks great.

For this RPG, I'll just program in xLib again(sigh...all the sprites I have drawn...)
At least, I got my walking engine again
Imma remodel my battle engine so it would looks like a battle in Lufia 3: The legend Returns

(P.S. This is halted until I finish R.P.G. RPG)

Quote from: FinaleTI on November 30, 2010, 03:40:12 pm

Quote from: DJ Omnimaga on November 30, 2010, 03:44:11 am

Alternatively you can split the game in sub-programs in Axe and run them using a BASIC program.

You could use an Axe program as a launcher instead...

Nope, because of the executable code limit, unless there's a way to clear it all between program launches? The launcher would have to be BASIC, since upon exiting ASM programs ran with Asm(), the TI-OS clears the code from the 8192 bytes place where it's ran.

Is it even possible to run sub-programs from an Axe program, anyway?

It's possible to run programs from an Axe program, and in fact, I'm doing that for Nostalgia in an effort to circumvent the code limit.
You need to use Hex Asm to do it though.