If you are submitting a weapon to the Realm667 Armory, 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.

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 wad file placed inside a zip. Not a weapon in a pk3 format.
• 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.
• Custom ammo IS allowed, but make sure you include the ammo in question, and remember to say that it's custom, in the info.
• No KeyConf or Player.WeaponSlot. Leave that up to modders using the weapons. Weapon.SlotNumber is more acceptable, but it should still be left to the modder. For testing the weapons without binding them to a slot, use the "Use *WeaponName*" command, in the console, where *WeaponName* is the summon name for the weapon.
• Custom pain and death states on players and monsters are allowed to a degree. If you use these, include a modified monster (Custom Doom Imp with the pain state, for example) as a demonstration. DO NOT go overboard with these, however. Include instructions in the INFO lump, as well.
• ACS IS allowed, however, it must be open-source (include a copy of the script(s) in the INFO lump). Try to keep your ACS simple, and especially 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.
• If you are updating something already on the Armory, tag it as an update.

Submission Template:

Small addition to the rules:

Why no Weapon.SlotNumber? (The Player property wouldn't be practical at all as it implies redefining the player class which requires KEYCONF, and can thus be ignored.) It's like saying "no doomednum, leave that to modders" or "no spawnid, leave that to modders". They're perfectly able to edit or delete that line themselves, at least as able to do that as they're able to add it.

Well, I might append the rule, saying that Weapon.SlotNumber is okay, but optional.


Actually, I leave that to the modders in my submissions, too.

Uff, good.

Not so long time ago I rid of keyconf and used slotnumbers .

FFUUUUUUUUUU...

Why is that a problem?

Because letting modders do it themselves is asking too much? Because one is too lazy to remove testing parameters prior to submission? Because it's easier to post... than to do these things?

This is a ridiculous way to express your disapproval of a rule. It contributes nothing. Want the rule changed? Say so in a more respectable manner. Raging will get you nowhere.

Example:

ok, but that would be somewhat uncomfortable
whenever i download a weapon, i write {IDKFA + slotnumber }
but i suppose there's nothing wrong