Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

Tutorials Section Rules

Status
Not open for further replies.
Joined
Jun 8, 2007
Messages
1,985
Reaction score
490
Tutorials Section Rules
(In Coder's Paradise)

Follow the Coder's Paradise Rules (1-6), http://forum.ragezone.com/f144/rules-and-general-info-180546/.

  1. If a tutorial exists, you cannot post the same tutorial unless you give good reasons why the original is inadequate. Also, you must put a link to the similar tutorial, for cross-referencing. If you can provide a source that backs up your tutorial over the opposing, than that's even better. Remember, the goal for this section is for a non-redundant, clean, easy-to-browse tutorial section that covers a wide range of languages and skills. Please do not clutter the section with duplicate entries. We highly appreciate it if you constructively criticize similar threads before creating your own. Improving a bad thread is better than having two threads with different information on the exact same subject.
  2. Posts simply with Links to Resources go inside the Resources Thread (in Coder's Paradise), http://forum.ragezone.com/f144/resources-60999/
  3. Remember to follow rules (1-4) from Coder's Paradise. That includes using tags to categorize your posts. Example,
    PHP:
    , [C++], [C], [VB], [HTML], [JavaScript], [JS], [AJAX], etc. Tags such as [TUT] are forbidden because it's pointless for the reason stated in this next rule,
    [*][B]Every thread should be a tutorial.[/B]
    [*][B]Remember your tutorials are meant to help people. [/B]Make sure they are thoroughly written. Check for spelling & grammar mistakes, and mostly coding mistakes.
    [*][B]Don't ridicule tutorials for grammar or spelling issues. [/B]Politely tell them in a constructive manor. Also, [I][B]constructively tell them about coding mistakes[/B][/I], to ensure they get fixed.
    [*][B]Use[/B][B] the Like Feature.[/B] Do not reply to a topic if you're just going to say "thanks", or "nice tut" or similar things. It's considered spam. It's much better to use the 'Like' Feature. (Hover over the post and click 'Like' in the bottom right.) That way everyone's happy. (Especially the person who's post you liked.)
    [/LIST]
    [B][COLOR=DarkRed]Follow the rules.[/COLOR][/B] :rolleyes:
    
    
    
    [U][B][SIZE=4]Changes[/SIZE][/B][/U]
    
    [LIST]
    [*][B]Jan 6, 2010[/B]
    [/LIST]
    [INDENT]  - [COLOR=DarkRed][B]Rule 1[/B],[/COLOR] [COLOR=Gray]"If a tutorial has already been posted, don't post it again."[/COLOR]
     - [COLOR=Navy][B]Changed To[/B][/COLOR], "[COLOR=DarkGreen][B]If a tutorial exists, you cannot post the same tutorial[/B] unless you give good reasons why the original is inadequate. Also, you must put a link to the similar tutorial, for cross-referencing. If you can provide a source that backs up your tutorial over the opposing, than that's even better. Remember, the goal for this section is for a non-redundant, clean, easy-to-browse tutorial section that covers a wide range of languages and skills. Please do not clutter the section with duplicate entries. We highly appreciate it if you constructively criticize similar threads before creating your own. [B]Improving a bad thread is better than having two threads with different information on the exact same subject.[/B][/COLOR]"[/INDENT]
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top