I don,t mind large programs either, as long as the large size is justified. Example, I will not appreciate if I download a 60 KB large RPG only to find out there are only 4 rooms in it (that are one screen large). Just make sure to not go overboard and it should be fine.

There's also the fact large programs are harder to install, but I think it can be worth it sometimes. Just make sure your install process got as least steps as possible. Example: an archive and RAM folder, not 8 or 9 folders to send one by one and running install programs.

Except that you're still limited to 16 KB. That said, I could fit Metroid II Evolution in 15 KB of code, approximately, and a lot of stuff was hard-coded, like bosses. Granted, there was xLIB that didn't count in that, but I am sure I could have done less hard-coding and fit it in smaller size.

Otherwise, there's always the BASIC launcher+XCOPY+multiple Axe sub-programs solution, though

Menus are quite large most of the time. The Reign of Legends 4 was gonna have a dynamic menu system, but it was still in the 3 KBs because of all the stuff that had to be hard-coded. For a RPG you also got the battle engine, events, walking engine, map loading, title screen, etc. In some extreme cases, you may be forced to put the menu and battles in a totally different program.

Menus are quite large most of the time. The Reign of Legends 4 was gonna have a dynamic menu system, but it was still in the 3 KBs because of all the stuff that had to be hard-coded. For a RPG you also got the battle engine, events, walking engine, map loading, title screen, etc. In some extreme cases, you may be forced to put the menu and battles in a totally different program.

A menu is large? My menus, both for basic and Axe are the smallest part of the code, but that's because they're number based.

You may be right, menus with cursor can be very long and larg

Menus aren't too bad if you make a generic menu subroutine; that's only like 500 bytes or less in Axe, but you still have to hardcode all the different options which could take up a lot more space :x

If you look at my Racer3D: Replay menu... It's a number-based menu, very short, but it's not THAT functional, since I can only have 9 options (as there are 9 algarisms). I could have 10, but I don't want the 0.

However, Metroid Chozo Mission is already a large game, so he might be looking for a really small menu in order for the game not to be too large.

#cough# what?

well, you see, start by making a list with let's say, one element with 6 bytes per element in saferam (so a 6 byte list for now)

the values being L+0 = x, L+1 = y, L+2 = sub x (not position in tilemap but rather that value used to make movement smooth between x positions), L+3 = sub y, L+4 = hp, L+5 = max hp.

then, in a routine executed every time the main loop well, loops, (or an interrupt if you like that style) check if the enemy is within the screen ocupied by samus.  if so, draw the enemy using those coordinates.  BUT, first check if the monster has any hp.  If not, then don't draw it.  Also, to make it move, check to see where the wall is next to it.  If the wall is on it's right, do Y+1 -> Y.  If it's above, make x-1 -> x.  But, only do that if it has hp

the max hp is so that it has a hp to start with, so then it doesn't start with some random value like 54000 and go down by one every shot

if you need code examples, I'll be glad to provide, just ask in a later post.

Quote from: DJ Omnimaga on November 27, 2010, 01:08:27 pm

Menus are quite large most of the time. The Reign of Legends 4 was gonna have a dynamic menu system, but it was still in the 3 KBs because of all the stuff that had to be hard-coded. For a RPG you also got the battle engine, events, walking engine, map loading, title screen, etc. In some extreme cases, you may be forced to put the menu and battles in a totally different program.

A menu is large? My menus, both for basic and Axe are the smallest part of the code, but that's because they're number based.

You may be right, menus with cursor can be very long and larg

Menus can become evilly large. My in-game menu for Nostalgia is about 9500 bytes and I still haven't implemented everything.