Charas-Project

Game Creation => Requests => Tutorials => Topic started by: WarxePB on November 13, 2005, 08:03:22 PM

Title: General Tutorial Writing Rules
Post by: WarxePB on November 13, 2005, 08:03:22 PM
So, you want to write a tutorial? Well, you've come to the right place.

First off, if your tutorial is more coding-oriented (How to code an ABS, dashing, RGSS tips), post it in the RPGM Programming forum. If you're not sure what forum it should be in, post it in this forum, and it will be moved if necessary.

Next, some general tips:

-Write about something useful. If a lot of people ask about switches, and there's no decent tutorial about switches, write one!

-Try to use good spelling and grammar. Reading "Next, turn a switch ON" is a lot easier than "turn swtch onn", and it makes your tutorial look more professional.

-Explain anything that people might have trouble with. If your tutorial works with a lot of forks/branches, you might want to briefly explain them, or simply say "A working knowledge of forks/branches is recommended for this tutorial." Optionally, you can also link to another tutorial that explains the concept in depth.

-Add examples. Some people work much better with pictures or guides than just straight text. So, a good idea would be to show a picture of what you're explaining is supposed to look like, or type out the correct code. A working example of the tutorial is even better.

-Make sure it works! Especially if you're doing a coding-oriented tutorial, functionality is a must.

-Be a good mentor. If someone asks you about something in your tutorial, explain it, then add it to your tutorial to prevent clutter in a thread.


I think I covered all of them, but if anyone has anything to add, please do.


Finally, if people really like your tutorial, and you want to sticky it, simply ask myself or an admin, through the thread, PM, email, whatever. If we think it's good enough, it'll be stickied. If not, don't repeatedly ask, because that doesn't give a good impression.


Good luck!
Title: Re: <FONT COLOR=#336AEF>General Tutorial Writing Rules</FONT>
Post by: fruckert on May 14, 2011, 09:48:01 AM
...well, this bot has a stupid name.
Title: Re: <FONT COLOR=#336AEF>General Tutorial Writing Rules</FONT>
Post by: ellie-is on May 14, 2011, 01:38:55 PM
Fruck (and EVERYONE) stop responding to the ****ing bot posts. They will be moved to the junk bin on the right time, but until then, just shut up. Okay?
Title: Re: <FONT COLOR=#336AEF>General Tutorial Writing Rules</FONT>
Post by: fruckert on May 14, 2011, 01:58:55 PM
But it's so fuuuuuun.

/sarcasm
Title: Re: <FONT COLOR=#336AEF>General Tutorial Writing Rules</FONT>
Post by: SaiKar on May 14, 2011, 02:20:13 PM
But you're literally making the problem worse. Most bots these days check to see if people respond to their posts. If we do, then they know it's an active community and report this information back.

This is NOT the first, nor the second, time I've said this but you people don't ****ing get it.
Title: Re: <FONT COLOR=#336AEF>General Tutorial Writing Rules</FONT>
Post by: fruckert on May 14, 2011, 02:33:03 PM
...totally forgot to use common sense there.

Sorry, won't happen again.