Killing Floor Workshop Etiquette
Workshop uploads are easier to trust when the page is clear, credited, and searchable. LazyKFWiki’s etiquette note was blunt, but the core idea is simple: respect authors, describe your upload, and do not pollute tags.
Credits
Always credit people whose work you used. That includes map assets, textures, scripts, weapon models, code snippets, screenshots, test help, and old forum packages. If the original author is unknown, say what you know instead of pretending the work is yours.
Useful credit fields:
| Field | Example |
|---|---|
| Original author | Person or team that made the base content. |
| Modified by | Your name if you changed or repackaged it. |
| Testers | People who tested the upload. |
| Assets | Models, textures, sounds, UI, preview art. |
| Links | Steam profile, GitHub, forum thread, archived file origin. |
Description Quality
A one-word Workshop description wastes everyone’s time. Players need to know what the upload is, how to run it, whether it affects perk progression, and whether server admins need extra files.
At minimum, include:
- short purpose;
- map, mutator, weapon, texture, or utility category;
- compatibility notes;
- installation notes;
- known issues;
- whitelist or greylist status if relevant;
- credits and external download links if Workshop extraction fails.
Do not go to the other extreme either. A huge wall of jokes, lore, changelog noise, and unrelated text makes the useful information harder to find. Keep the page structured.
Tags
Tags should describe the upload, not maximize visibility through spam.
| Upload type | Reasonable tags |
|---|---|
| Map | map, plus co-op, single, or multiplayer if needed. |
| Video or ad replacement | misc, art, or another accurate media-related tag. |
| Mutator | mutator, gameplay, or a specific mechanic tag. |
| Weapon pack | weapon, mutator, gameplay if accurate. |
Irrelevant tags make the Workshop harder to search. If everyone tags everything as everything, the tag system stops being useful.
Practical Checklist Before Publishing
- Add credits.
- Write a short summary.
- Explain installation and activation.
- Add compatibility and whitelist notes.
- Use only relevant tags.
- Add screenshots or preview images when the upload is visual.
- Provide a mirror or manual download if server admins need files outside Workshop.