General SMW ASM Section Submission Guidelines

1. If you are not the author of a resource, do not submit it without permission.
   Explicit permission is required to submit a resource on behalf of another person, user or not. Submitting a resource on behalf of a banned user is forbidden. Technical updates to fix bugs or improve the usability of an already-hosted resource may generally be submitted without author permission; changes that alter a resource's style or core function(s) require permission from all active authors. See Site Rule C1 for further details.
   
   
2. Do not submit simple modifications of an already existing resource.
   Contact a moderator if you would like to tweak the name, description, tags or screenshots of a submission of which you are an author.
   
   
3. Do not include unnecessary files in your submission.
   Avoid including screenshots or excessive folders, or test levels/.bps patches for relatively simple resources.
   
   
4. Name, describe and tag your resource in an appropriate manner.
   Please give your resource and its .zip file reasonably descriptive names, and be reasonably clear when adding the description and tags. Useless, inappropriate or misleading information may be altered or removed at a moderator's discretion.
   
   
5. Please include a simple screenshot or (preferably) .gif with your submission demonstrating your resource in action, if applicable.
   Demo images should ideally offer an easily understood depiction of how the resource behaves, and should exclude extraneous elements such as elaborately decorated levels, unrelated sprites or abilities, etc. Submitting more than one .gif/image to demonstrate the complete function of your resource is highly encouraged (sprite extra bit differences, fix patch before/after behavior, etc.). Images are unnecessary for resources with no visual component.
   
   
6. Please make sure you have thoroughly tested your resource prior to submission.
   Be sure to test your resource in all formats it claims to support - if your resource is written for LoROM and SA-1, then test your resource on both.
   
   
7. Ensure that all files included with your submission are ready to use as provided.
   Palette files should be of the .palmask format. GFX files shouldn't contain any unrelated graphics, and your resource should by default reference all included graphics as submitted. If your resource includes a sample level, it should reference any ExGFX or other files as named.
   
   
8. If submitting an update to a previously accepted resource, please include an appropriate version number.
   A version number may be assigned at a moderator's discretion if none is provided by the author.
   
   
9. If your resource is designed for SA-1 compatibility, make sure to identify the ROM type accordingly.
   For resources compatible with both LoROM and SA-1, correct mapping must be automatically detected and applied:
   Example SA-1/LoROM Check: Show/Hide
   
   

   Code

   	!dp = $0000
   	!addr = $0000
   	!bank = $800000
   	!sa1 = 0
   if read1($00FFD5) == $23
   	sa1rom
   	!dp = $3000
   	!addr = $6000
   	!bank = $000000
   	!sa1 = 1
   endif

   
   Code is subsequently adapted using the defines

   !sa1

   ,

   !dp

   ,

   !addr

   and

   !bank

   .
   
   
   
10. Your resource may be gently modified during moderation.
    A moderator may make very small technical changes to a submission, generally to fix small errors that lead to a bug or crash as discovered during moderation (for example, a missing SA-1 conversion). This is done as a courtesy to spare the author the effort of resubmitting after making a trivial fix. Any changes made are documented by the moderator in a comment on the resource and may be freely challenged by the author(s) if desired. Stylistic changes or changes that alter the core function of a resource will not be made in this way.

For a list of tags which you can use in your submission, see this page.