Tutorial & Resources Rules

[tooltiperror]

Table of Contents

1. Tutorials & Resources Section Rules
   • 1.1. General Rules & Intellectual Integrity
   • 1.2. Allowed Resources
2. Systems & Snippets
   • 2.1. Code Resource Rules
   • 2.2. Snippets
   • 2.3. Systems
3. Spells
   • 3.1. General Spell Rules
   • 3.2. JASS Specifications
4. Tutorials
   • 4.1. Tutorial Rules
5. Models & Textures
   • 5.1. Model & Texture Rules
   • 5.2. Model Rules
   • 5.3. Texture Rules

Introduction
These are the brand spanking new upload rules as of October 1, 2012. They are exceedingly useful for being citation friendly (broken down into categories, sections, and specific rules) and specific.

If you have not yet uploaded a resource, and are unclear about a rule, please post in the World Editor Help Forum for guidance. Do not be afraid, we will not bite. Also consider posting your resource for critique before submitting it in the Help Forum. Finally, feel free to Private Message myself or the rest of the World Editor moderating team for help or more information. Without further interruption, here are the new rules.

It is the new custom of moderators to post the rules a resource is not following and cite it when commenting on a resource.

New rules may be added without warning but are often accompanied by a reply to this thread summarizing the changes.

1. Tutorials & Resources Section Rules
   • 1.1.General Rules & Intellectual Integrity
     • 1.1.1. All work must be completely original and by the author. Exceptions are made to resources that are modifications of another author's work. Such modifications may be approved if deemed by moderation to be worthy of their own submission.
     • 1.1.2. A resource should only be submitted if complete. Incomplete or partially completed resources are not allowed-do not post anything unfinished here.
     • 1.1.3. Demo maps (.w3x and .w3c files included with the resource) should be uploaded as attachments to this site and are not to be posted as links to other sites, including file sharing sites.
     • 1.1.4. A resource should be completely free of memory leaks.
     • 1.1.5. Do not submit a resource if you do not believe it is worthy of being submitted.
     • 1.1.6. Avoid English mistakes, specifically in spelling and grammar.
     • 1.1.7. Screenshots of resources are encouraged.
     • 1.1.8. Submissions without explanations will be sent to The Graveyard.
     • 1.1.9. Avoid the use of color codes in BBCode. They may be unreadable in different themes.
     • 1.1.10. Do not put demo maps into .zip or .rar archives.
     • 1.1.11. Moderators and Administrators may not approve their own resources.
     • 1.1.12. Resources that do not receive attention after 7 days of being posted may be moved to The Graveyard. Resources that are not even wrong may be sent to The Graveyard immediately by a moderator's judgement.
     • 1.1.13. Resources that remake code already offered by another common library may be required to use that library. This will be judged on a case by case basis.
   • 1.2.Allowed Resources
     • 1.2.1. Resources using the JASS NewGen Packet (JNGP), specifically JASSHelper, are all allowed.
     • 1.2.2.The following additions to JASS are allowed:
       • vJASS
       • ZINC
     • 1.2.3.The following additions to JASS are not allowed:
       • cJASS
2. Systems & Snippets
   • 2.1.Code Resource Rules
     • 2.1.1. All code must be posted in the original post.
     • 2.1.2. No pre-placed units may be utilized.
     • 2.1.3. Be generous in the use of configuration values.
     • 2.1.4. Your resources should require as little modification to a map as possible and be as easy to install as possible.
     • 2.1.5. Resources must be useful. Resources not deemed as useful will be sent to The Graveyard.
     • 2.1.6. Avoid use of blizzard.j functions ("BJs") when possible.
     • 2.1.7. Debug messages must only function in debug mode or be removed before the resource is published.
     • 2.1.8. Code must be readable and follow good coding standards. A good reference document is Bribe's JPAG.
   • 2.2.Snippets
     • 2.2.1. Snippets should serve a function not native to JASS but not large enough to merit a system. Use judgement to differentiate between snippets and systems.
     • 2.2.2. New snippets must be inside libraries if they make use of vJASS.
   • 2.3.Systems
     • 2.3.1. Systems should serve a function not native to JASS but too large to merit a snippet. Use judgement to difference between snippets and systems.
     • 2.3.2. Systems should be made up of one or more libraries if they make use of vJASS.
     • 2.3.3. Do not post systems to solve problems that nobody cares about. Examples include timer systems that are just beating a dead horse.
3. Spells
   • 3.1.General Spell Rules
     • 3.1.1. DotA spell remakes are allowed. The most accurate submissions will be approved.
     • 3.1.2. All spells must come with a demo map. Note 1.1.3.
     • 3.1.3. Spell code must be posted in the original post.
     • 3.1.4.All implementation instructions must be included in the demo map.
       • 3.1.4.1. It is preferred to include installation instructions in the spell's trigger.
     • 3.1.5. All new spells must be MUI (Multi-unit instanceable)
     • 3.1.6. All new spells must be configurable based on level.
   • 3.2.JASS Specifications
     • 3.2.1. Avoid BJs (Usually. Use discretion.)
     • 3.2.2. Avoid pausing the caster. To make a "casting" type spell, use Channel.
4. Tutorials
   • 4.1.Tutorial Rules
     • • 4.1.1. Tutorials should be written professionally, not overuse bolding, underlining, or italicizing, and use proper English.
       • 4.1.2. You must post your entire tutorial in the thread.
       • 4.1.3. Tutorials should be useful.
       • 4.1.4. Tutorials should teach. If you do not want to teach but want to share a method that may be useful for reference, consider submitting a demo map.
       • 4.1.5. A picture is a worth a million words. Consider posting a picture whenever it may be helpful.
5. Models & Textures
   • 5.1.Model & Texture Rules
     • 5.1.1. All files should be stored within a .zip or .rar archive.
     • 5.1.2. All files should have a readme (preferably a text document named "readme.txt") in their root directory to explain implementation.
     • 5.1.3. All submissions must include a picture.
   • 5.2.Model Rules
     • 5.2.1. Include information about all custom animations.
     • 5.2.2. Include detailed importing instructions.
     • 5.2.3. World of Warcraft rips are not acceptable.
     • 5.2.4. Do not be wasteful in model size. WC3 is an old game, there is a point where quality is wasteful.
     • 5.2.5. Models need proper attachment points.
     • 5.2.6. Models should be sufficiently natural looking.
   • 5.3.Texture Rules
     • 5.3.1. Make icons interesting and useful. A recoloring of another icon without any use will be sent to The Graveyard.
     • 5.3.2. Icons requite a DISBTN. Additional forms are preferred but not required.