Console intro: Difference between revisions

Revision as of 22:27, 13 February 2025

Complete descriptions of the console commands and variables are now available (in handy categorized lists and a complete alphabetical list for reference). Check out the Console categories page for descriptions of the categories.

One way to get the console to work, is to edit the text file kingpin/main/autoexec.cfg and add this line:

@@ Line 1: / Line 1: @@
-<p>Complete descriptions of the console commands and variables are now available (in handy categorized lists and a complete alphabetical list for reference). Check out the [[Console categories]] page for descriptions of the categories, or just click any of the category links on the left (under Console Help -- yeah, the ones that weren't there when you were on the main page).</p>
+<p>Complete descriptions of the console commands and variables are now available (in handy categorized lists and a complete alphabetical list for reference). Check out the [[Console categories]] page for descriptions of the categories.</p>
 <p>One way to get the console to work, is to edit the text file kingpin/main/autoexec.cfg and add this line:</p>
-<syntaxhighlight>set developer 1</syntaxhighlight>
-<p>Then you'll be able to open (or close) the console with the ~ key (that's a TILDE, and it's on the key on the upper-left of your keyboard, under ESCAPE, with the wiggly line and the left-tic on it!) <strong>Note</strong> that in some foreign versions, such as the British release of Kingpin, the console will not work unless you edit the autoexec.cfg as described above <em>and</em> add <strong>+developer 1 t</strong>o the Kingpin shortcut If, for some reason, that doesn't work, edit kingpin/main/autoexec.cfg and add the line:</p>
-<syntaxhighlight>bind ~ "toggleconsole"</syntaxhighlight>
-<h3>How to edit a text file like autoexec.cfg</h3>