ID:167334
 
what all do i need to create a new game? also, what do i need to know?
Well, the first thing you need to create a game is an idea, preferrably one that won't respond with about 50 entries if you search it in the hub. Then, you need the software, which I assume you already have, and finally, programming skills. You'll also need iconing skills unless you can find someone to make icons for you.

The best way to get programming skills with the DM language (in my opinion) is to create a simple RPG, using the DM guide to tell you how to do the basic stuff. It takes a long time even to get reasonable at programming, and only then do I sugest you try and make a proper game. Trust me, otherwise your game will be full of noobish programming flaws (which is guaranteed to happen for people's first games).

So yeah, there's a lot involved, and many people give up fast. But at least you've got something to start with now, the rest is up to you.
There are several fine beginner tutorials at http://www.byondscape.com/ ascape.dmb?type=%2FForm%2FSearch&query=&category=Tutorials. I highly recommend any of the ZBT series as your starting point.
You need dream maker to make byond games, time helps too. You need to find some good tutourials and demos to help you get started.

checklist:

1. Never give up. when theres a will, theres ALWAYS a way.
2.check out various demos, tutourials, but dont copy and paste code. Look at comments and try to see what exactly the coder did to have the result.
3.Never be afraid to use the manual, it is very helpful
4.Download a picture of penguin and put it on your desktop.
5.Dont get in over your head(dont try to make a mmorpg as your first game)
6.Dont make a dragon ball game. just dont. We have enough.
7.Dont steal code
In response to Rky_nick
Sweet checklist, man! Let me comment.

Rky_nick wrote:
checklist:

1. Never give up. when theres a will, theres ALWAYS a way.

So . . . that means Nadrew might still love me?

2.check out various demos, tutourials, but dont copy and paste code. Look at comments and try to see what exactly the coder did to have the result.

That's a good way to learn. However, if you don't know anything about computer science or code-writing to begin with, it won't help a whole lot! ZBT isn't a great tutorial for you if you haven't ever written code before.

3.Never be afraid to use the manual, it is very helpful

Once you learn the basics of coding, the manual (F1 help) is your mommy. Whenever you get stuck or forget something, just call mom and you're good to go! However, until you hit that point of "DM proficiency", which requres that you have a Base Attack Bonus of at least +3 and 6 ranks in Knowledge (data structures), the manual will mostly serve to confuse you.

4.Download a picture of penguin and put it on your desktop.

He's not kidding. You'd better do it.

5.Dont get in over your head(dont try to make a mmorpg as your first game)

Getting in over your head is OK. Just don't expect other people to get you out, and don't be afraid to abandon or restart the project a bunch of times. You can learn a lot getting in over your head, but it's important not to get a big head and expect that you can do anything you set your mind to on the first try (or one of the first ten tries, for that matter).

6.Dont make a dragon ball game. just dont. We have enough.

Meh, if you want to make a dragonball game, or any kind of game, go ahead! Don't let anybody discourage you. Be forwarned that the BYOND community is very critical of BYOND games since there are so many and many more in development, but that doesn't mean you should try if you're so inclined.

7.Dont steal code

This is *so important*. Let me elaborate. Many people will OFFER you code. If you don't understand it really but you plug it into your game and it works, it's *still stealing*. No, not in a legal sense. But if you're trying to learn to create games (or anything else), you need to learn by DOING. If I hold you hands and make them swing a bat, it doesn't matter if you hit a home run. As soon as you get in the game, you're going to be as helpless as if I weren't there. Okay, enough with sports analogies. You'll learn when you're actively participating in writing your code. When somebody writes code for you, it's to demonstrate a principal. Take the principal and write your own code based on it.



Now taht we're through with that, give me an email if you need help getting started. One of the most helpful things when you're learning brand new things is somebody who you can direct your stupid questions at. Hold! I'm not saying that you're stupid! Nobody learns to write code without misunderstandings, mistakes, and misadventures that make experienced coders laugh or cringe. If you want me to help you through your infancy here, you can get me at piratehead care of gmail dot com. Good luck!
In response to Rky_nick
Rky_nick wrote:

4.Download a picture of penguin and put it on your desktop.

This requires more than just the normal penguin, for a feat so daring as to help with programming, you need a super penguin. The only super penguin I know of is Tux.

Anywho, the one thing that I think is most important in programming: Being willing to learn. If you refuse to take the time to learn what you are doing, you can not do any better the second time (And there will be a lot of second times.)
In response to Rky_nick
Rky_nick wrote:
7.Dont steal code

when ever you are offered a code, take it apart, rewrite it. look up anything that you dont get in the DM Guide.

~~Albire