Qbasicnews.com

Ok, I've got everything ready to make a text based game. I just need to know how to organize it. Should I make it work first, then make it look pretty after, or do it in one fell swoop?

~Bob

it's better to construct a foundation, or an engine on which your game will work from. You want to create an engine so the actual developement of the game will be easy. Try to see where reoccuring events happen, and make a system that easily facilitates it. Once you have the foundation for your game(the squeleton), you can begin to make it look the way you want. Remember, just like an archetectual structure, the larger the foundation, and the stronger it is, the higher the structure can go. :wink: So, it`s better to get all the hard, dirty work out of the way, and then it`s smooth sailing.

bob: use whatever works for you. Its a general practice to build the backend/engine and then work on the frontend. I dont generally make text games. But when I work on a project I build the backend, then quickly put together a make-do frontend. After my backend becomes stable I work on the frontend and refine it.

yeah, just do like I do and go with the flow! I've made some text-based games (kind of) and the great thing about QB is there's many ways to do something, so just go for it!

Heh. I'm making a text-based one because its my first game. And thanks for the advise guys.

~Bob

What do you guys mean by 'engine' anyway?

I guess I'm not ass organized as I thought I was.

~Bob

It sounds like you need to read up on programming. There's a lot of QB sites with tutorials. I learned by studying peoples code and trying things out on my own. Also, QB's help is very comprehensive. Anytime you're stuck, ask questions on the forum. The engine of a program is like the engine of a car. Everything that makes a car work comes from the engine. It's composed of many parts all with individual tasks. And the frame of the car is like the look of the program, the colors, etc. I would look for tutorials on programming structure, subroutines, and program flow. But for now, about your original question, I wouldn't worry about the look of your program now until you have a game that works. Get all the tough jobs out of the way, then reorganise it the way you want. Hope this helps