Elysian Shadows

Ok so I will have to make a game for my AP Comp Sci Final Project, so why not start now? He wont know the difference. So will be using Allegro, instead of OpenGL and SDL since it will be 100% 2D game. It will be a sim about lifting and stuff like that. Like an rpg, instead the stats are like weight and lifting stats. and the items are supplements and food and ect. Kinda corny but new type of game play IMO. Train too much at once and you over train and stuff... Now will it be better as a "Platformer" or the classical RPG top down camera?



So my plan:

1. Pseudo Code
- Brain washing
- On paper
- Classes and functions
- Just general Idea of the project and story

2. Begin Coding Engine
- Movement and Collision
- Physics, if necessary.
- Save/Load game data
- Load Map

3. Begin Coding Map Editor
- Map editor
- Flags such as "Solid" and "door" and ect

4. Add Details
- Add the story and sprites.
- Add other "systems" as Shop or other needs.

5. Add Details to Map
- Make more backgrounds and sprites

6. Repeat
- Repeat 4-5 as necessary

7. Finalize
- Test
- Fix Bugs
- Distribute

How long do you have to make it?

Moosader wrote:How long do you have to make it?

end of the school year Im assuming so like 7 months

Oh that's a really long time. Should be plenty.
How much experience do you have? You might make some sample review programs before jumping into a full-blown platformer or rpg.

I'm having to do something similar for FBLA

Sounds good on paper, but it will never work like that. Writing a game is nowhere near linear. You can't work out all of your functions on paper, then code them, and follow a step-by-step process.

Your game will grow as you work on it. You will think of more ideas, think of different ways to do things, or realize why your pen-on-paper design isn't going to work and have to rework lots of it.

Of course you have a nice plan for it, just don't get upset when you deviate quite a bit.

GyroVorbis wrote:Of course you have to have a nice plan for it, just don't get upset when you deviate quite a bit.

Fixed =)

you will find that coding takes up by far the least of the time.
time spent researching, testing, fixing bugs, and maintaining code. take up the most time.

GyroVorbis wrote: Your game will grow as you work on it. You will think of more ideas, think of different ways to do things, or realize why your pen-on-paper design isn't going to work and have to rework lots of it.
.

That always happens, I have the exact right plan for even a simple program, it never seems to work as is, I end up tweaking at least 50% of it at minimum

Moosader wrote:Oh that's a really long time. Should be plenty.
How much experience do you have? You might make some sample review programs before jumping into a full-blown platformer or rpg.

Well I spent time trying to learn SDL, Allegro and OpenGL, I found Allegro was the easiest to get started with a 2d game opposed to SDL where you have to find extra libraries and stuff. With Football practice and other HW and lifting getting in the way, I probably wont have full day in a week to just get on the computer and code ... unless I take off some internet time...

davidthefat wrote:So my plan:

1. Pseudo Code
- Brain washing

Do you mean brainstorming? Unless, of course, you plan on brainwashing your target audience into playing your game.

I thought maybe he was like, going to meditate and clear all the thoughts from his head.

trufun202 wrote:

davidthefat wrote:So my plan:

1. Pseudo Code
- Brain washing

Do you mean brainstorming? Unless, of course, you plan on brainwashing your target audience into playing your game.

Yea brain storm... Now I look like a dumb ass

davidthefat wrote:Yea brain storm... Now I look like a dumb ass

Naa, not when there's douchebags like me to point that kinda stuff out. I was just playin' - nothing but love.

I think that a weight lifting game is too complicated for a first graphical game, so I think I will go with a platformer