Due to the update from Valve to Source 2, this repository is no longer relevant. It will be kept up as a reference archive for other Source 1 games.
A collection of my stripper and map setting configuration files for CS:GO maps of or relating to the Minigames gamemode.
Simply open an issue on this github repository with the bug in question. Please include the full map name in the issue's name, whether it is a map bug or bug with existing config, and follow the template for map bugs.
For making any map-cfg configs, you simply need to add a csgo setting on its own line. This is primarily for ConVars that are not whitelisted in bspconvar_whitelist.txt or that are locked/hidden and require sm_cvar to change, but may also be used to easily change whitelisted CVars the map needs but has not set itself. Load order for the configs is as follows:
- autoexec.cfg - On server start.
- server.cfg - On map change, before plugins are loaded.
- map.cfg - OnAutoConfigsBuffered
- map.post.cfg - OnConfigsExecuted
For making configs, you will most likely need knowledge of how to use CS:GO's hammer editor. You will also want a tool like VIDE's entity lump editor, or entSpy to view a map's entity logic. In addition, you may need a tool like BspSrc to decompile a map's bsp to get it's vmf if you wish to open the map directly in the hammer editor. You can also compare maps with current strigger configs in this repository and see how past fixes have been done if you're looking for functional examples of things.
IMPORTANT: Make sure the filename of the config matches the exact map name on the server.
Stripper: Source is quite a complicated plugin, but essentially boils down to being the hammer editor in text form. If you're looking for a good starting point to learn how to make Stripper: Source configs, you can check out the official documentation or this tutorial. If you have any questions regarding stripper creation you can always join the #mapping channel on the GFLClan Zombie Escape Discord for assistance.
In order to try and keep stripper files consistant, the following syntax should try to be maintained:
- Use // for comments instead of ;, #, or \0
- Use "filter:" instead of "remove:" to delete entities from the map
- List all changes and bug fixes at the top of the file in a change block if there are multiple fixes in the file
- Put brackets {} on their own lines
- Use spaces instead of tabs