Resource list (Source): Difference between revisions
Jump to navigation
Jump to search
Note:A resource list must be located in the
Tip:.txt, .res, .ain and .nav files with the same name as the map are automatically pushed, and don't need to be included.
m (→Tools) |
(Removed →Tools: section) |
||
Line 19: | Line 19: | ||
*{{todo|What data types are there beside <code>file</code>?}} | *{{todo|What data types are there beside <code>file</code>?}} | ||
*{{todo|Can a .res be safely [[BSPZIP]]ped?}} | *{{todo|Can a .res be safely [[BSPZIP]]ped?}} | ||
== See also == | == See also == |
Revision as of 10:39, 13 December 2011
A Resource list (.res
file) accompanies a map. When the map is running, it directs the server to push arbitrary files to connecting clients.
While it is generally preferable to achieve this by using BSPZIP to embed the files into the map itself, there are occasional situations where only loose files and a .res will work.

\maps
folder with the same name as the associated BSP.Example
Resources { materials/vdc/some_material.vmt file materials/vdc/some_material.vtf file }
Remember to enclose any paths containing spaces with "quote marks" (e.g. "materials/oh look some spaces/material.vtf" file
).

- Todo: What data types are there beside
file
? - Todo: Can a .res be safely BSPZIPped?