Pre-publication evaluation: Difference between revisions
Jump to navigation
Jump to search
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.
m (→Essentials) |
m (→[[The Ship]]) |
||
Line 77: | Line 77: | ||
* Create a 1024x1024 material (resized from 1280x1024) vgui/map_backgrounds/map_background_<map> | * Create a 1024x1024 material (resized from 1280x1024) vgui/map_backgrounds/map_background_<map> | ||
* Create a 256x128 material vgui/map_previews/map_preview_<map> | * Create a 256x128 material vgui/map_previews/map_preview_<map> | ||
* Create a [[deckplan]] for your Ship. | * Create a [[deckplan]] for your Ship.{{note|There is currently no deckplan designing utility; one will be released with the official SDK.}} | ||
[[Category:Modding]] | [[Category:Modding]] | ||
[[category:Level Design]] | [[category:Level Design]] | ||
[[Category:Publicity & Publication]] | [[Category:Publicity & Publication]] |
Revision as of 14:28, 3 December 2006
Mods

Essentials
- Confirm that the mod has been built under Release rather than Debug.
- Read Steam 3rd Party Mod Support.
- Read Customizing Options: Keyboard.
- A shared soundcache manifest is built.
- A
maplist.txt
file to base the shared soundcache on. - If you're making a multiplayer mod, create a
mapcycle.txt
, referencedby the default value of mapcyclefile ConVar. - Delete excess files
- Files required for each map are in their places.
- Design a default MOTD, or Message of the Day, for the mod in
motd.txt
. - Implementation for all functionalities desired to be in this release is completed.
- 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.
demoheader.tmp
stats.txt
textwindow_temp.html
cfg\banned_user.cfg
cfg\banned_ip.cfg
cfg\config.cfg
scripts\kb_def.lst
scripts\settings.scr
This should be placed in thecfg
folder.bin\client.pdb
bin\server.pdb
- Any *.db files that may have collected from image preview resources.
- Possibly
scene.cache
andmodelsounds.cache
if a lower download size is desired.Note:These files would require rebuilding by the client.
maps/soundcache/*.cache
(do not delete the.manifest
s)Note:These files would require rebuilding by the client.
models/.../*.xbox.vtx
SAVE
directoryscreenshots
directoryreslists
directorymaterials/maps
directoryDownloadLists
directoryNote:These minor files would require rebuilding by the client.
materials/temp
directory
Refining
- Read VGUI2 Programming Best Practices.
- Encrypt weapon scripts using vice.
- Add documentation on mod-specific console commands and console variables.
- Include an icon for the mod if desired in
resource\game.ico
.
- Include the FGD for third-party mod mappers.
- Encrypt
bin\client.dll
with
UPX
Maps
See also: Releasing a Map
Final compile
- Examine the compile log to ensure there are no compile errors, you could also use the Interlopers Compile Checker.
- When you load the map into the game, check the console to ensure there are no errors or warnings.
- Make sure you have compiled the map with Normal VIS and RAD. Do not release a map compiled with Fast VIS or RAD.
- Remember to run the buildcubemaps command in the console before releasing your finished product, otherwise reflections will not work properly.
Distributing custom content
If you have custom models, sounds, textures, or materials, you must either:
- Bundle them into the map BSP file (using Bspzip, Map Analyst, Pakrat, etc.). See
- Add a ".res" Map Resource File to your map release to let the server know there's files that should accompany the BSP when it's downloaded.
If you don't do this, then anyone downloading the map through a server whilst playing will not get your custom content.
Game specific considerations
Counter-Strike: Source
- Create a ".txt" file with the same name as the map. This text will be displayed to players when the map starts. Lines are wrapped.
- Edit the bot Navigation Mesh so bots will behave more intelligently in your map.
- Create a level overview material.
- Run the map with only bots playing, 10 a side, and see whether either side has an outright advantage. There is no substitute for human players, but bots will typically show up the obvious design flaws in a map (poorly positioned meeting points, not enough entrances/exits in critical areas, and so on)
Day of Defeat: Source
- Create a ".txt" file with the same name as the map. This text will be displayed to players when the map starts. Lines are wrapped.
- Create a level overview material.
The Ship
- Create a 1024x1024 material (resized from 1280x1024) vgui/map_backgrounds/map_background_<map>
- Create a 256x128 material vgui/map_previews/map_preview_<map>
- Create a deckplan for your Ship.
Note:There is currently no deckplan designing utility; one will be released with the official SDK.