Thread: How would you design a RPG?

I always try to make little rpg's, but my designs always fail. Usualy I have a main game loop that executes 50 times a second or so. In the game loop it gets input, updates stuff (locations, animations), then redraws the screen. For my screen I usualy have a structure called layer than has a multidimensional integer array representing the tiles on the screen. Then I have a structure called display that is an array for three layer structures. The bottom one is for background tiles, the second one is for character sprites, and the top one is for stuff that goes in front of characters(birds, clouds, doorways). I never get to doing the battle or inventory stuff though. I am just wondering how other people would design a RPG.

RPG's are the hardest games to make

Well, I got a text document on the internet somewhere on making RPGs. I will send you the URL when I remember where it is.

PS: The document was written by me, BTW

Josh, I feel your pain. RPGs are very difficult to create. I started to create one in Allegro, but then it wound up just being a tile engine. I thought to myslef, how could I ever make this into a game? The main problem is probably that I didn't plan for the game at all. Stupid me.

ff, hopefully you can find the URL, because I would really to see it.

it's got some source from an *wink* Allegro *wink* rpg I made a while back as well.

and no, you can't download the RPG either. When my HD crashed January I lost it, I forgot to backup stuff (I always back up in January, and the year I forgot to, BANG! It crashed)

I hope I can find it. A BUNCH of people want to read it.

another thing you might want to try to do is poke around in the data files for RPGs that other people have made and see if any of them are simple enough that you can understand how they work.

Originally posted by TechWins
but then it wound up just being a tile engine.

I totally understand that! That's one of the reason's I'm putting so much effort/time into getting SkyLock 1's engine running as smooth as possible and as modular as possible. That way I can reuse 90% of it in the 2nd edition of the game which will be a top-down space shooter and the 3rd edition which will be an RTS. I'll only have to change the gameplay portions but the input/sound/music/blitting/etc will all be the same wrappers.

The main problem is probably that I didn't plan for the game at all.

I feel you there! I learned a great deal on the first month or so that I worked on the game. I've spent a good part of the last 5 months reworking (on paper and THEN the compiler) a lot of the headaches I wrote for myself in the first month.

Lesson learned. My notepad goes everywhere with me now.


JoshG
I think the hardest part of writing an RPG is the story/character building. You can get away with an OK magic system and an Average combat system if you have a great story and good character depth. But no super magic system/combat system will make up for a poorly written story and bad character design.

exactly.

If you notice nowadays companies like squaresoft are focused too much on graphics and the battle engine. They just put in an average storyline and ship it, and people buy it because it is made by squaresoft.

I know it's not an RPG (: But a great story line is, imo, the reason that Max Payne is such a great game. Sure, the great graphics and bullet time don't hurt, but it would be stupid without a storyline.

First write the ads, then shoot the movie.