Killing Floor Workshop BBCode Template

A good Workshop page is short enough to scan and detailed enough for players and admins. LazyKFWiki’s template centers on practical information rather than decoration.

Required Sections

Section	What to include
General information	What the upload does in a few words.
Whitelist status	Whether perks and achievements can progress.
Technical information	Package names, class names, config files, and important settings.
Compatibility	What it works with and what it conflicts with.
Installation	Separate instructions for clients and server admins if needed.
Download links	Workshop plus direct GitHub/forum mirrors if extraction fails.
Credits	Authors, testers, artists, file origin packages, and related links.

Minimal BBCode Skeleton

[h1][b]General Information[/b][/h1]
Short description of what the upload does.

[h1][b]Whitelist Status[/b][/h1]
Dedicated server: ...
Listen server: ...
Solo: ...

[h1][b]Technical Information[/b][/h1]
Package:
Mutator class:
Config file:

[h1][b]Compatibility[/b][/h1]
Known compatible and incompatible packages.

[h1][b]Installation[/b][/h1]
Client steps.
Server admin steps.

[h1][b]Download Links[/b][/h1]
Workshop:
GitHub or forum mirror:

[h1][b]Credits[/b][/h1]
Author:
Testers:
Assets:

Whitelist Status Examples

Players still care about stats. If your upload affects progression, say so clearly:

Context	Example note
Dedicated server	All clients can gain perks and achievements if the package is allowed.
Listen server	Clients may progress, but the host can be greylisted depending on the mod.
Solo	Many non-whitelisted gameplay mods stop progression.

Credit Links

Steam vanity profile names can change. When linking credits, convert vanity URLs to stable SteamID64 profile URLs using a tool such as steamid.io.