i am trying to make a top down shooter and i want a map that scrolls along where ever the character moves. so that instead of the character moving the map moves, but there is one big problem i cant figure out how to make a map as large as i want that works, or any map for that matter. also is there a way i can have the program so that it doesn't calculate all of the map at once as i am planning on having some rather big maps. and if anyone has a way for me to rotate sprites that would be great because i have alot of sprites 4 for each character and then there are a lot of others and i want to save as much space as possible.

also if anyone can help me make a menu that would be awesome, i already tried ( https://codewalr.us/index.php?topic=186.0 ) it didnt work

@Jonson26 Since this is in the Axe subforum, I think this is meant to be in written in Axe for the 83+/84+/84+SE series and doesn't have to do with TI-Basic or the nsipre.

@Jonson26 Since this is in the Axe subforum,

Oh. Sorry,  I might have overlooked it.

it is written in axe parser for the ti 83 plus(non silver edition)

Well, in that case I can't really help you much, b7ut it seems to be entirely possible.
You might want to take a lookj at this: https://www.omnimaga.org/ti-z80-calculator-projects/super-mario-bros-2-port-(axe)/.
Since Mario is a sidescroller, you might finde something useful in its code. Also, there seems to be some useful information on that topic.
Good luck! 

Odd... I could have sworn there was a link to a tutorial.
Anyway, looking at the source code of a sidescroller seems to be your best bet in finding the information you need.

Wow! Thats a lot of questions. Ill try to answer them all.

1. Making a map that moves with the character and extends beyond the screen:
You dont say how the map is formatted. I assume you mean a tile map. Creating a tilemaping engine is not terribly hard, but creating a good one is. Runer112 has made a really good one called YAAM. There is really no reason not to use it. It is a bit confusing to learn but straightforward enough when you figure it out.

2. Rotate sprites:
Axe has sprite rotation commands built in. I don’t remember what they are exactly but you can find them in the ‘s’ section of the catalog. Remember that they use the same memory so copy or display the sprite before you use another rotation command. They are also sort of slow. Not a big deal if you are rotating one or 2 sprites a tick but can be a big problem if you rotate many each tick.

3.  GDB’s:
I don’t think you understand what a GDB is. Its nothing more than a pointer. All it does is tell the program to look in a specific spot for the data. Since all it does is point to the start of the data, the data can be of any size. If you wrote:
:Data(0,0,0,0,0) -> GDB1Then GDB1 would be 5 bytes long.
:Buff(NUMBER) -> GDB1Then GDB1 would be NUMBER bytes long. There is no limit to how big NUMBER can be as long as there is space in memory. It can point anywhere. If you did: L1 -> GDB1 then you could use GDB1 instead of L1.

I find that it is very helpful to program with a copy of the Axe Parser command list nearby. You might want to spend more time to become very familiar with pointers before you continue. Much of Axe requires you to have a solid grasp of them. (Plus you can do some really cool things with them when you become a better programmer)