Empires Wiki - User contributions [en]

Basic Classic Map

2026-04-06T17:07:48Z

Awpolt:

{{MappingDocumentation}}

'''Overview'''

''Please ensure that you have [[Configuring Hammer for Empires|properly configured Hammer for Empires]] before proceeding.''

This guide is for showing you how to set up the Classic style map seen in most Empires maps. I made it because when I wanted to find out how to make one, I found all of the required information I needed was in several different Wiki documents, and it wasn't comprehensive or straightforward or well signposted. This tutorial is written with beginners in mind (including beginners to the Hammer editor), so if what is being talked about is too simple... skip it!

__TOC__

== Classic Map Checklist ==

To get a Classic map in Empires to function on a basic level (i.e., not necessarily look pretty, but work nonetheless), you will need the following:

=== Entities ===
* '''emp_imp_commander'''
A Commander vehicle for the Brenodi Empire
* '''emp_nf_commander'''
A Commander vehicle for the Northern Faction
* '''emp_building_imp_barracks'''
A starting spawn for the Brenodi Empire
* '''emp_building_nf_barracks'''
A starting spawn for the Northern Faction
* 2 x '''emp_res_node'''
The location where a Refinery can be dropped to give resources to either team (recommended)
* 2 x '''emp_resource_point_prop'''
The physical representation of the resource node (recommended)
* '''emp_info_params'''
The game settings for your map
* '''emp_info_map_overview'''
The fixed camera location that gives you your first view of the map when it finishes loading
* '''info_node'''
Even if you leave it blank, this hardcodes the AI node graph into your map. Without one, there can be delays connecting to a server with your map.

=== Resource Files ===
* '''emp_<yourmapname>.vtf'''
An image file of the map overview.
* '''emp_<yourmapname>.vmt'''
A text file that tells the game about the above file
* '''emp_<yourmapname>.txt'''
A script file that contains a few pieces of important information about your map.

== First steps in Hammer ==

1. To start with, load up the '''Source SDK''' (under "Tools" in Steam) and open the '''Hammer''' editor. This is the software used to create maps for any Source-powered game or mod.

Once you have loaded up Hammer, your screen should look like this:

[[Image:Step 1.png|medium|step 1]]

2. Create a new map by going '''File -> New'''. The screen should now look like this:

[[Image:Step 2.png|medium|step 2]]

=== Make a brush with the block tool ===

3. Now select the '''block tool''' on the left hand side.

[[Image:Step 3.png|medium|step 3]]

4. Move your mouse to the '''top right viewport''' (overhead view) and use the mouse wheel to zoom in and out. To move the view, hold the space bar and drag with the left mouse button. When you are satisfied that you can navigate in this view, drag out a square using the left mouse button with the '''block tool''' selected. Make it around 4096 by 4096 units. You will see a white outline where the block will be created. Press return on your keyboard to place the block.

[[Image:Step 4.png|medium|step 4]]

5. After you have done this, the box should appear in the 3D view (top left viewport).

[[Image:Step 5.png|medium|step 5]]

=== Moving around in the 3D view ===

6. The next thing to do is to get used to moving around in the 3D view, there are two equally useful methods for doing this.

i) With the '''camera tool''' selected, click and hold the left mouse button in the 3D view. This rotates your view on the spot. The right mouse button moves your view left, right, up and down (relative to where you are looking). Holding both mouse buttons at once zooms the view in and out.

ii) Alternatively, you can move about freely without having to use the camera tool (i.e. when you want to use another tool and still move the camera to help you see what you're doing). All you have to do is move your mouse over the 3D viewport after which you will be able to use a number of keys to move the camera.
* Zoom in and out with the '''W''' and '''S''' keys
* Strafe left and right with the '''A''' and '''D''' keys
* Direct the camera up, down, left and right with the '''arrow keys'''

Once you are comfortable with moving around, move on to step 6.5.

6.1. At this stage, your newly placed block will look something like this. This is the default white texture, your block may be appear different to the picture, but it doesn't matter because we are about to choose and apply a different texture.

[[Image:Step 6.5.png|medium|step 6.5]]

=== Applying Textures ===

6.2. This makes it hard to see what you're doing, and doesn't look all that good either, so we are going to put a different texture on it. Half-Life 2 comes with many different textures, most of which can be used for this kind of object. In this case, we're going to make the visible surface look like grass. To find your texture, select browse at the right hand side.

[[Image:Step 6.6.png|medium|step 6.6]]

6.3. Now type in the filter "grass".

[[Image:Step 6.7.png|medium|step 6.7]]

6.4. Select the specific texture that you want by double clicking it. You will then be brought back to the editing screen, where you should now select your block and click the apply texture button.

[[Image:Step 6.8.png|medium|step 6.8]]

{{Tip|Any non visible faces of the block should be textured in '''nodraw'''. This is a special texture that means these faces will not be drawn in the map and therefore are not taking up any memory unneccessarily. It is an essential technique for optimising your maps (especially in a mod with such open spaces such as Empires), so whether you are new to Hammer or not, get into the habit of culling all your backfaces with nodraw and your maps will be less laggy. You can find the 'nodraw' texture by searching for 'nodraw' just like you did with the grass texture.}}

=== Adding a Skybox ===

13. The next thing to now do is to make the skybox. For this tutorial we are going to be using a 2D skybox, as this is much simpler than a 3D one. Effectively all we are going to do is use the block tool to make a box around the map, and use the '''skybox''' texture on the inner surfaces to turn it into sky. Here is Supaste's method, which starts making a skybox from the edge of our map in the top view.

[[Image:Step 13.png|medium|step 13]]

{{Tip|The player will only be able to see the inner sides of the skybox brush, so don't forget to texture the outside faces in in '''nodraw''' and not '''skybox''' or any other texture.}}

14. Now you have one side of your skybox (untextured) but it is not the right height so you need to go into a different 2D view and begin resizing it. I would say that about 1087 units high would be enough, but keep in mind that the commander can only move inside this box. If it's too short, his view of the battle will be severely limited. Also remember that when making these bits it sometimes helps you later on to have blocks meet at corners rather then edges (as shown in bottem right 2D view).

[[Image:Step 14.png|medium|step 14]]

15. I think its a good time to tell you how to copy a block as this comes in useful when doing lots of brushwork. To copy a block, all you have to do is select it and drag it with your mouse in a 2D view whilst holding the shift key. Try doing this with the block we made in step 13. Also you can delete blocks you have made by selecting them and pressing the 'delete key'

[[Image:Step 15.png|medium|step 15]]

16. Now do the same with the other two sides.

[[Image:Step 16.png|medium|step 16]]

17. Now we need to add a ceiling, start by dragging a box in the top 2D view the same size and shape as the floor then bring it up to meet the corners of the side of your map.

[[Image:Step 17.png|medium|step 17]]

18. You will want to texture the ceiling and the walls, texture them as skyboxes this is done in the same way as how we textured the floor only you use the skybox texture search 'skybox' or 'tools' to find it.

[[Image:Step 18.png|medium|step 18]]

== Placing the required entities ==

7. Now we are going to place some entities. These are what really make the map function. Some examples would be the barracks and the command vehicles. To begin, click the '''entity tool''' (the one that looks like a lightbulb).

[[Image:Step 7.png|medium|step 7]]

=== Barracks ===

8. You will notice that when you do this, at the right hand side of the screen, two previously greyed out dropdown boxes will now become available. The top one is used to decide what you are placing (in this case, leave it on "Entities") and the bottom box chooses what you are placing out of that category. The other options relate to prefabs, and are not relevant to this tutorial. We will be using the bottom box to select the Brenodi barracks entity. This is named '''emp_building_imp_barracks'''.

[[Image:Step 8.png|medium|step 8]]

9. The easiest way to place entities in the map is via the 3D view. Clicking anywhere on your ground, a barracks should appear. Chances are, it hasn't been placed exactly how you want it (it is probably too high) so this means we will have to use the 2D views to position it how we want it.

[[Image:Step 9.png|medium|step 9]]

10. To move a object in the 2D view simply select it (by clicking on it in the 3D view), and drag it around. Notice it will snap to the grid. In order to change the grid size, use the '[' and ']' keys. This works exactly the same in all of the 2D views.

11. Once you have positioned the Brenodi barracks where you want it, do the same with the NF one ('''emp_building_nf_barracks''')...

[[Image:Step 11.png|medium|step 11]]

=== Command Vehicles ===

12. Now we need to add the command vehicles ('''emp_imp_commander''') and ('''emp_nf_commander'''). This works exactly the same as the barracks, but leave them ever so slightly above the ground so that when the game starts they drop to the floor rather than being stuck in the ground. The Brenodi CV's front wheels will look all screwed up; dont worry, this will correct itself in-game.

[[Image:Step 12.png|medium|step 12]]

=== Resource Nodes ===

Also required are at least 2 resource nodes so both teams are capable of accruing resources at the same time. I would recommend reading Supaste's [[Resource Nodes]] guide for this, as res nodes are a two-step process (you need the invisible entity that allows a Refinery to be built at a location, and you need the visible marker to tell players and Commanders where the nodes actually are).

=== Map Parameters ===

19. Next we need to add '''emp_info_params''' this a entity that tells hammer how many resources each team starts with, how many reinforcements each team has and various other things. When you place it it should appear as a red cube when selected and a purple cube when not selected. To edit the propities of it double click it in the 3D view. (Dont forget if you want to play this map set the resources quite high as resource nodes are not in this tutorial)

[[Image:Step 19.png|medium|step 19]]

=== Creating a fixed Overview camera ===

20. Lastly we need to add a '''emp_info_map_overview''' entity which defines the view you get of the map when you firt join and are setting up your class and waiting for the Commander vote to end. Go through the same steps as before for creating this entity.

[[Image:Step 20.png|medium|step 20]]

== Compile your Map ==

You need to compile your map to turn it from a source file used for editing into a map file that can be played as a level in a game. Go to '''File -> Runmap''' and hit ok to compile! If you have any errors, ask in the [http://forums.empiresmod.com/ Empires Mapping Forums] (registration required).

== Map Resources ==

This section contains the info I had trouble finding when I came to map for Empires. Basically, without a set of additional resource files for your map, it won't run properly (you won't even be able to spawn!).

Here is a list of those files with a rundown of what they actually do:
* '''emp_<yourmapname>.vtf'''
An image file of the map overview. If you don't want to make one of these yet because your map is in the preliminary stages, you should be able to copy one from another map to use temporarily (just remember to rename it to match your map name!).
* '''emp_<yourmapname>.vmt'''
A text file that tells the game what kind of image type the above is (i.e. it tells the game that it's a map overview and not some other kind of special texture).
* '''emp_<yourmapname>.txt'''
A script file that contains a few pieces of important information about your map. First off it translates movements in XY axes of the game world to movements on the map. If the numbers are off then spawn points, vehicles and buildings won't appear in the correct locations on the map.

If you want to create your own minimap now [http://forums.empiresmod.com/index.php?threads/4200 there is a good guide] on the Empires forums.

{{Note|All your files must be named the same as your map. So if your map is '''emp_testmap.bsp''', your resource files should be '''emp_testmap.vtf''', '''emp_testmap.vmt''' and '''emp_testmap.txt'''. The files must also be placed in the correct folders (see [[Setting Up Map Resources]]).}}

{{Tip|I would recommend immediately saving each session's work as '''emp_<yourmapname>_<version number>''' each time you open up Hammer so you can fall back to previous versions if you need to. Then, whenever you compile a version, jump into the Empires/maps folder, delete '''emp_<yourmapname>''' and rename '''emp_<yourmapname>_<version number>''' to '''emp_<yourmapname>'''. Your newly compiled version will now match the resource files and you can boot the map in Empires to check it out!}}

quick and dirty temp links:

[[Basic Mapping]] (steps 3 & 4)

== Conclusion and Credits ==

That should be it!

If you have any questions, do not hesitate to ask in the [http://forums.empiresmod.com/ Empires Mapping Forums] (registration required)

Tutorial adapted from Supaste's [[Basic Conquest Map]] guide (please see that guide for its credits list). The images contained here were created for the aforementioned guide. Some minor alterations to wording and presentation have been made according to my taste, as well as some corrections and additional tips and sections.

[[Category:Mapping|Basic Conquest Map]]

== Links and References ==
* '''[[Configuring Hammer for Empires]]'''
How to setup the Hammer level editor so that you can make and compile maps ready to run them in Empires.
* '''[http://forums.empiresmod.com/ Empires Mapping Forums]''' (registration required)
Home of the Empires Mapping Community . Ask questions, share advice and present your work to your peers for constructive criticism.
* '''[[Resource nodes]]'''
Guide to creating res nodes, by Supaste.
* '''[[Setting Up Map Resources]]'''
An in-depth guide to how to create and edit your resource files, by Kylegar et al.
* '''[http://forums.empiresmod.com/index.php?threads/4200 Guide to Creating Minimaps]'''
Full guide to creating clean and accurate minimaps, by Jcw87.

Bots and NPCs

2026-04-05T22:38:32Z

Awpolt:

{{MappingDocumentation}}
__NOTOC__

This will be periodically updated with information about NPCs and Bots (fake players).

NPC

This refers to non-player AI controlled entities.

NPC Notes:
* NPCs will automatically go to and attempt capture available control points
* NPCs shoot at valid targets 2000 units away and in line of sight

===== Bots =====

This refers to fake clients, that are simulated server side.

<hr>

==== Adding NPCs to maps ====
Added to hammer are 2 test NPC entities, these should work on any map however their functionality is limited. To ensure correct operation with your map, i have created a checklist of things that need to be done.

'''NPC checklist:'''
* Your map needs to be compiled with a version of empires later than [[Version/2.15.x|2.15.3]].
* Your map needs a navigation mesh created, see https://developer.valvesoftware.com/wiki/Navigation_Meshes
* Your capture points need to be numbered correctly, capture point number 0 will not work with NPCs.
<hr>

====NPC Entity List:====
* [[npc_human_nf]]
* [[npc_human_be]]
* [[npc_grenadier_nf]]
* [[npc_grenadier_be]]

==Debugging NPCs==
=== Console Commands ===
* '''ai_debug_emp_paths''' : shows the actual paths the bots are currently following, blue for BE, red for NF
* '''ai_debug_emp_cap_points''' : bots print which capture point they are trying to go to

== Blocking Navigation ==
[[Image:Nav blocker setup 1.png|thumb|'''Step 1:''' The ''func_nav_blocker'' is textured here with '''tools/toolstrigger''', and covers the extent of the area I want to block]]

[[Image:Nav blocker setup 2.png|thumb|'''Step 2:''' The ''func_nav_blocker'' is configured with the team to block for, and a name so that it can be activated by other entities]]

[[Image:Logic auto setup 1.png|thumb|'''Step 3:''' A ''logic_auto'' is created so that we can trigger our ''func_nav_blocker'' to start blocking]]

[[Image:Logic auto setup 2.png|thumb|'''Step 4:''' The ''logic_auto'' is configured to fire when the game is runing on a PC, at game start time]]

[[Image:Logic auto setup 3.png|thumb|'''Step 5:''' The ''logic_auto'' has it's output set so that it triggers the ''BlockNav'' input on our previous ''func_nav_blocker'' entity]]

[[Image:Nav blocker setup 3.png|thumb|'''Step 6:''' Finally, checking that the ''func_nav_blocker'' has detected the input correctly coming from the ''logic_auto'']]

# First you need to create a ''func_nav_blocker'' entity covering the extent of the area you wish to block, and textured with '''tools/toolstrigger'''.
# Configure the ''func_nav_blocker'' settings, and choose whch team(s) you wish to block for and give it a name so that it can be activataed by another entity.
# Create an entity to use to activate the ''func_nav_blocker'', here we use ''logic_auto'' but any entity can be used here
# Configure the ''logic_auto'' so that it triggers on game start
# Set the ''logic_auto'''s output to fire the '''BlockNav''' input on the ''func_nav_blocker''
# Finally, check that the ''func_nav_blocker'' has the correct input coming in

''' The images to the side of the page show what it should look like'''.

= Common NPC FAQs =
* The NPCs aren't moving anywhere, only occasionally shuffling forwards or standing there.
** This is most likely because there is no navigation mesh, or capturable flags available.

[[Category: Mapping]]

Skyboxes

2026-04-05T22:21:31Z

Awpolt:

{{MappingDocumentation}}
__NOTOC__

== Skyboxes and Recommended Light Settings ==
This section lists skyboxes used in Empires along with their recommended lighting configurations.
----

=== skybox/sky92 ===

==== light_environment ====

* '''Pitch:''' -20
* '''BrightnessHDR:''' 255 193 141 300
* '''AmbientHDR:''' 107 113 55 85
* '''SunSpreadAngle:''' 2

==== shadow_control ====

* '''Rotation (Y Z X):''' 20 180 0
* '''Shadow Color:''' 140 138 100
* '''Maximum Distance:''' 800

==== env_tonemap_controller ====

* '''ExposureMin:''' 0
* '''ExposureMax:''' 1.3
* '''BloomScale:''' 0.6

==== env_sun ====

* '''Pitch:''' -5
* '''Sun Color:''' 249 216 147

==== env_fog_controller ====

* '''Primary Fog Color:''' 180 85 1
* '''Secondary Fog Color:''' 80 50 20
* '''Fog Start:''' 8000
* '''Fog End:''' 20000
* '''Interpolate Time:''' 10
* '''Far Z Clip Plane:''' 20000

----

== Additional Sky References ==
For more sky options and configurations, see:

https://developer.valvesoftware.com/wiki/Sky_List#Half-Life_2

Dimensions

2026-04-05T22:16:56Z

Awpolt:

{{MappingDocumentation}}
__NOTOC__

== Player Movement and Size Limits ==

=== Maximum Map Dimensions ===
Empires maps often approach the maximum size limits of the Source engine, so careful planning and optimization are essential when designing large environments.
----

=== Player Movement Limits ===

* '''Maximum reachable height:''' Determined by jump mechanics and map geometry.
* '''Crouch jump height (from standing):''' '''64 units'''

This value is useful when designing obstacles, ledges, and accessible areas to ensure proper player navigation.{{fixme|Page needs updating. Some dimensions are missing! }}
[[Category: Mapping]]

Modeling

2026-04-05T20:00:52Z

Awpolt: /* Community Props and Models */

{{Sitenav|Moddeling}}

== Current props and models ==
* [[Vehicles]]
* [[Buildings]]
* [[Natural Props]]
* [[Artificial Props]]

== Community Props and Models ==

* [[Tutorial: Create your own models]]
* [[Tutorial: Edit existing models]]
* [[Tutorial: Add custom gibs to your model]]

== Modeling Programs ==
* 3D Studio Max (Commercial)
* [http://www.softimage.com/products/modtool/ XSI] (Freeware)
* [http://www.milkshape3d.com/ Milkshape] (Shareware)
* [http://www.misfitcode.com/misfitmodel3d/ Misfit Model 3D] (Freeware)
* [http://www.blender.org/ Blender] (Open Source)

== Royalty Free Models ==
* Trees: https://www.turbosquid.com/3d-model/free/trees

== Needed Models ==
=== Buildings ===
* Windows
* Walls
* Doors
* Cranes
* Bunkers & lookout tower
=== Decorative ===
* Random cool looking stuff
* Infantry cover
* Scene enhancers
* Giant letters -- to spell custom things on rooftops

=== Road Signs ===
* Just a variety of general purpose signs.

=== Statues ===
* Patriotic statues
* Artsy statues (look around local musuems for inspiration)
* Famous people from Empires (read history)

=== Modelling Pipeline ===
https://wiki.empiresmod.com/Modelling_Pipeline

[[Category: Modeling]]

Modeling

2026-04-05T19:12:29Z

Awpolt:

{{Sitenav|Moddeling}}

== Current props and models ==
* [[Vehicles]]
* [[Buildings]]
* [[Natural Props]]
* [[Artificial Props]]

== Community Props and Models ==

* [http://wiki.empiresmod.com/index.php?title=Fun_projects#Modeling_.26_Concept_Art Models to work on]
* [[Tutorial: Create your own models]]
* [[Tutorial: Edit existing models]]
* [[Tutorial: Add custom gibs to your model]]

== Modeling Programs ==
* 3D Studio Max (Commercial)
* [http://www.softimage.com/products/modtool/ XSI] (Freeware)
* [http://www.milkshape3d.com/ Milkshape] (Shareware)
* [http://www.misfitcode.com/misfitmodel3d/ Misfit Model 3D] (Freeware)
* [http://www.blender.org/ Blender] (Open Source)

== Royalty Free Models ==
* Trees: https://www.turbosquid.com/3d-model/free/trees

== Needed Models ==
=== Buildings ===
* Windows
* Walls
* Doors
* Cranes
* Bunkers & lookout tower
=== Decorative ===
* Random cool looking stuff
* Infantry cover
* Scene enhancers
* Giant letters -- to spell custom things on rooftops

=== Road Signs ===
* Just a variety of general purpose signs.

=== Statues ===
* Patriotic statues
* Artsy statues (look around local musuems for inspiration)
* Famous people from Empires (read history)

=== Modelling Pipeline ===
https://wiki.empiresmod.com/Modelling_Pipeline

[[Category: Modeling]]

Modelling Pipeline

2026-04-05T19:09:03Z

Awpolt:

Documentation of the current modelling pipeline.

{{Abandoned}}

== Current Texture Pipeline ==

# Create your image.
# Import the image into '''VTFEdit'''.
# Select the appropriate settings.
# Save the file in '''.vtf''' format.

'''Note:''' Steps 2–4 must be repeated each time the image is edited.
----

== Current Model Pipeline (Blender) ==

# Install '''Blender Source Tools'''.
# Create your model in '''Blender'''.
# Export the model to the correct file format.
# Create a '''.qc''' file.
# Compile the model by running the '''.qc''' file through '''studiomdl'''.
# Place textures in the correct folder ''(only when textures change — see Texture Pipeline)''.
# Place materials in the correct folder ''(only when materials change)''.
# Load the model into '''HLMV''' (Half-Life Model Viewer).

For more detailed instructions, see:

https://forums.empiresmod.com/index.php?threads/making-models-for-empires-source-mp-2013.18308/

'''Note:''' Steps 2–8 must be repeated each time the model is edited.
----

== TODO ==

* Add pipelines for additional modeling programs.

----

== Tools ==

* https://ficool2.github.io/HammerPlusPlus-Website/tools.html

----

Modelling Pipeline

2026-04-05T19:05:19Z

Awpolt:

Documentation of the current modelling pipeline.

{{Abandoned}}

== Current Texture Pipeline ==

# Create your image.
# Import the image into VTFEdit.
# Select the appropriate settings.
# Save the file in '''.vtf''' format.

'''Note:''' Steps 2–4 must be repeated every time the image is edited.
----

== Current Model Pipeline (Blender) ==

# Install Blender Source Tools.
# Create your model in Blender.
# Export the model to the correct file format.
# Create a '''.qc''' file.
# Compile the model by running the '''.qc''' file through '''studiomdl'''.
# Place textures in the correct folder ''(only when textures change — see Texture Pipeline)''.
# Place materials in the correct folder ''(only when materials change)''.
# Load the model into '''HLMV''' (Half-Life Model Viewer).

For more detailed instructions, see:

https://forums.empiresmod.com/index.php?threads/making-models-for-empires-source-mp-2013.18308/

'''Note:''' Steps 2–8 must be repeated every time the model is edited.
----

== TODO ==

* Add pipelines for additional modeling programs.

----

Change Log

2026-04-05T16:39:47Z

Awpolt:

This is an overview of the published versions of empires:

== Source Engine (2013 branch) ==
{{VersionTableHeader}}
{{VersionTableRow|patches=5|2.39|4|2026-02-21}}
{{VersionTableRow|2.39|3|2026-01-25}}
{{VersionTableRow|2.39|2|2025-12-13}}
{{VersionTableRow|2.39|1|2025-12-06}}
{{VersionTableRow|2.39|0|2025-11-30}}
{{VersionTableRow|patches=4|2.38|3|2025-07-26}}
{{VersionTableRow|2.38|2|2025-07-05}}
{{VersionTableRow|2.38|1|2025-07-05}}
{{VersionTableRow|2.38|0|2025-06-20}}
{{VersionTableRow|patches=5|2.37|4|2024-10-19}}
{{VersionTableRow|2.37|3|2024-09-08}}
{{VersionTableRow|2.37|2|2024-08-18}}
{{VersionTableRow|2.37|1|2024-08-11}}
{{VersionTableRow|2.37|0|2024-05-26}}
{{VersionTableRow|patches=4|2.36|3|2024-04-20}}
{{VersionTableRow|2.36|2|2024-02-24}}
{{VersionTableRow|2.36|1|2024-02-18}}
{{VersionTableRow|2.36|0|2024-02-17}}
{{VersionTableRow|patches=3|2.35|2|2023-07-15}}
{{VersionTableRow|2.35|1|2023-07-08}}
{{VersionTableRow|2.35|0|2023-06-18}}
{{VersionTableRow|patches=9|2.34|9|2023-03-05}}
{{VersionTableRow|2.34|8}}
{{VersionTableRow|2.34|7}}
{{VersionTableRow|2.34|6}}
{{VersionTableRow|2.34|5}}
{{VersionTableRow|2.34|4}}
{{VersionTableRow|2.34|3}}
{{VersionTableRow|2.34|2}}
{{VersionTableRow|2.34|1|2022-01-16}}
{{VersionTableRow|patches=5|2.33|5|2022-01-01}}
{{VersionTableRow|2.33|4}}
{{VersionTableRow|2.33|3}}
{{VersionTableRow|2.33|2}}
{{VersionTableRow|2.33|1}}
{{VersionTableRow|patches=2|2.32|2}}
{{VersionTableRow|2.32|1}}
{{VersionTableRow|patches=2|2.31|2}}
{{VersionTableRow|2.31|1}}
{{VersionTableRow|patches=10|2.30|10}}
{{VersionTableRow|2.30|9}}
{{VersionTableRow|2.30|8}}
{{VersionTableRow|2.30|7}}
{{VersionTableRow|2.30|6}}
{{VersionTableRow|2.30|5}}
{{VersionTableRow|2.30|4|2021-01-22}}
{{VersionTableRow|2.30|3}}
{{VersionTableRow|2.30|2}}
{{VersionTableRow|2.30|1|2020-12-05}}
{{VersionTableRow|patches=6|2.29|6}}
{{VersionTableRow|2.29|5}}
{{VersionTableRow|2.29|4}}
{{VersionTableRow|2.29|3}}
{{VersionTableRow|2.29|2}}
{{VersionTableRow|2.29|1}}
{{VersionTableRow|patches=8|2.28|8}}
{{VersionTableRow|2.28|7}}
{{VersionTableRow|2.28|6}}
{{VersionTableRow|2.28|5}}
{{VersionTableRow|2.28|4}}
{{VersionTableRow|2.28|3}}
{{VersionTableRow|2.28|2}}
{{VersionTableRow|2.28|1}}
{{VersionTableRow|patches=1|2.27|1}}
{{VersionTableRow|patches=8|2.26|8}}
{{VersionTableRow|2.26|7}}
{{VersionTableRow|2.26|6}}
{{VersionTableRow|2.26|5}}
{{VersionTableRow|2.26|4}}
{{VersionTableRow|2.26|3}}
{{VersionTableRow|2.26|2}}
{{VersionTableRow|2.26|1}}
{{VersionTableRow|patches=9|2.25|9}}
{{VersionTableRow|2.25|8}}
{{VersionTableRow|2.25|7}}
{{VersionTableRow|2.25|6}}
{{VersionTableRow|2.25|5}}
{{VersionTableRow|2.25|4}}
{{VersionTableRow|2.25|3}}
{{VersionTableRow|2.25|2}}
{{VersionTableRow|2.25|1}}
{{VersionTableRow|patches=4|2.24|4}}
{{VersionTableRow|2.24|3}}
{{VersionTableRow|2.24|2}}
{{VersionTableRow|2.24|1}}
{{VersionTableRow|patches=3|2.23|3}}
{{VersionTableRow|2.23|2}}
{{VersionTableRow|2.23|1}}
{{VersionTableRow|patches=2|2.22|2}}
{{VersionTableRow|2.22|1}}
{{VersionTableRow|patches=6|2.21|6}}
{{VersionTableRow|2.21|5}}
{{VersionTableRow|2.21|4}}
{{VersionTableRow|2.21|3}}
{{VersionTableRow|2.21|2}}
{{VersionTableRow|2.21|1}}
{{VersionTableRow|patches=2|2.20|2}}
{{VersionTableRow|2.20|1}}
{{VersionTableRow|patches=1|2.19|1}}
{{VersionTableRow|patches=2|2.18|2}}
{{VersionTableRow|2.18|1}}
{{VersionTableRow|patches=4|2.17|4}}
{{VersionTableRow|2.17|3}}
{{VersionTableRow|2.17|2}}
{{VersionTableRow|2.17|1|2018-08-15}}
{{VersionTableRow|patches=4|2.16|4}}
{{VersionTableRow|2.16|3}}
{{VersionTableRow|2.16|2}}
{{VersionTableRow|2.16|1}}
{{VersionTableRow|patches=11|2.15|11}}
{{VersionTableRow|2.15|10}}
{{VersionTableRow|2.15|9}}
{{VersionTableRow|2.15|8}}
{{VersionTableRow|2.15|7}}
{{VersionTableRow|2.15|6}}
{{VersionTableRow|2.15|5}}
{{VersionTableRow|2.15|4}}
{{VersionTableRow|2.15|3}}
{{VersionTableRow|2.15|2}}
{{VersionTableRow|2.15|1}}
{{VersionTableRow|patches=7|2.14|7}}
{{VersionTableRow|2.14|6}}
{{VersionTableRow|2.14|5}}
{{VersionTableRow|2.14|4}}
{{VersionTableRow|2.14|3}}
{{VersionTableRow|2.14|2}}
{{VersionTableRow|2.14|1}}
{{VersionTableRow|patches=5|2.13|5}}
{{VersionTableRow|2.13|4}}
{{VersionTableRow|2.13|3}}
{{VersionTableRow|2.13|2}}
{{VersionTableRow|2.13|1}}
{{VersionTableRow|patches=1|2.12|1}}
{{VersionTableRow|patches=1|2.11|1}}
{{VersionTableRow|patches=1|2.10|0|2016-9-25}}
{{VersionTableRow|patches=4|2.9|3}}
{{VersionTableRow|2.9|2}}
{{VersionTableRow|2.9|1}}
{{VersionTableRow|2.9|0|2016-08-13}} 
{{VersionTableRow|patches=1|2.8|0|2016-05-08}}
{{VersionTableRow|patches=1|2.7|0|2016-02-17}}
{{VersionTableRow|patches=12|2.6|9|2015-06-27}}
{{VersionTableRow|2.6|8|2015-05-10}}
{{VersionTableRow|2.6|7a}}
{{VersionTableRow|2.6|7|2015-05-04}}
{{VersionTableRow|2.6|6|2015-04-25}}
{{VersionTableRow|2.6|5|2015-03-28}}
{{VersionTableRow|2.6|4a|2015-03-22}}
{{VersionTableRow|2.6|4|2015-03-21}}
{{VersionTableRow|2.6|3|2015-03-14}}
{{VersionTableRow|2.6|2|2015-02-12}}
{{VersionTableRow|2.6|1|2015-01-27}}
{{VersionTableRow|2.6|0|2015-01-14}}
{{VersionTableRowOld|patches=10|2.52|.9|2015-01-10}}
{{VersionTableRowOld|2.52|.8|2014-12-25}}
{{VersionTableRowOld|2.52|.7|2014-12-13}}
{{VersionTableRowOld|2.52|.6|2014-11-29}}
{{VersionTableRowOld|2.52|.5|2014-11-21}}
{{VersionTableRowOld|2.52|.4|2014-11-16}}
{{VersionTableRowOld|2.52|.3|2014-11-08}}
{{VersionTableRowOld|2.52|.2|2014-10-21}}
{{VersionTableRowOld|2.52|.1|2014-10-18}}
{{VersionTableRowOld|2.52||2014-09-28}}
{{VersionTableRowOld|patches=1|2.51||2014-09-28}}
{{VersionTableRowOld|patches=4|2.5| RC4}}
{{VersionTableRowOld|2.5| RC3}}
{{VersionTableRowOld|2.5| RC2}}
{{VersionTableRowOld|2.5| RC1|2014-03-26}}
|}

== Source Engine (orange box branch) ==

{{VersionTableHeader}}
{{VersionTableRowOld|patches=1|2.41||2013-03-23}}
{{VersionTableRowOld|patches=1|2.4||2012-12-27}}
{{VersionTableRowOld|patches=2|Steam Release| 2|2011-11-26}}
{{VersionTableRowOld|Steam Release| 1|2011-03-09}}
{{VersionTableRowOld|patches=1|2.31|a|2011-02-22}}
{{VersionTableRowOld|patches=1|2.30||2010-11-21}}
{{VersionTableRowOld|patches=1|2.29||2010-11-8}}
{{VersionTableRowOld|patches=2|2.28|b|2010-10-28}}
{{VersionTableRowOld|2.28||2010-10-11}}
{{VersionTableRowOld|patches=1|2.27||2010-09-30}}
{{VersionTableRowOld|patches=3|2.26||2010-09-25}}
{{VersionTableRowOld|2.26| Rc2|2010-09-23}}
{{VersionTableRowOld|2.26| Rc1|2010-09-23}}
{{VersionTableRowOld|patches=3|2.25|b|2010-04-29}}
{{VersionTableRowOld|2.25|a|2010-04-18}}
{{VersionTableRowOld|2.25||2010-04-14}}
{{VersionTableRowOld|patches=5|2.24|e|2009-07-24|type=Linux hotfix}}
{{VersionTableRowOld|2.24|d|2009-05-21}}
{{VersionTableRowOld|2.24|c|2009-05-08|type=Balancing hotfix}}
{{VersionTableRowOld|2.24|b|2009-05-08}}
{{VersionTableRowOld|2.24||2009-05-07|type=Prerelease}}
{{VersionTableRowOld|patches=4|2.2|3|2009-03-14}}
{{VersionTableRowOld|2.2|2|2009-01-19}}
{{VersionTableRowOld|2.2|1|2008-12-30}}
{{VersionTableRowOld|2.2||2008-12-13}}
|}

== Source Engine (hl2 branch) ==

{{VersionTableHeader}}
{{VersionTableRowOld|patches=2|2.1|1|2008-01-03}}
{{VersionTableRowOld|2.1||2008-01-02}}
{{VersionTableRowOld|patches=1|2.0||2007-11-30}}
{{VersionTableRowOld|patches=10|1.0|71|2006-07-31}}
{{VersionTableRowOld|1.0|7|2006-07-23}}
{{VersionTableRowOld|1.0|6|2006-07-2}}
{{VersionTableRowOld|1.0|5|2006-05-14}}
{{VersionTableRowOld|1.0|4}}
{{VersionTableRowOld|1.0|31}}
{{VersionTableRowOld|1.0|3}}
{{VersionTableRowOld|1.0|2}}
{{VersionTableRowOld|1.0|1|2006-03-17}}
{{VersionTableRowOld|1.0||2006-03-04}}
|}
== Refractor 2 Engine ==

{{VersionTableHeader}}
{{VersionTableRowOld|patches=1|0.2||2004-04-10}}
{{VersionTableRowOld|patches=2|0.1||2004-02-08}}
{{VersionTableRowOld|0.1||2004-01-10}}
|}

== Misc. Pages ==
{{fixme|These pages contain content that needs to be split up into the redlink pages above.}}
* [[Change_Log_(2.8-2.25)|2.8 - 2.25]]
* [[Change_Log_(pre_2.25)|2.25 and older]]

Mapping

2026-04-05T16:27:27Z

Awpolt:

{{MappingDocumentation}}
__NOTOC__

== Overview ==
From a technical standpoint, mapping for Empires is very similar to mapping for any other Source game or mod, with the addition of several required entities. The mapping section of the Empires Wiki explains how to configure the Source SDK for Empires and provides additional resources to help you get started.

From a gameplay perspective, however, mapping for Empires is quite different. Empires maps are generally much larger than those in other Source games or mods, often pushing the limits of what the Source engine can handle. As a result, optimization requirements are stricter, both in terms of mapper constraints and overall map performance.

There are two primary types of maps in Empires: '''Classic''' and '''Conquest''', each offering a distinct style of gameplay.
----

== Classic Maps ==
Classic maps are the flagship experience of Empires, showcasing its core gameplay mechanics. Each team has a commander and a starting base (such as a barracks or designated spawn point).

Teams must expand outward, capturing territory to gain resources and strategic advantages. The commander oversees the battlefield from an overhead view, directing the team toward completing objectives.

Some classic maps also include capture points (typically flags), creating a hybrid gameplay style. In these maps, building refineries is combined with capturing objectives that provide resources or strategic benefits, such as spawn points, ammo/health crates, or even map-altering events.
----

== Conquest Maps ==
Conquest maps modify the standard Empires gameplay by removing command vehicles entirely. Without commanders, teams must rely on direct coordination to push forward, capture objectives, and control territory.

These maps can feature infantry-only combat or a mix of infantry and vehicles, depending on the design.
----

== Editing Entities Without Recompiling the Whole Map ==
In some cases, you may want to adjust entity properties (such as vehicle IDs or loadouts) without recompiling the entire map. This can be done using external tools or methods, as demonstrated here:

https://imgur.com/a/RJcHCma
----

== Other Resources ==

* [https://developer.valvesoftware.com/wiki/Main_Page Valve Developer Wiki]
* [https://developer.valvesoftware.com/wiki/Category:Level_Design Level Design]
* [https://developer.valvesoftware.com/wiki/Category:Entities Entities]
* [https://developer.valvesoftware.com/wiki/Category:Hammer Hammer Editor Documentation]
* [https://www.interlopers.net/index.php/tutorials Interlopers Tutorials]
* [https://halfwit-2.com/?page=tutorials Halfwit-2 Tutorials]

[[Category: Mapping]]

Mapping

2026-04-05T16:21:42Z

Awpolt:

{{MappingDocumentation}}
__NOTOC__

'''Overview'''

From a technical standpoint, mapping for Empires is very much the same as mapping for any other Source game or mod, but with a collection of additional, necessary entities. The mapping section of the Empires Wiki will explain how to configure the Source SDK for Empires, and offer additional learning resources with which to get started.

From a gameplay standpoint, mapping for Empires is very different from mapping for other Source games or mods. Empires maps are predominantly larger than those of other games and mods. Most often, Empires maps are nearly as large as the Source engine will allow. Optimization is more stringent in both limitations on mappers and requirements of maps.

There are two types of maps common to Empires: ''classic maps'' and ''conquest maps'', each entailing a unique style of gameplay.

===Classic Maps===
Classic maps are the flagship maps which champion the core gameplay that Empires was built to provide. Each team has a commander, and some sort of starting base (be it a barracks or an arbitrary spawn point). The teams must venture out, take control of territories for resources or strategic vantage. A commander views the battlefield from above and leads the team in the completion of its objectives. Some classic maps include capture point objectives (flags, most often) to create a hybrid style of play, where building refineries is mixed with capturing points that offer resources or some other territorial benefit, such as a spawnpoint, ammo/health crate, or layout-changing event.

===Conquest Maps===
Conquest maps segment Empires gameplay by removing the command vehicles from each team. Each team must venture forward to capture objectives and control territories. Conquest maps can involve standalone infantry or a combination of infantry and vehicles.

===Editing entities without recompiling whole map===
e.g. to fix vehicle ids or loadouts
https://imgur.com/a/RJcHCma

==Other Resources==
*[http://developer.valvesoftware.com/ Valve Developer Wiki]
**[http://developer.valvesoftware.com/wiki/Category:Level_Design Level Design]
**[http://developer.valvesoftware.com/wiki/Category:Entities Entities]
**[http://developer.valvesoftware.com/wiki/Category:Hammer Hammer Editor Documentation]
*[http://interlopers.net/index.php?page=tutorials Interlopers Tutorials]
*[http://halfwit-2.com/?page=tutorials Halfwit-2 Tutorials]

[[Category: Mapping]]

Engineer-Buildable Objects

2026-04-05T16:20:07Z

Awpolt:

{{Sitenav|[[Mapping]] > Engineer Buildable Objects}}This guide will teach you how to place buildable objects within your map. To begin, I will assume that you already have a working map. If you do not, please check out the Basic Conquest Map tutorial first.

The first type of object is brush-based. Examples of these include the ramps leading to the dam on mvalley or the access ramps on crossroads.

=== Brush-Based Objects ===

# Load your map in Hammer and center the views around where you want your object to appear.
# Using the Brush Tool, create your object. In this example, I will create another ramp similar to those you have seen before, but you can create anything you like.
# Select all of the brushes (blocks) that make up your object by holding the '''Shift''' key and left-clicking them in the 3D view.
# Once you are sure the entire object is selected, press '''Ctrl + T''' to convert it into an entity.
# A new dialog box will appear. From the drop-down menu, select '''emp_eng_map_brush'''.
# You will see several properties listed below the drop-down. These control everything from ownership to health.
# Most properties are self-explanatory and include descriptions to guide you. Make sure to review the entire list and configure each setting as needed. Below are the example settings used for this ramp:

* '''Name:''' be_ramp
* '''Number of Parent Capture Point:'''
* '''Initial Owner:''' Brenodi Empire
* '''Changes Ownership:''' No
* '''Raise Object on Build:''' Yes
* '''Solid on Spawn:''' No
* '''Visible to Enemy Team:''' No
* '''Time to Respawn:''' 60
* '''Initial Health:''' 25
* '''Maximum Health:''' 100
* '''Only Grenadier Can Harm:''' No
* '''Solid on Respawn:''' No

# You now have a ramp that raises when built, belongs to BE, and becomes buildable again after one minute.
# Compile your map. The object should now appear in-game and behave according to the values you set.

----

=== Model-Based Objects ===
The second type of object is model-based. These allow you to place more complex objects into your map, but they are less flexible than brush-based ones. Examples include the wooden barriers on escort or those found in the ruins on duststorm.

# Load your map in Hammer and center the views around where you want your object to appear.
# Using the Entity Tool, select '''emp_eng_map_model''' from the drop-down menu on the right-hand side of the screen.
# Click on a surface in the 3D view to place the entity.
# Press '''Alt + Enter''' to open the properties window, then locate the '''Model''' property.
# Click '''Browse''' and select the model you want to use.
# Click '''OK''', then use the 2D views to position your object. Models can be rotated, but they cannot be skewed or resized.
# Once you are satisfied with the placement, press '''Alt + Enter''' again and configure the remaining properties (see steps 6–9 above).

[[Category:Mapping|Engineer-Buildable Objects]]

Mapping Tutorials

2026-04-05T16:17:29Z

Awpolt:

{{MappingDocumentation}}

'''Beginner'''
*[[Basic Classic Map]]
*[[Basic Conquest Map]]
*[[Resource nodes|Resource Nodes]]
*[[Flag Maps]]
*[[Engineer-Buildable Objects]]
*[[Releasing a Map]]

==Intermediate==
* [[Multi-Part Buildables]]
* [[Adding A Timelimit]]
* [[Custom map particles]]
* [[Editing entities without recompiling whole map]]

[[Category: Mapping]]

Mapping Tutorials

2026-04-05T16:15:37Z

Awpolt:

{{MappingDocumentation}}

*[[Basic Classic Map]]
*[[Basic Conquest Map]]
*[[Resource nodes|Resource Nodes]]
*[[Flag Maps]]
*[[Engineer-Buildable Objects]]
*[[Releasing a Map]]

==Intermediate==
* [[Multi-Part Buildables]]
* [[Adding A Timelimit]]
* [[Custom map particles]]
* [[Editing entities without recompiling whole map]]

[[Category: Mapping]]

Configuring Hammer for Empires

2026-04-05T16:07:35Z

Awpolt:

{{MappingDocumentation}}
Hammer should work out of the box using the Hammer.bat file in the bin folder. Feel free to create a shortcut! Once launching, choose Empires 2013 from the list, and voila! Hammer for Empires should launch. If you encounter problems, do not hesitate to post on the [[Empires Discord]] to seek help.

Helping Out

2026-03-20T22:53:28Z

Awpolt:

{{Sitenav|Helping Out}}

The beauty of a [[wiki]] is that anyone can contribute to its maintenance and growth. All you need to do is register for an account and start editing by clicking the “Edit” link at the top of each page. Wiki pages are created using a simple markup language, which is explained in the [[metawikimedia:Help:Contents#For_editors|MediaWiki Editor’s Guide]].

* If you have any questions about working on the content here, feel free to stop by the [[Empires Discord]].

VGUI

2018-09-20T14:14:21Z

Awpolt: /* Adding a new HUD element */

==VGUI==
GUI elements in Empires are made using [https://developer.valvesoftware.com/wiki/VGUI2 VGUI2]. The layout of windows can be edited using the .res files in the resource folder.

==HUD==
HUD elements in Empires are either made using C++ for performance or by using a combination of VGUI and Javascript. The positioning and layout of HUD elements is controlled by the hudlayout.res file in the scripts folder.

Hud elements are updated using [[Data Bindings]]

=== Adding a new HUD element ===
# Create a new folder structure extension in the Empires/empires folder named custom/
# Add hudlayout.res inside the folder
# Open hudlayout.res
# Add an entry for your new element:<br>
<pre>
MyCustomCrosshair // The name of your element
{
"fieldName" "MyCustomCrosshair" // This should be the same as the previous name. (required)
"type" "javascript" // Indicates that this is a javascript hud element (required)
"res" "resource/ui/emp_hud_vehicle_crosshair.res" // The location of your res file (required)
"src" "resource/ui/emp_hud_vehicle_crosshair.js" // The location of your javascript file (required)
"paintbackground" 0 //Disables the default background
"paintborder" 0 // Disables the default border

"xpos" "50" // Sets the x position. Position is relative to a 640x480 screen.
"ypos" "50" // Sets the y position
"wide" "100" // Sets the width
"tall" "100" // Sets the height
"autoResize" "0" // Disables resizing by the user

// debug border, enable these two to help with positioning
//"border" "DebugBorder"
//"paintborder" 1
}
</pre>
# Make a copy of the res and src files and edit them. For more information, look at the [[CVguiJavascriptContext]] documentation.
# For more information about the position, look at the [[HUD pos]] documention.

===HUD Hide flags===

The player has a variable <code>m_iHideHUD</code> that defines which hud elements should be hidden.
https://github.com/ValveSoftware/source-sdk-2013/blob/0d8dceea4310fde5706b3ce1c70609d72a38efdf/mp/src/game/client/hud.cpp#L948

Each hud element can asign its self to a hide group using <code>SetHiddenBits(int group)</code>.

There are 3 special hide flags.
* HIDEHUD_ALL is special because it is always asigned to every element. So calling SetHiddenBits(HIDEHUD_ALL) is pointless.
* HIDEHUD_PLAYERDEAD & HIDEHUD_NEEDSUIT are special because it does not use <code>m_iHideHUD</code>. Seem to be a bit of a hack by valve.

== VGUI Elements ==
Some frequently used [[:Category:VGUI_Elements | vgui elements]] are:
* [[Panel]]
* [[Label]]
* [[ImagePanel]]
* [[CVguiJavascriptContext]]

==Borders==

<pre>
DebugBorder2
{
"inset" "0 0 0 0" // margin
"backgroundType" "1" // is of type backgroundtype_e (BACKGROUND_FILLED = 0, BACKGROUND_TEXTURED = 1, BACKGROUND_ROUNDEDCORNERS = 2)
Left // the side
{
"1" // a border can have more then 1 line.
{
"color" "0 255 0 255" // color of the border
"offset" "2 1" // start and end offset. skip the first 2 pixels and skip the last 1 pixel
}
}
Right
{
"1"
{
"color" "0 255 0 255"
"offset" "1 0"
}
}
Top
{
"1"
{
"color" "0 255 0 255"
"offset" "0 0"
}
}
Bottom
{
"1"
{
"color" "0 255 0 255"
"offset" "0 0"
}
}
}
</pre>

==Testing==
To speed up testing, set the following launch options in Steam under the game's properties:
-dev +map con_urb +exec testing

[[Category:VGUI]]

VGUI

2018-09-20T14:11:55Z

Awpolt:

==VGUI==
GUI elements in Empires are made using [https://developer.valvesoftware.com/wiki/VGUI2 VGUI2]. The layout of windows can be edited using the .res files in the resource folder.

==HUD==
HUD elements in Empires are either made using C++ for performance or by using a combination of VGUI and Javascript. The positioning and layout of HUD elements is controlled by the hudlayout.res file in the scripts folder.

Hud elements are updated using [[Data Bindings]]

=== Adding a new HUD element ===
# Create a new folder structure extension in the Empires/empires folder named custom/
# Add hudlayout.res inside the folder
# Open scripts/hudlayout.res
# Add an entry for your new element:<br>
<pre>
MyCustomCrosshair // The name of your element
{
"fieldName" "MyCustomCrosshair" // This should be the same as the previous name. (required)
"type" "javascript" // Indicates that this is a javascript hud element (required)
"res" "resource/ui/emp_hud_vehicle_crosshair.res" // The location of your res file (required)
"src" "resource/ui/emp_hud_vehicle_crosshair.js" // The location of your javascript file (required)
"paintbackground" 0 //Disables the default background
"paintborder" 0 // Disables the default border

"xpos" "50" // Sets the x position. Position is relative to a 640x480 screen.
"ypos" "50" // Sets the y position
"wide" "100" // Sets the width
"tall" "100" // Sets the height
"autoResize" "0" // Disables resizing by the user

// debug border, enable these two to help with positioning
//"border" "DebugBorder"
//"paintborder" 1
}
</pre>
# Make a copy of the res and src files and edit them. For more information, look at the [[CVguiJavascriptContext]] documentation.
# For more information about the position, look at the [[HUD pos]] documention.

===HUD Hide flags===

The player has a variable <code>m_iHideHUD</code> that defines which hud elements should be hidden.
https://github.com/ValveSoftware/source-sdk-2013/blob/0d8dceea4310fde5706b3ce1c70609d72a38efdf/mp/src/game/client/hud.cpp#L948

Each hud element can asign its self to a hide group using <code>SetHiddenBits(int group)</code>.

There are 3 special hide flags.
* HIDEHUD_ALL is special because it is always asigned to every element. So calling SetHiddenBits(HIDEHUD_ALL) is pointless.
* HIDEHUD_PLAYERDEAD & HIDEHUD_NEEDSUIT are special because it does not use <code>m_iHideHUD</code>. Seem to be a bit of a hack by valve.

== VGUI Elements ==
Some frequently used [[:Category:VGUI_Elements | vgui elements]] are:
* [[Panel]]
* [[Label]]
* [[ImagePanel]]
* [[CVguiJavascriptContext]]

==Borders==

<pre>
DebugBorder2
{
"inset" "0 0 0 0" // margin
"backgroundType" "1" // is of type backgroundtype_e (BACKGROUND_FILLED = 0, BACKGROUND_TEXTURED = 1, BACKGROUND_ROUNDEDCORNERS = 2)
Left // the side
{
"1" // a border can have more then 1 line.
{
"color" "0 255 0 255" // color of the border
"offset" "2 1" // start and end offset. skip the first 2 pixels and skip the last 1 pixel
}
}
Right
{
"1"
{
"color" "0 255 0 255"
"offset" "1 0"
}
}
Top
{
"1"
{
"color" "0 255 0 255"
"offset" "0 0"
}
}
Bottom
{
"1"
{
"color" "0 255 0 255"
"offset" "0 0"
}
}
}
</pre>

==Testing==
To speed up testing, set the following launch options in Steam under the game's properties:
-dev +map con_urb +exec testing

[[Category:VGUI]]