{sticky}[READ THIS] SFX Shoppe Submission Rules{/sticky}

If you are submitting a special effect to the Realm667 SFX Shoppe, please read these rules, and follow the submission template. It makes the job of adding them so much easier, and if a submission doesn't follow the rules, it won't be added until it does, or it could be flat-out rejected.

General Submission Rules
can be found on the left side of the page in the info box called "SUBMISSION RULES". Make sure to check the mouseover-tooltips for details. Categorie-specific submission rules can be found below.

Category-Specific Rules

• Use paletted PNGs for sprites. Since PNGs ignore palette, or adapt to the IWad being used, it makes it much easier to use the monsters in different games. Make sure the sprites are paletted (256 color palette).
• Use OGG or FLAC for sounds. They are much more compressed formats without any (noticable) quality loss. There are several programs to convert to one of these formats, such as Audacity.
• Make sure it is a pk3 file placed inside a zip. Sort your content into apropriate folders so it is easier for modders to implement your weapon into their mod.
• Include GLDefs, if necessary. If you can't write them yourself, then you can have someone else write them.
• Include information, from the template below, in both the submission post, and in the wad itself, in an INFO lump.
• Include credits. Like information, include credit information (from the template) in both the submission post and in the wad itself, in a CREDITS lump.
• Include documentation. Use a DOCUMENT lump to explain how the SFX is supposed to be used (placement, argument use, etc.). Trust me, figuring that out yourself is NOT fun.
• ACS and ZSCRIPT allowed, however, it must be open-source (include the source code in its own lump). Leave comments saying how things work. Additionally, try to use named scripts, to reduce the chances that they'll conflict with scripts on a map, for example.
• Follow the template, below, in your submission post.
• Tag it as a submission. Use the right topic icons with an apropriate prefix, like the blue S icon with [SUBMISSION] in your title.
• If you are updating something already on the repo, tag it as an update. Use the right topic icon here as well with the purple U and a [UPDATE] prefix

Submission Template
Information:
Type: What kind of spawner is it? Unlike the Armory and Beastiary, this is more like a short description.
Connections: Does this SFX have any connections to other SFX? Does it use any of the same actors as another spawner? Say what it is, or if it doesn't, just say "None."
Spawn Offsets: If the SFX is a spawner (rain, snow, etc.), what are the offsets it spawns in? Use N/A if it doesn't apply to this SFX, and Arguments if it is controlled by arguments set in the editor.
Spawn Ceiling: Does it spawn on the ceiling?
Variants: How many different types are there, and what are the different types?
Summon: What is the actor's exact name?
Brightmaps: Does it have brightmaps?
Actor modification: Does it require modification to an existing actor to work properly? Custom actor states and virtual function overrides are an example of such modification.
ACS: Does the submission use ACS, with LoadACS?

Credits:
Code: Who wrote the code?
GLDefs: Who wrote the GLDefs? If there are none, just leave it out.
Sounds: Where did the sounds come from, and who edited them?
Sprites: Where did the original sprites come from? Who made them?
Sprite Edit: If the sprites were edited from something else, who edited them?
Idea Base: If your SFX was inspired by something, what was it inspired by?

Description:
People prefer to know exactly what they're downloading, before they download it.

Screenshots:
Put two preview screenshots here. Use an image upload site like Imgur

Download Link:
Either upload to a site like DropBox or Google Drive, or just attach it to your post. Please choose one that shouldn't expire, because it might expire before we can add it.