create 3 functions for your modes. then 3 buttons each calling different function.
no need for if-else thing

i'm not quite sure you read and understood the workshop. what's the point of just reading it? try doing it, try it with your small examples. otherwise you'll ask alot of this kinds of questions which i hear, you already do...

I have learned lite-C with the AUM magezin. It is really easy to learn with it. But level chaning is really complicated. See this at my game...

yeah, im sorry, its like i said though, once you get to the 3D coordinates in the workshops, it starts using the WED, which i dont have yet. And I get a better answer in the forums when i ask these questions, because some of it isnt exactly explained in the workshops. But im really sorry for bugging everyone here.

Don't be sorry, we're here to help. Some members just get a little frustrated when people ask simple questions, that can be found in the manual or a workshop.

Are you doing the right workshops? It's this one just in case...

http://server.conitec.net/down/litec.zip

...Either way, you wont really need if-else code to check the game type because you have seperate functions, which can be run from your different buttons.

You can split your game into different parts like graphics, sound, input/output, collision, physics etc. Then you can bring all your written parts together and build the game. This is known as "Modular programming".

It might seem complecated, but once you actually start writing code; it becomes much easier.

It might help to draft out on a piece of paper what you want to happen when you click e.g, "Story Mode" button, for instance...

1) Close Main Menu screen
2) Show cutscene
3) Load level
4) Load player model
5) Show the GUI (health/ammo/etc)

Once you know exactly what you want you can go about looking for the specific function in the manual, which will perform your task.

Hope this helps you find your way around lite-c.

Thanks a lot! I really appreciate it, this will help a lot. Its just that im new to this, and get sort of impatient sometimes. I'll be sure to check the workshops and the AUMS much more carefully before i ask a question. Thanks!

ok, I've got the main menu finished, all except the functions for the buttons, all i need is one example though. I'm going to save the menu and everything else as seperate programs, so on the endurence button, would i code it like this?

PANEL* endubutton2 =
{
bmap = goover;
pos_x = 10;
pos_y = 200;
button(0, 0, goclicked, gonorm, goover, endurance.c, NULL, NULL);
flags = OVERLAY | SHOW;
}