Resource list (Source): Difference between revisions
Jump to navigation
Jump to search
Warning:Clients can choose to not loose sound files, or not download any files except the BSP itself! Prefer using BSPZIP or similar to pack custom content into the map when possible.
Tip:.txt, .res, .ain, and .nav files with the same name as the map are automatically pushed, and don't need to be included.
Tip:If a .mdl file is listed, .vvd, .ani, .dx80.vtx, .dx90.vtx, .sw.vtx, .phy, and .jpg files with the same name and path as the .mdl will also automatically be pushed.
m (→See also) |
No edit summary |
||
(19 intermediate revisions by 9 users not shown) | |||
Line 1: | Line 1: | ||
{{LanguageBar}} | |||
{{tabs|Resource list|goldsrc=true|source=true}} | |||
A '''Resource list''' (<code>.res</code> file) accompanies a map. When the map is running, it directs the server to push arbitrary files to connecting clients. | A '''Resource list''' (<code>.res</code> 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. | 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. | ||
{{ | {{warning|Clients can choose to not loose sound files, or not download any files except the BSP itself! Prefer using [[BSPZIP]] or similar to pack custom content into the map when possible.}} | ||
== Example == | == Example == | ||
Line 9: | Line 11: | ||
Resources | Resources | ||
{ | { | ||
materials/vdc/some_material.vmt file | "materials/vdc/some_material.vmt" "file" | ||
materials/vdc/some_material.vtf file | "materials/vdc/some_material.vtf" "file" | ||
} | } | ||
{{tip|.txt, .res, .ain, and .nav files with the same name as the map are automatically pushed, and don't need to be included.}} | |||
{{tip|If a .mdl file is listed, .vvd, .ani, .dx80.vtx, .dx90.vtx, .sw.vtx, .phy, and .jpg files with the same name and path as the .mdl will also automatically be pushed.}} | |||
{{todo|What data types are there beside <code>file</code>? It seems to not matter what type is specified, as long as the type definition isn't empty or absent.}} | |||
{{todo|Can a .res be safely [[BSPZIP]]ped?}} | |||
{{ | == Files == | ||
A resource list must be located in the {{path|maps}} folder with the same name as the associated [[BSP]]. | |||
==VGUI Resource Files== | |||
Some resource files can be found in your /resource folder. Most of them are for [[VGUI]]. For more information, see [[RES file (VGUI)]]. | |||
== | |||
== See also == | == See also == | ||
*[[VGUI2]] | |||
*[[BSPZIP]] | *[[BSPZIP]] | ||
*{{vide|4.1}} | |||
*[[PackBSP]] | *[[PackBSP]] | ||
*[[Map Analyst]] | *[[Map Analyst]] | ||
*[[Pakrat]] | *[[Pakrat]] | ||
*[[Map_Resource_Extractor]] | |||
[[Category:Level Design]] | |||
[[Category: | [[Category:File formats]] | ||
[[Category:Files]] |
Latest revision as of 21:03, 27 June 2025
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.

Example
Resources { "materials/vdc/some_material.vmt" "file" "materials/vdc/some_material.vtf" "file" }


Todo: What data types are there beside
file
? It seems to not matter what type is specified, as long as the type definition isn't empty or absent.Todo: Can a .res be safely BSPZIPped?
Files
A resource list must be located in the maps
folder with the same name as the associated BSP.
VGUI Resource Files
Some resource files can be found in your /resource folder. Most of them are for VGUI. For more information, see RES file (VGUI).