2d engine , should I ?
Moderator: Coders of Rage
- blackball2186
- Chaos Rift Newbie
- Posts: 42
- Joined: Sun Jul 24, 2011 3:26 am
- Favorite Gaming Platforms: NES SNES PS Dreamcast
- Programming Language of Choice: C#, C / ++,
- Location: Los Angeles, CA
Re: 2d engine , should I ?
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
- thejahooli
- Chaos Rift Junior
- Posts: 265
- Joined: Fri Feb 20, 2009 7:45 pm
- Location: London, England
Re: 2d engine , should I ?
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.
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.
I'll make your software hardware.
- blackball2186
- Chaos Rift Newbie
- Posts: 42
- Joined: Sun Jul 24, 2011 3:26 am
- Favorite Gaming Platforms: NES SNES PS Dreamcast
- Programming Language of Choice: C#, C / ++,
- Location: Los Angeles, CA
Re: 2d engine , should I ?
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
- VolsporTV
- Chaos Rift Newbie
- Posts: 40
- Joined: Wed Apr 11, 2012 12:18 pm
- Current Project: The Void
- Favorite Gaming Platforms: PC, NES, Dreamcast
- Programming Language of Choice: C/++ and ByondScript
- Location: Enid, OK
Re: 2d engine , should I ?
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.
- THe Floating Brain
- Chaos Rift Junior
- Posts: 284
- Joined: Tue Dec 28, 2010 7:22 pm
- Current Project: RTS possible Third Person shooter engine.
- Favorite Gaming Platforms: PC, Wii, Xbox 360, GAME CUBE!!!!!!!!!!!!!!!!!!!!!!
- Programming Language of Choice: C/C++, Python 3, C#
- Location: U.S
Re: 2d engine , should I ?
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!
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!
"Why did we say we were going to say we were going to change the world tomorrow yesterday? Maybe you can." - Myself
- thejahooli
- Chaos Rift Junior
- Posts: 265
- Joined: Fri Feb 20, 2009 7:45 pm
- Location: London, England
Re: 2d engine , should I ?
I wouldn't say design the entire engine before starting, but definitely plan ahead before starting a certain component of the engine.THe Floating Brain wrote:DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.
I'll make your software hardware.
- dandymcgee
- ES Beta Backer
- Posts: 4709
- Joined: Tue Apr 29, 2008 3:24 pm
- Current Project: https://github.com/dbechrd/RicoTech
- Favorite Gaming Platforms: NES, Sega Genesis, PS2, PC
- Programming Language of Choice: C
- Location: San Francisco
- Contact:
Re: 2d engine , should I ?
Generally, the more the better.thejahooli wrote:I wouldn't say design the entire engine before starting, but definitely plan ahead before starting a certain component of the engine.THe Floating Brain wrote:DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.
Falco Girgis wrote:It is imperative that I can broadcast my narcissistic commit strings to the Twitter! Tweet Tweet, bitches!
- THe Floating Brain
- Chaos Rift Junior
- Posts: 284
- Joined: Tue Dec 28, 2010 7:22 pm
- Current Project: RTS possible Third Person shooter engine.
- Favorite Gaming Platforms: PC, Wii, Xbox 360, GAME CUBE!!!!!!!!!!!!!!!!!!!!!!
- Programming Language of Choice: C/C++, Python 3, C#
- Location: U.S
Re: 2d engine , should I ?
dandymcgee wrote:Generally, the more the better.thejahooli wrote:I wouldn't say design the entire engine before starting, but definitely plan ahead before starting a certain component of the engine.THe Floating Brain wrote:DESIGN THE ENTIRE ENGINE BEFORE WORKING ON IT.
+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.
"Why did we say we were going to say we were going to change the world tomorrow yesterday? Maybe you can." - Myself
- blackball2186
- Chaos Rift Newbie
- Posts: 42
- Joined: Sun Jul 24, 2011 3:26 am
- Favorite Gaming Platforms: NES SNES PS Dreamcast
- Programming Language of Choice: C#, C / ++,
- Location: Los Angeles, CA
Re: 2d engine , should I ?
Thanks for your input everybody, I will definitely keep your advice in mind