Currently unnamed fighting game

[Nextoy]

So after messing with the game maker for a while I think it's about time I go around to actually getting started on a game I'm making. Now with that there's only two real problems I have:

1. I don't know C programming that well, so it'll probably be a little rough.
2. I don't have anyone to actually sprite up the characters for me.

So I figured I'd post this here to see if anyone wants to help me out. About ten days ago I posted a request for a spriter as well, but I took down the thread since it went without any response. So now I'm making a more generalized thread for the game here.

I also prepared a document containing a bit of information about the game for anyone to read. It's located in the following link.
https://docs.google.com/document/d/15zB ... oI8Ck/edit

Yes I realize that this is a bigger project then what most beginners would normally do, but I have every intention to see this game's production to it's end. If anyone has anything they want to say about it, please speak your mind! I wont judge you or yell at you for whatever you say, I want whatever feedback I can on this.

And if a lot of people say that this project is too big or complex for someone like me, then well you might have a point. However even if I put this in the shelf I'm still going to come back to it later. This is a good plan for a game, and I want to be able to play it one day.

So yeah, I think that's all I need to say right now. Also if anyone has a good name that'd be nice.

[SuperSonic]

Hey, good luck on your project!

[Nextoy]

Blah, thanks. I'll be needing at least luck with this one, haha. ^^'

[skydereign]

And if a lot of people say that this project is too big or complex for someone like me, then well you might have a point. However even if I put this in the shelf I'm still going to come back to it later. This is a good plan for a game, and I want to be able to play it one day.

I don't think you should start with a project this large unless you have a good understanding of how gE works. At the minimum you need to really understand variables and the event structure used by gE. Without those you'll end up creating an unnecessarily complex, and hard to work with system. A lot of new users try to tackle large projects when they first start out, and this ends up confusing them even more.

So my suggestion would be to not actually work on the game engine quite yet, and just use gameEditor. You can still do things with this project in mind, in fact it would even be better to do so. But test things out first, learn how to implement something before you add it to your game, and then learn a better way to do it. If you do that, you won't end up like many users where you get too concentrated on adding things to your game that you don't learn. What I first started using gE I spent a week or two learning to implement any feature I could come up with. This allowed me to have a larger understanding of how games in gE can and should be created, and in the end that will help you when working on your game (making it faster and better).

[Nextoy]

Actually I've already thought a bit ahead of you on that. I'm making the game in steps and plan to release a demo for people to see whenever I've gotten certain points down. Such as right now I'm focusing solely on getting one character to do a handful of attacks, getting the health bars to work properly, and keeping them from running outside of the screen and falling into an unknown abyss.

[skydereign]

Actually I've already thought a bit ahead of you on that. I'm making the game in steps and plan to release a demo for people to see whenever I've gotten certain points down. Such as right now I'm focusing solely on getting one character to do a handful of attacks, getting the health bars to work properly, and keeping them from running outside of the screen and falling into an unknown abyss.

That isn't quite what I meant. Naturally you'll make your games in steps, but you should have the big picture in mind when starting a game like this. Knowing how to do everything before you actually go to make the game is extremely helpful. If you just keep adding code to a game, it will eventually break. For instance adding an attack might require you to add a special case in the movement code. That's fine if that is all it is, but chances are you will need to add something else that may impact it. I know you can't make your game perfect on your first round, but you can definitely minimize the troubles if you are well prepared. All I'm suggesting is you learn how to do more things in gE and get really comfortable before starting to actually construct the game.

[Nextoy]

Fair enough. That's actually part of the reason why I've been messing with a few of the demos on here to see how much I can manipulate without them breaking.

[Hblade]

gl

[Nextoy]

Thanks, I'll probably be needing it.

[SuperSonic]

Oh, here's a tip. You'll want to learn everything you can about file input and output

[Nextoy]

Oh, here's a tip. You'll want to learn everything you can about file input and output

Haha, looks like I have something I'll have to look up then ^^'

[SuperSonic]

This may help http://www.cplusplus.com/reference/clib ... tdio/FILE/

[Nextoy]

This may help http://www.cplusplus.com/reference/clib ... tdio/FILE/

Indeed it is. +1

[JamesLeonardo32]

I do say, good luck. But at the same time maybe make a short easy-to-make game before hitting it big.
Thats really all i can suggest for now.

[Nextoy]

I do say, good luck. But at the same time maybe make a short easy-to-make game before hitting it big.
Thats really all i can suggest for now.

Ha, well it's not like I'm trying to do something annoyingly large at least ^^'