Jump to content

Vauff

Server Manager
  • Content Count

    415
  • Joined

  • Last visited

  • Days Won

    3

GFL Supporter

Expires:

Vauff last won the day on October 17

Vauff had the most liked content!

Community Reputation

398 Bronze 4

8 Followers

About Vauff

  • Birthday 04/29/2000

Personal Information

  • Location
    Ontario, Canada

Computer Information

  • CPU
    Intel Core i5-9600k
  • GPU
    Gigabyte Radeon RX 580 8GB
  • Ram
    Team T-Force Vulcan 16GB DDR4-3000
  • Motherboard
    Gigabyte Z390-UD
  • Power Supply
    Corsair TX650M
  • Monitor(s)
    Asus VG245H, Acer G215HL
  • Hard Drive(s)
    Western Digital Black 500 GB NVMe SSD, Crucial MX500 1 TB SSD

Recent Profile Visitors

4,222 profile views
  1. STRIPPER CONFIG FILES GUIDE Guide by bb_IU Updated/Maintained by Vauff Last revised: 2019/10/17 Guide Sections : Introduction Reason for creating this guide Entities Stripper:Source plugin Configuration file creation Addition and deletion of entities Modification of entities Saving as CFG Decompiling Inputs and Outputs Important links for reference Notes Introduction: Reason for creating this guide: Welcome to my guide on: how to create configuration files for the stripper plugin! The goal that I had in mind when I started creating this guide, was compiling a bunch of resources for GFL CS:GO ZE admins who are interested in the "technical" side of zombie escape. When I first started to get interested in these types of things, I noticed that there wasn't much discussion about it, so I had to go around different zombie escape communities in order to learn what I had wanted to learn. With the creation of this guide; and maybe more if I can keep learning lul, I hope that I'm able to help out any future people who are interested in learning more about the technical side of zombie escape, but are struggling to find resources for/assistance with it. Aside from this, making configuration files for the stripper plugin has many use cases. You can make use of the plugin to tweak values for mechanics in maps, block off areas, or even to fix certain entities which are causing undesirable behavior, etc. Entities: Before we get into the guide, you must first understand what an entity is, in the context of the Source Engine. According to the VALVE developer community wiki, an entity is defined as: "An object defined within the Source Engine as having characteristics which differentiate it from the world." You can find a list of all available entities here: (https://developer.valvesoftware.com/wiki/List_of_base_entities) (https://developer.valvesoftware.com/wiki/List_of_Counter-Strike:_Global_Offensive_Entities) Stripper:Source plugin: BAILOPAN's stripper plugin is a utility for Source Engine servers which allows servers to mess around with Source Engine entities. Unlike most server plugins, this plugin actually runs on top of Metamod (what SourceMod runs on) instead of being a SourceMod plugin. This doesn't really mean anything to the layman, other than that you install it differently. Originally, plugin-users only had the ability to: permanently add entities to a map, and delete entities via usage of the filter directive. But in 2006 new syntax was added to the plugin, which allowed for more flexible entity modification. The new syntax allows plugin-users to: search and modify entities (Replace/insert/delete entity properties). The plugin accepts two different types of main configuration files. The first type being a global configuration file (global_filters.cfg) which is run on every map change, and the second type being a map specific configuration file (<map name>.cfg ex: ze_journey_p.cfg) which is run ONLY when that specific map is played on the server. As someone not managing a server, all configuration files that you make will be map specific configuration files, you will never find the need to conjure up a global configuration file. Configuration file creation: Addition and deletion of entities: As mentioned before, this feature allows you at add and delete entities via the configuration file. The syntax for this feature is NOT flexible, so any configuration files created should follow the syntax in order to phase out the risk of the configuration file not working. The first step to learning how to make use of this feature is to learn how to declare entities. You can declare an entity by using a block. The start and end of a block can be created with the '{' and '}' characters respectively. After the creation of the block, you can declare the properties of the entity being declared inside the block. 1 line in a block can host exactly 1 property of an entity. When declaring the property of an entity make use of the following syntax: TWO QUOTED STRINGS PER LINE, SEPARATED BY A SPACE. FIRST STRING IS THE KEY, SECOND STRING IS THE VALUE. You can find the specific properties for different entities by making use of the entity wiki page link that I will leave in the last section of the guide. Entity declaration example: { "origin" "50 921 0" "angles" "0 -100 0 "damage" "155" "classname" "trigger_hurt" } Moving on, now that we know how to declare entities, we can make use of the different directives made available to us with this feature. There are two directives that this feature makes use of: "add:" directive, and "filter:" directive. The add directive allows us to use the entity addition feature, whereas the filter directive allows us to use the deletion via filter feature. The directives are placed at the top of a block in order to start using them. Directive usage example: add: { "origin" "50 921 0" "angles" "0 -100 0 "damage" "155" "classname" "trigger_hurt" } add: { "origin" "100 300 -100" "angles" "0 0 0 "damage" "1" "classname" "trigger_hurt" } filter: { "classname" "trigger_hurt" } In the example above, we add two entities by making use of the add directive, and then delete all trigger_hurt entities in the map by using the filter directive. Another thing to note is that you can get quite specific with the targeting when trying to delete an entity, for example: filter: { "origin" "100 300 -100" "angles" "0 0 0 "damage" "1" "classname" "trigger_hurt" } Modification of entities: This powerful feature is your bread and butter. It is what you will want to use in order to modify the various properties of entities present in maps. The modification feature adds the following directive: "modify:" directive. Blocks which make use of the modify directive have access to the following sub-blocks: "match:" sub-block, "replace:" sub-block, "delete:" sub-block, "insert:" sub-block. Although they look like directives, they are specific to each instance of blocks under the modify directive, so we call them sub-blocks. Similar to what we did in the previous feature, you will want to keep 1 entity instance/type to 1 modify block. Lastly, it's IMPORTANT to note that without the modify directive, you will not be able to access the sub-blocks. The following example will aim to provide a look at how each sub-block functions in 1 example: modify: { match: { "classname" "trigger_once" "targetname" "bosshp_add" } replace: { "classname" "trigger_multiple" } delete: { "filtername" "zombie" } insert: { "wait" "0" } } Here's what each sub-block will do when executed: match: This sub-block will search for all entities which match all the specified properties inside the block. Using classname/targetname is generally standard convention, as seen in this example, however if an entity does not have a targetname or it isn't unique, you may see classname/hammerid or classname/origin instead. Classname is rarely required, however it helps to have it there to keep track of what entity class is being modified. In the end, the only thing that's required is that your keyvalue combinations only return the entities you want to modify. replace: This sub-block will replace the keys of the entities which are returned from the match sub-block, with the keyvalues that you specify inside the replace sub-block. In the example, it will replace all matched entities classnames with "trigger_multiple". delete: This sub-block will delete the specified properties from the matched entities. In the example, it will search for the exact property key and value "filtername" "zombie", and then delete it from an entity returned by the match sub-block if it's present. insert: This sub-block will insert the specified value from the key value pair inside the sub-block. In the example, it inserts "wait" "0" which is a keyvalue for trigger_multiples that determines how fast it can be re-triggered. Saving as CFG: Now that you understand how the different aspects of the configuration files for the Stripper plugin work, you can create CFGs on your own! Open up a text editor of your choice, and create a new file. After filling it up with your desired contents, save the file as a CFG. It's important to set the file name to the name of the map that you are creating the CFG for. For example: ze_atix_panic_v1.cfg. Decompiling: Another extremely helpful process which will speed up the time you take to create configuration files for the stripper plugin is decompiling the map in order to take a look at the different entities and their key-value pairs that are available in the map for modification. Before we jump into this, first you should download the following program (http://www.riintouge.com/VIDE/). The reason that you should download it is because, VIDE (Valve Integrated Development Environment), offers an Entity Lump Editor feature. This specific feature will allow you to decompile the map and take a look at the entities and key-value pairs. If you click on the file button, you will find the option to "Open" a file. Click on this and navigate to the map file of your choice (Navigate to your games map folder and choose a .BSP file). After doing this, it will list all the entities present in the map. Now that you have access to the different entities, you can easily go through the list / use the filter bar and find what you wish to modify. Inputs and Outputs: Before we start to mess around with I/Os, it's important that we first understand what they are. According to the VALVE developer wiki, I/Os are: Editing I/Os via the usage of the configuration file is basically the same as editing generic entity property values, but it will require more caution on your side. When editing the I/Os of an entity, make sure that you understand what the I/O is doing. If you take a look at the picture above (PROGRAM: VIDE), you can see an example of what I/Os look like. If I were to edit an output, I would simply double click on the output that I want to edit, copy the selected value, and bring it over to the configuration file. Once in the configuration file I would then edit the values as I please. modify: { match: { "classname" "trigger_once" "targetname" "trigger_b_door" } delete: { "OnStartTouch" "consoleCommandsay *** DOOR OPENS IN 20 SECONDS ***01" } insert: { "OnStartTouch" "consoleCommandsay *** DOOR OPENS IN 30 SECONDS ***01" } } In the code block above, I have tweaked the output to print out for 30 seconds, rather than 20. An interesting thing to take note of when editing I/Os is that you usually want to delete the I/O then insert it, rather than replace it. This is due to the fact that when dealing with I/O, the key (OnStartTouch in this case) is not unique like standard keys such as "origin" or "targetname" are. Lastly, you will notice that there are weird characters present if working with CS:GO. The weird characters are used to separate outputs. When making use of VIDE to look at entities, you don't need to worry about reproducing that character as you can simply copy paste the exact syntax from the map via VIDE. You can also do the same when attempting to add an output. Other options for this are to make use of the ' , ' character. You can make use of the ' , ' character, when adding an output to a newly added entity in a configuration file, BUT you cannot use ' , ' when attempting to replace an output from an entity. When replacing an output, always copy the string straight from VIDE. For older Source engine games this is all irrelevant, commas are used exclusively in configs and in the actual games. Adding entities which require brushwork: A brush in the context of the Source Engine is defined as: Sometimes you may find the need to add an entity which will require brush work of some sort. Examples of use cases for this are: adding buy zones, adding safe zones, adding trigger_hurt areas to maps. When this situation comes up you can simply make use of the "add:" directive and set the model number of the entity that you're adding as the model number of a suitable brush entity from inside the .vmf file. An example of this can be seen below: ;Nuke safe zone fix. add: { "model" "*29" "classname" "trigger_hurt" "targetname" "Nuke" "StartDisabled" "1" "spawnflags" "3" "origin" "261.92 -253.52 -3422.77" "nodmgforce" "0" "damagetype" "0" "damagemodel" "0" "damagecap" "20" "damage" "9999999" } (Credits to @Potti for providing the configuration file example) If you need higher precision, or are unable to find a suitable model number, there is another option that allows you to specify exact dimensions. This only works for triggers though, not entities like func_brush. Refer to the picture below for assistance in doing this (provided by @Moltard) Important links for reference : (https://developer.valvesoftware.com/wiki/Entity) (https://developer.valvesoftware.com/wiki/Entities_in_Depth) (https://developer.valvesoftware.com/wiki/List_of_entities) (https://developer.valvesoftware.com/wiki/HammerObjectPropertiesDialog) (https://developer.valvesoftware.com/wiki/List_of_base_entities) (https://developer.valvesoftware.com/wiki/List_of_Counter-Strike:_Global_Offensive_Entities) (https://github.com/alliedmodders/stripper-source) (https://forums.alliedmods.net/showthread.php?t=39439) (https://www.bailopan.net/stripper/) (http://www.riintouge.com/VIDE/) (https://developer.valvesoftware.com/wiki/Inputs_and_Outputs) (https://developer.valvesoftware.com/wiki/Brush) (https://developer.valvesoftware.com/wiki/Brush_entity) (https://github.com/ata4/bspsrc/releases) (https://github.com/gflclan-cs-go-ze/ZE-Configs/tree/master/stripper) Notes : If you find any information in the guide that needs to be corrected, please don't hesitate to post here. Thanks for reading the guide!
  2. For tons of reasons, -1 - You've never talked in Discord - I have no idea who you are - There's no record of your provided name ever playing on the server - Your app is incredibly bare bones - You provided your email instead of a Steam ID? Please look back at the application form for what to provide there - You're not even member
  3. -1 Your listed Discord account hasn't joined our Discord server, and I can't find any playtime on the server for the nickname you've provided, nor can I recall ever seeing you.
  4. While there's clearly some sort of issue going on here, it's working for pretty much everyone else. The issue has something to do with your setup + the new FastDL together, and I wouldn't expect a resolution to the issue if you start saying "but thats not my problem anymore". The fact that you can download the bz2 in-browser shows it isn't a connection issue, meaning it's related to CS:GO somehow. Are you running any anti-cheat software perhaps? One player reported that they weren't able to download from the new FastDL with FACEIT anti-cheat running. Edit: I've 100% confirmed FACEIT AC blocks our new FastDL, so definitely disable that when connecting to the server if you use that
  5. A new FastDL server was deployed a couple days ago, you're likely having some sort of connection issue with it. Are you able to download them when trying the links in browser?
  6. Changing vote to +1 Pretty happy with what I've seen since my last vote, would definitely like to see you as admin. Good luck!
  7. Command Guide

    This thread lists all the available public commands on the CS:GO Minigames server, with descriptions of what each of them do. Commands can be prefixed in chat with ! or / (silent), or with sm_ in the console. !calladmin - Report a player to the admin team for breaking server rules !cm - List players you have self muted !comms - Displays any mute/gag punishments you may have active !dev - Displays server information !extendsleft - Shows how long the current map has been played, and how many extends have been used !gloves - Select which gloves you want to use !knife - Select which knife you want to use !models - Choose your custom player model, you can get access to more models by applying for Member and donating !moresb - Toggle on/off more scoreboard info (Timeleft on left side of the screen) !music - Toggle map music on/off !nextmap - Displays the next map the server will switch to when the time left runs out !nominate - Nominate a map to appear on the map vote !nomlist - List all the maps that are currently nominated !playtime - Shows your total playtime on the server !revote - Change your vote in server votes after already casting one !rules - List basic server rules, more detail is available in the MOTD !searchcmd - Find more specific help on server commands !settag - Set your custom chat tag, available to VIP only !showadmins - List the admins currently online !sm - Self mute a player !su - Remove a self mute on a player !spec - Spectate a player !tags - Manage your tag setup, most features available to VIP only !tp - Toggle between first/third person mode !ws - Select the weapon skins you want to use
  8. -1 No idea who you are, can't recall ever seeing you. Also, are you sure your playtime number is right? I can only find one name for you with 15 hours (unless you've used different names, if so please give them).
  9. -1 Don't really know you at all or really see you on the server, though that could be due to differing timezones. Playtime wise, while your current time is technically acceptable, it's nothing really outstanding. Also you've not joined the GFL ZE Discord, or provided a Discord handle (which is a requirement in applying for admin by the way).
  10. Changing vote to +1 You've shown yourself as great admin material since posting this application. Probably only took me so long to +1 because of not being online with you consistently enough.
  11. +1 You're really active, mature, don't break rules. Not sure what else I can say.
  12. To report players breaking our server rules, please use the following template and make a new thread in this section. Only report players if you have evidence, or the offence can be backed up with server logs (chat offences). Make sure to copy everything inside the box.
  13. mg_ski_mountain_va3 - Removed cubemap reflections on wood (it looked bad) - Changed the fountain water texture so it looks more like water - Removed a bad clipping on the slope
×
×
  • Create New...