Nice. This is definitely going on my "games to play" list
It looks awesome, especially given the language.

Edit: 900^th post!

Hm... Looking at it, you don't actually have to have the branch table at the beginning. Good for you, figuring that out
Don't you need ($-$4000)/3 rather than $-$4000, though? Anyway, if you edit AsmDev's batch files somewhat (and change your source a bit), you won't have to go away from AsmDev and TASM.
In short, you'll need to change the compilation order to compile the first page last, add export directives to all pages except the first, and add an #include to the file for the first page so it includes the labels exported from the other pages.

Nice!
* calcdude lost The Game too, though

About the branch table thing - I dont put that at the start of my programm, and it still jumps to the right place on page 2.

The branch table is the pairs of .dw's and .db's. Unless you're not using the code you posted, you have a branch table.

Since I dont put it at the start, there's no need for the JP to the ProgStart either.

Same as above. Are you using the code you posted?

And appearantly my assembler doesn't want the label name after the .dw, it wants the offset.

As calc84 said, labels pretty much are offsets. The assembler doesn't like it because it's in a different file. You might have to move away from TASM, or at least AsmDev.

Like I said, If my label is the first thing on  Page2 i just put $4000 there, but I don't want to manually count every line to calculate what offset the other labels are at, that's insane!

I think I've already responded to this

Of course I could load a number in AppBackupScreen and then make a jump table at the first label of Page 2, which isnt much work or takes much room, but it's still cheating and a way of hiding my incompetence as a programmer, ghehe...

That's slower, not to mention unnecessary.

And I'm not having ANY problems at the moment, everything is working fine.
Well, I still can't jump to anyhing but the first label on page 2, but you now know why that is

Yes we do

And don't worry, you aren't sounding rude.

Good

I should've made muself much much more clear, you're no psychic.
I'm already overwhelmed by the many people willing to help me, and they're helping me ALOT, so thank you!

We're trying our best

Ah, that's the problem. Since they're assembled one page at a time, each page is unaware of the other's labels.
Depending on what assembler you're using, you could make the whole app one file (BuckeyeDude and I gave examples for Spasm and Brass).
But, if you insist on doing it this way, you have two options. The first is to have each page file included in a larger file, but your assembler still has to support multiple pages in one file. The other option is to make use of the export directive, but this entails adding another #include to the first page and means you have to assemble the first page last.

Again, what assembler are you using and how is your source formatted? Are you using one file per page or one file for the whole app?

The only problem with that is it doesn't work on the 83+, for which RAM page 0 is permanently in $C000-$FFFF in memory map mode 0. There's no good way to do it in memory map mode 1, either, or I would write one.
Edit: Ninja'd

Sounds nice. I'll inquire over PM if I feel like it