it's never really "easy" to make an RPG. no matter the language, it's a lot of work. granted, i'd think it's safe to say it's easier to make a better (in terms of speed and graphics, not gameplay) RPG in axe than basic. of course it takes awhile to get used to Axe, though

Umm  I personally haven't tried an axe RPG so I don't know, but FinaleTI is working on an RPG called Nostalgia so i believe he would be able to best answer your question.

Personally i think that making an RPG with axe shouldn't be too much harder than in Basicif you are experienced in both, but you seem to have not been using axe so it might be harder for you, but if you learn axe well it should be about the same, unless you're planning on doing some extremely creative and complicated things.

If you haven't yet, take a look at Raylin's Rules for RPGs to start
http://ourl.ca/6546
Never mind I already told you about it before.

And a look at Nostalgia
http://ourl.ca/6009

Edit: actually now that i think again i think graphmastur was planning on making TAO Unleashed with axe

Oh, and a feature request: automatically making things like Output(0,0) be equivalent to Output(0) (and Output(0,0,"ERKH") be equivalent to Output(0):Disp "ERKH"). In other words, making it automatically calculate the full two bytes as it compiles.

I'm pretty sure Axe does this already.

I'm actually working on an Axe RPG right now, Blox. More info on it later, though.

It *was* my contest entry, and I've never mentioned it on the forums, save a few references and my sig.  It's physics driven and centers on moving around blocks.   Once I work on it again, I'll post info on it.

it's never really "easy" to make an RPG. no matter the language, it's a lot of work. granted, i'd think it's safe to say it's easier to make a better (in terms of speed and graphics, not gameplay) RPG in axe than basic. of course it takes awhile to get used to Axe, though

It depends, in BASIC, if the RPG is not super large (like 4 dungeons and one or two towns max) it can be much eaiser in BASIC, because you do not have to spend weeks trying to figure out how you will get something higher than 1 frames per second on a regular 83+ due to all enemies and ships moving around. In a RPG, almost everything is turn-based so you worry so much less about optimizing speed that it makes some RPGs easier to code than any other game in BASIC. However large RPGs are ridiculously long to create.

An example: Illusiat 7, 8 and 9 took me 2 weeks to create each of them. Mortal Kombat (included in Omnipack SE) took me 2 weeks, even though it's a 10x smaller game with shorter gameplay. xLIB xLIB Revolution, which is just a DDR clone with fancy graphics took me 2 weeks as well (mostly coding, not graphics). In Mortal Kombat I spent most of the time trying to increase the speed (and failed since it was back in 2002)

It *was* my contest entry, and I've never mentioned it on the forums, save a few references and my sig.  It's physics driven and centers on moving around blocks.   Once I work on it again, I'll post info on it.

Quite ironically, both Omni contests (2009 and 2010) had an entry called Blox in the works but none were finished for the contest. Is there a curse on the name or something? ({AP} was the one working on the 2009 one)

If I'm not mistaken, it shouldn't overwrite them.
Unless you call another subroutine that overwrites them, or you write to them manually, they should stay intact.

Hi and welcome here . The best way to do it is to store a TI-BASIC image in  Pic0 through Pic9, then in an Axe program, put [PicNUMBER]->Pointer at the beginning of the code, for example [Pic1]->GDB0. When compiling, this will import the entire picture in the program. To display it, I believe that you do Copy(GDB0,L6,756) then DispGraph or something like that. That would copy the image to the buffer (L6) and DispGraph would display the buffer on the screen.