Elysian Shadows

I wasn't trying to upset anyone, or to cop an attitude, I appreciate all the posts that I've gotten. I just have a problem with pessimists, I did not mean to upset anybody, I apologize if I did

Sorry if I sounded pessimistic, it's just that there are a lot of people who want to make RPGs who have no idea what they're getting into. They think that because they've learned to move a single object around the screen by following a LazyFoo tutorial, they are now ready to make an entire RPG.

However, from what you've said now you don't seem like that so I'd advise you just to go for it and make your own engine.

Thank you, I didn't mean to be angry in my other post, if I upset you I appologize. I thInk I will just go for broke and make the engine

blackball2186 wrote:Thank you, I didn't mean to be angry in my other post, if I upset you I appologize. I thInk I will just go for broke and make the engine

Hey mate, it is fine! I would just go and make the engine from scratch so you have something to work with if you decide to make other games.

If I may, I would like to make some suggestions so you can avoid the mistakes I made on my game engine; although my engine was as flexible, powerful and, as easy to use as I imagined; it:
Was not stable.
Had extraneous and occasionally annoying features.
Lagged (easily fixable).

If I may offer the following advice (not to say you are inexpreanced or a bad programmer) so you will not have the same problems as I:

DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.
Do not use the first solution to a problem that comes to mind, come up with several, and logically argue the best one to yourself.
Proto-type things.
Take breaks, this is more of a health thing but I highly suggest it; I did not and now I can temporarily not write or type without wrist pain (luckully I can use an iPad ).

Here is just some general advice:

Keep key development features in mind, for example in my engine I wanted scripters to be able to easily locate game objects in memory. So I implemented an ID system with a "find" function that set a object as a global in the script.
Keep general goals for the engine in mind.
Improve upon or find alternatives to features that are badly implemented in other engines that you know you will need in yours, like my last example the way other engines located objects in memory always bugged me so that's why I made the ID system.
Also use my last tip but for well implemented features (make improvements and new appoaches).

Hope I helped!

THe Floating Brain wrote:DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.

I wouldn't say design the entire engine before starting, but definitely plan ahead before starting a certain component of the engine.

thejahooli wrote:

THe Floating Brain wrote:DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.

I wouldn't say design the entire engine before starting, but definitely plan ahead before starting a certain component of the engine.

Generally, the more the better.

dandymcgee wrote:

thejahooli wrote:

THe Floating Brain wrote:DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.

I wouldn't say design the entire engine before starting, but definitely plan ahead before starting a certain component of the engine.

Generally, the more the better.

+1 I mainly say that for affect I don't mean design every foreach, just make sure when designing to think about and design many algorithms not just OO stuff.

Thanks for your input everybody, I will definitely keep your advice in mind