I have always wanted to create my own BYOND game. Never really understand the language. I FragalaP am going to do something many people don't. I am going to read and complete the full DM guide. I will also keep everyone up to date to where I am and what I can do. I don't want to add another whining complainer to the developer forums asking how to code and get other people to make a game for them and have their name on it basically.
I will keep everyone updated after every chapter I read.
So here it goes
Designer's Guide to Worlds BYOND
Chapter 1. Meet the Dream Maker
ID:25792
 Jan 15 2007, 6:51 pm
|
|
DarkView thanks a lot for that encouragement. I will read a chapter once every few days and work on that chapter for a week or so. If I ever need some help ill ask the forums and you. Thanks alot
| |
The key is to read a section (which can be as large as a chapter or as small as a paragraph), make sure you understand and have a firm grasp on the information presented to you in that section, then move on to the next section.
If for one reason or another you just don't understand a section, go to the forums. If you can point out the section in the guide there are tons of people who will be happy to help explain it in further detail.
Don't be discouraged if you get a reply like 'oh man, that's so simple, you should give up'. There are plenty of jerks who know how to program on the forums, but there's also a fair few users like myself who are more interested in helping people than inflating our own egos. If you're serious about learning then you'll get help eventually.
The other important thing is to take breaks. This isn't something that needs to be rushed and you're not going to learn it all overnight. If you're going slow then that's your pace. You're much better going at your pace and becoming a good programmer than going too fast and becoming a crappy programmer.
If you understand a section and start to feel tired or bored, it might be a better idea to just go off and think about what you've learned rather than pushing on and trying something new.
One last bit of advice. Make demos based on what you're learning. At the start it's a bit hard because you can only do little stuff that isn't very interesting, but as you move on you'll have ideas on how to do cool things by combining your previous knowledge with what you were just learning. That's when things get really fun.
(Just a side-note, I wouldn't recommend releasing to the public any demos or libraries you make. Demos and libraries are learning tools so they should be made by experts on the subjects, not beginners).
Anyway, I wish you the best of luck.