Console intro - Revision history

FREDZ at 22:31, 13 February 2025

2025-02-13T22:31:48Z

← Older revision		Revision as of 22:31, 13 February 2025
Line 4:		Line 4:
	<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>		<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>
	<p>bind ~ "toggleconsole"</p>		<p>bind ~ "toggleconsole"</p>
			===How to edit a text file like autoexec.cfg===
			<p>Here are extremely detailed instructions for editing a text file, including how to add <strong>developer 1</strong> to your Kingpin autoexec.cfg file:</p>
			<ol>
			<li>Run notepad by selecting it from your Start button (Programs -> Acessories -> Notepad).</li>
			<li>If, for some reason, notepad is not there, open the Run dialog box (Start -> Run), type in "notepad" (without the quotes) and press <em>ENTER</em>.</li>
			<li>When notepad opens, select File -> Open, and browse to your [[Setup_the_game#Location_Kingpin\|Kingpin directory]]. Click the "Files of Type" box at the bottom of the Open dialog box and select "All Files".</li>
			<li>Find the Kingpin/Main folder, select the autoexec.cfg file (you may just see "autoexec"), and select Open.</li>
			<li>Type the following line into the file -- it dosn't matter where, just make sure it's on a line all by itself: <strong>developer 1</strong></li>
			<li>Select File -> Save, and then close notepad.</li>
			<li>You should now be all set, but don't forget that enabling developer mode as you just did is very likely to mess up the single-player game. For example, doors that are supposed to open once a certain enemy is dead may not (or worse). If you're still playing the single-player game, I suggest <em>NOT</em> enabling developer mode (delete that line altogether, or just change it to <strong>developer 0</strong>).</li>
			</ol>

FREDZ at 22:29, 13 February 2025

2025-02-13T22:29:34Z

← Older revision		Revision as of 22:29, 13 February 2025
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.</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>		<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>set developer 1</p>
			<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>
			<p>bind ~ "toggleconsole"</p>

FREDZ at 22:28, 13 February 2025

2025-02-13T22:28:43Z

← Older revision		Revision as of 22:28, 13 February 2025
Line 2:		Line 2:
	<p>One way to get the console to work, is to edit the text file kingpin/main/autoexec.cfg and add this line:</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>		<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>~~

FREDZ at 22:28, 13 February 2025

2025-02-13T22:28:29Z

← Older revision		Revision as of 22:28, 13 February 2025
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.</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>		<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>

FREDZ at 22:27, 13 February 2025

2025-02-13T22:27:54Z

← Older revision		Revision as of 22:27, 13 February 2025
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>		<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>~~

FREDZ at 22:26, 13 February 2025

2025-02-13T22:26:49Z

← Older revision		Revision as of 22:26, 13 February 2025
Line 5:		Line 5:
	<syntaxhighlight>bind ~ "toggleconsole"</syntaxhighlight>		<syntaxhighlight>bind ~ "toggleconsole"</syntaxhighlight>
	<h3>How to edit a text file like autoexec.cfg</h3>		<h3>How to edit a text file like autoexec.cfg</h3>
	~~<p>Here are extremely detailed instructions for editing a text file, including how to add <strong>developer 1</strong> to your Kingpin autoexec.cfg file:</p>~~
	~~<ol>~~
	~~<li>Run notepad by selecting it from your Start button (Programs -> Acessories -> Notepad).</li>~~
	~~<li>If, for some reason, notepad is not there, open the Run dialog box (Start -> Run), type in "notepad" (without the quotes) and press <em>ENTER</em>.</li>~~
	~~<li>When notepad opens, select File -> Open, and browse to your Kingpin directory. Click the "Files of Type" box at the bottom of the Open dialog box and select "All Files".</li>~~
	~~<li>Find the Kingpin/Main folder, select the autoexec.cfg file (you may just see "autoexec"), and select Open.</li>~~
	~~<li>Type the following line into the file -- it dosn't matter where, just make sure it's on a line all by itself: <strong>developer 1</strong></li>~~
	~~<li>Select File -> Save, and then close notepad.</li>~~
	<li>You should now be all set, but don't forget that enabling developer mode as you just did is very likely to mess up the single-player game. For example, doors that are supposed to open once a certain enemy is dead may not (or worse). If you're still playing the single-player game, I suggest <em>NOT</em> enabling developer mode (delete that line altogether, or just change it to <strong>developer 0</strong>).</li>
	~~</ol>~~

FREDZ: FREDZ moved page Console Intro to Console intro

2025-02-09T21:16:06Z

FREDZ moved page Console Intro to Console intro

← Older revision		Revision as of 21:16, 9 February 2025
(No difference)

FREDZ: Created page with "
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).

One way to get the console to work, is to edit the text file kingpin/main/autoexec.cfg and..."

2025-02-09T21:10:56Z

Created page with "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). One way to get the console to work, is to edit the text file kingpin/main/autoexec.cfg and..."

New page

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).
One way to get the console to work, is to edit the text file kingpin/main/autoexec.cfg and add this line:
<syntaxhighlight>set developer 1</syntaxhighlight>
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!) Note 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 and add +developer 1 to the Kingpin shortcut If, for some reason, that doesn't work, edit kingpin/main/autoexec.cfg and add the line:
<syntaxhighlight>bind ~ "toggleconsole"</syntaxhighlight>
<h3>How to edit a text file like autoexec.cfg</h3>
Here are extremely detailed instructions for editing a text file, including how to add developer 1 to your Kingpin autoexec.cfg file:
<ol>
<li>Run notepad by selecting it from your Start button (Programs -> Acessories -> Notepad).</li>
<li>If, for some reason, notepad is not there, open the Run dialog box (Start -> Run), type in "notepad" (without the quotes) and press ENTER.</li>
<li>When notepad opens, select File -> Open, and browse to your Kingpin directory. Click the "Files of Type" box at the bottom of the Open dialog box and select "All Files".</li>
<li>Find the Kingpin/Main folder, select the autoexec.cfg file (you may just see "autoexec"), and select Open.</li>
<li>Type the following line into the file -- it dosn't matter where, just make sure it's on a line all by itself: developer 1</li>
<li>Select File -> Save, and then close notepad.</li>
<li>You should now be all set, but don't forget that enabling developer mode as you just did is very likely to mess up the single-player game. For example, doors that are supposed to open once a certain enemy is dead may not (or worse). If you're still playing the single-player game, I suggest NOT enabling developer mode (delete that line altogether, or just change it to developer 0).</li>
</ol>