So to help users out, you can use the "stripper_dump" console command (requires rcon or server console access). Unfortunately, I don't know all of the entity properties. Match first, then replace, then delete, and insert last. You can specify the sub-blocks in any order, although they are always processed the same way. Here, an arbitrary scaling value is added to the entity.Īlthough " match" is a required sub-block, replace, delete, and insert are all optional. insert: Specifies any additional key value pairs to insert.In this example, the model property of the trash can is being removed. The value string may have regular expressions (//). delete: Deletes any properties matching both the key name and the value string.In this example, " prop_physics_multiplayer" will become " hostage_entity." replace: Replaces the values of any properties that have the same key name.You can use regular expressions (//) for any key values here. match: Matches all entities that have the listed model and classname.This configuration entry will replace all garbage cans with hostages. "model" "models/props_junk/garbage_metalcan002a.mdl" For each matched block, the replace, delete, and insert sub-blocks are processed. The Match sub-block lets you specify which property blocks to search for. This adds a new directive called " modify." Modification blocks have four sub-blocks: Match, Replace, Delete, Insert. Version 1.1 of Stripper:Source adds a powerful new method of filtering entity property blocks. Note that rules are read in order - if add a rule a future rule can filter it out.Ĥ. For example, this will remove any entity that is any type of physics prop: These let you define patterns to match against. To learn more about regular expressions, visit Perl Regex. Lastly, you can also use regular expressions to match entities. You can also get very specific, for example, this will only filter out the hostage we added earler: For example, the following block will remove any entity that is a hostage: To filter an entity from the map, each entity block contains properties that you wish to match against. The example below will add the hostage to the map: Note that you do not need to specify this token for each block - it will continue until you use another operation token (such as "filter:"). The first quote is the key, the second quote is the value.įor example, this block describes a hostage: The properties are two quoted strings per line, separated by a space. Each line in the block declares a property of the entity. Each block, denoted between the tokens declares an entity. Note that the syntax is not flexible - you must declare each item or token on a separate line as shown above. Stripper:Source configuration files are stored in the following format: These will only be run when that specific map is used. cfg (for example, addons/stripper/maps/de_dust.cfg). You can also configure per-map files in addons/stripper/maps/. The first is addons/stripper/global_filters.cfg, which is run on every map change.
There are two main configuration files for Stripper:Source. Note! If you require older versions of Stripper:Source, for example, if you must use an older Metamod:Source version, you can find them by clicking here.
#How to remove istripper from windows zip file#
Extract the zip file into your server's mod folder.You can also specify per-map configuration options.įirst, make sure you have the proper tools installed. You can filter out entities with specific values or regular expressions, or declare new entities to be added. This is a small but flexible plugin which lets you filter and add entities to a map before it loads, much like Stripper2 for Half-Life 1, by botman. Stripper:Source by BAILOPAN Stripper:Source