So say, for example, you have a large collection of boot textures, but you don't fancy writing a long map.txt, specifying boots for hundreds if not thousands of players.Įxample of speeder.cfg file: # Game speed configuration count.factor = 0.96 Advanced configuration 9.1. 'Random boots' setting Bootserver configuration file (bootserv.cfg) contains a setting called random-boots.enabled, which allows to activate random selection of boots for those players, who don't have a GDB boot assigned in map.txt. ![]() Here is an example of simple map: # Bootserver map # 185,'adidas00.png' # Barthez 186,'adidas01.png' # Thuram 194,'puma.png' # Zidane 195,'adidas02.png' # Henry 217,'Germany adidasyellow.png' # Klose 1791,'adidas00.png' # Davids 7.2. Texture filename needs to be a pathname relative to GDB boots, so you can organize your boots into subfolders if you want, or just have a flat structure with all boots placed in the 'boots' folder itself. You can find out the ID for each player in the Edit Mode: the Player ID: text will be displayed at the top of the screen. Similar to other modules that use map.txt, you put a player ID and the filename for the boot texture on one line, separating them by a comma.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |