Pre-publication evaluation

Note:The following items are numbered to help you keep track of where you are in this process, not as an order for a specific procedure.

Essentials

1. Confirm that the mod has been built under Release rather than Debug.
2. Read Steam 3rd Party Mod Support.
3. Read Customizing Options: Keyboard.
4. If a maplist.txt exists, rename it to mapcycle.txt, the default for mapcyclefile ConVar.
5. Delete excess files
6. Files required for each map are in their places.
7. Design a default MOTD, or Message of the Day, for the mod in motd.txt.
8. A shared soundcache manifest is built.
9. Implementation for all functionalities desired to be in this release is completed.
10. Remove source folders (mapsrc, materialsrc, modelsrc)

Excess Files

If one of the following files or directories exist, deletion would make the mod's installation tidier.

1. demoheader.tmp
2. stats.txt
3. textwindow_temp.html
4. cfg\banned_user.cfg
5. cfg\banned_ip.cfg
6. cfg\config.cfg
7. scripts\kb_def.lst
8. scripts\settings.scr
   This should be placed in the cfg folder.
9. bin\client.pdb
10. bin\server.pdb
11. Any *.db files that may have collected from image preview resources.
12. Possibly scene.cache and modelsounds.cache if a lower download size is desired.
    
    Note:These files would require rebuilding by the client.
13. maps/soundcache/*.cache (do not delete the .manifests)
    
    Note:These files would require rebuilding by the client.
14. SAVE directory
15. screenshots directory
16. reslists directory
17. materials/maps directory
18. DownloadLists directory
    
    Note:These minor files would require rebuilding by the client.

Refining

1. Read VGUI2 Programming Best Practices.
2. Encrypt weapon scripts using vice.
3. Add documentation on mod-specific console commands and console variables.
4. Include an icon for the mod if desired in resource\game.ico.
5. Include the FGD for third-party mod mappers.