Search results
From Fortress Forever Wiki
Jump to navigationJump to search
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.819 bytes (124 words) - 20:05, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.815 bytes (124 words) - 20:05, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.816 bytes (124 words) - 20:06, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.807 bytes (124 words) - 20:06, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.804 bytes (124 words) - 20:06, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.807 bytes (124 words) - 20:06, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.810 bytes (124 words) - 20:06, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.813 bytes (124 words) - 20:07, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.801 bytes (124 words) - 20:07, 15 February 2008
- // Place any global binds/aliases/scripts into the userconfig.cfg file and specifics into each // IMPORTANT: The userconfig.cfg file DOES NOT auto-execute.819 bytes (126 words) - 20:06, 15 February 2008
- ...if you had copy-pasted the entire file into your own script. The included file must reside in FortresForever\maps\includes. Includes are generally done at714 bytes (103 words) - 13:28, 5 May 2010
- // Place all general binds/aliases/scripts into this file. // IMPORTANT: This file DOES NOT auto-execute.983 bytes (141 words) - 20:07, 15 February 2008
- ...l">the file name must end in .vtf; however it is actually looking up a vmt file. This .vmt must be located in located in FortressForever\materials\vgui\.</1 KB (159 words) - 11:02, 11 May 2009
- | weapon portrait = [[File:G_ga_190x190.jpg]] | igimage1=[[File:Spy_1.jpg|135px]]564 bytes (74 words) - 10:36, 29 October 2011
- File:2fort01.jpg|Mid Base Respawn File:2fort02.jpg|Battlements Respawn3 KB (576 words) - 13:08, 8 June 2012
- ...se trigger_ff_script, and then name it "nobuild". Then, in your map's .LUA file be sure to include base_teamplay.lua as such: <pre>-- Map's LUA file2 KB (324 words) - 16:15, 31 December 2007
- ...se trigger_ff_script, and then name it "nogrens". Then, in your map's .LUA file be sure to include base_teamplay.lua as such: <pre>-- Map's LUA file2 KB (322 words) - 16:16, 31 December 2007
- 1. The first file you will need to edit is your '''autoexec.cfg'''. * You can find this file in the following directory: '''FortressForever/'''.8 KB (1,413 words) - 19:43, 21 September 2008
- A script is a config file (usually for a specific class) that has key binds that make it easier for y ...med example. If we typed example into the console, or executed it in a cfg file, command 1, 2, and 3 would execute in the order listed in the alias.3 KB (480 words) - 22:19, 1 May 2010
- By default, the autoexec.cfg file is blank.157 bytes (19 words) - 10:54, 20 September 2009