Console - Revision history

Ashhawk: BSN link flagged for maintenance - using AWB

2022-02-01T15:57:48Z

BSN link flagged for maintenance - using AWB

FollowTheGourd: Not really a mod - just the exact same file as available through the above mentioned methods.

2010-05-27T22:57:53Z

Not really a mod - just the exact same file as available through the above mentioned methods.

Nezroy: adding link to make console commands visible mod

2010-05-27T15:17:28Z

adding link to make console commands visible mod

FollowTheGourd: /* Another way to get it */

2010-02-20T14:50:33Z

‎Another way to get it

FollowTheGourd: Available for sure in the character creator of all things

2010-02-19T02:38:25Z

Available for sure in the character creator of all things

BryanDerksen: a bug and a fix for the bug.

2010-02-18T23:52:15Z

a bug and a fix for the bug.

Jon Thompson: It was unclear that you needed a dash

2009-11-28T04:08:40Z

It was unclear that you needed a dash

Georg Zoeller: /* Using the console in-game */

2009-10-28T02:16:59Z

‎Using the console in-game

BryanDerksen: information on how to use the console in game, and how to use runscript

2009-07-22T20:48:52Z

information on how to use the console in game, and how to use runscript

BryanDerksen: import from extranet

2009-06-27T16:45:49Z

import from extranet

New page

Up in the View Menu other windows you will see one called "Console".

This is where you would enter console commands that allow the toolset to interact with the game engine. It is mostly (if not always) used when you have an area open in the Area Editor.

The console commands were built to work with the game not the toolset but some of them do work with the toolset alone.

Your toolset will crash when using some of them so make sure you save your work before trying them.

← Older revision		Revision as of 15:57, 1 February 2022
Line 1:		Line 1:
		+	{{BSN link}}
		+
	Up in the View Menu other windows you will see one called "Console".		Up in the View Menu other windows you will see one called "Console".

← Older revision		Revision as of 22:57, 27 May 2010
Line 55:		Line 55:
	Alternatively, install the free 7-zip program, right click on ''data\DataSetup.exe'', select ''7-Zip -> Open archive'', and then extract fonts.erf from ''$0"\packages\core\data\"''.		Alternatively, install the free 7-zip program, right click on ''data\DataSetup.exe'', select ''7-Zip -> Open archive'', and then extract fonts.erf from ''$0"\packages\core\data\"''.

−	You can also get the font from the [http://dragonagenexus.com/downloads/file.php?id=1110 Make CONSOLE commands visible] ~~mod~~.	+	You can also get the font from the [http://dragonagenexus.com/downloads/file.php?id=1110 Make CONSOLE commands visible] file.

← Older revision		Revision as of 15:17, 27 May 2010
Line 54:		Line 54:

	Alternatively, install the free 7-zip program, right click on ''data\DataSetup.exe'', select ''7-Zip -> Open archive'', and then extract fonts.erf from ''$0"\packages\core\data\"''.		Alternatively, install the free 7-zip program, right click on ''data\DataSetup.exe'', select ''7-Zip -> Open archive'', and then extract fonts.erf from ''$0"\packages\core\data\"''.
		+
		+	You can also get the font from the [http://dragonagenexus.com/downloads/file.php?id=1110 Make CONSOLE commands visible] mod.

← Older revision		Revision as of 14:50, 20 February 2010
Line 51:		Line 51:
	This problem is caused in some systems by the DVD's installer failing to install the fonts.erf file. Fonts.erf is included on the game disk, so you should be able to redo this part of the installation and properly install fonts.erf by running datasetup.exe manually (which is on the game disk in the "data" directory). This should not be an issue for Steam users since a different installer is involved in Steam installations.		This problem is caused in some systems by the DVD's installer failing to install the fonts.erf file. Fonts.erf is included on the game disk, so you should be able to redo this part of the installation and properly install fonts.erf by running datasetup.exe manually (which is on the game disk in the "data" directory). This should not be an issue for Steam users since a different installer is involved in Steam installations.

−	If you still have trouble obtaining fonts.erf from your installation, ~~download~~ the [http://social.bioware.com/page/da-character-creator Character Creator] and copy it from ''Dragon Age Origins Character Creator\packages\core\data''.	+	If you still have trouble obtaining fonts.erf from your installation, install the [http://social.bioware.com/page/da-character-creator Character Creator] and then copy fonts.erf from ''Dragon Age Origins Character Creator\packages\core\data''.
		+
		+	Alternatively, install the free 7-zip program, right click on ''data\DataSetup.exe'', select ''7-Zip -> Open archive'', and then extract fonts.erf from ''$0"\packages\core\data\"''.

← Older revision		Revision as of 02:38, 19 February 2010
Line 50:		Line 50:

	This problem is caused in some systems by the DVD's installer failing to install the fonts.erf file. Fonts.erf is included on the game disk, so you should be able to redo this part of the installation and properly install fonts.erf by running datasetup.exe manually (which is on the game disk in the "data" directory). This should not be an issue for Steam users since a different installer is involved in Steam installations.		This problem is caused in some systems by the DVD's installer failing to install the fonts.erf file. Fonts.erf is included on the game disk, so you should be able to redo this part of the installation and properly install fonts.erf by running datasetup.exe manually (which is on the game disk in the "data" directory). This should not be an issue for Steam users since a different installer is involved in Steam installations.
		+
		+	If you still have trouble obtaining fonts.erf from your installation, download the [http://social.bioware.com/page/da-character-creator Character Creator] and copy it from ''Dragon Age Origins Character Creator\packages\core\data''.

← Older revision		Revision as of 23:52, 18 February 2010
Line 46:		Line 46:
	oDestination = GetObjectByTag(sTemp);		oDestination = GetObjectByTag(sTemp);
	</dascript>		</dascript>
		+
		+	== Console text is invisible in some game installs ==
		+
		+	This problem is caused in some systems by the DVD's installer failing to install the fonts.erf file. Fonts.erf is included on the game disk, so you should be able to redo this part of the installation and properly install fonts.erf by running datasetup.exe manually (which is on the game disk in the "data" directory). This should not be an issue for Steam users since a different installer is involved in Steam installations.

@@ Line 9: / Line 9: @@
 == Using the console in-game ==
-The in-game console is normally not accessible. To enable it run the game with a command line parameter "enabledeveloperconsole". Then, when the game is running, press the tilde key (~) to bring up the console. This is a prompt in the upper left corner of the screen. The console was used extensively in development for debugging and testing purposes, but in the finished version of the game there's only one console command available; "runscript".
+The in-game console is normally not accessible. To enable it run the game with a command line parameter "-enabledeveloperconsole". Then, when the game is running, press the tilde key (~) to bring up the console. This is a prompt in the upper left corner of the screen. The console was used extensively in development for debugging and testing purposes, but in the finished version of the game there's only one console command available; "runscript".
 The runscript command does exactly as it says - it runs a script, given as a name typed after a space. So for example:

← Older revision		Revision as of 02:16, 28 October 2009
Line 20:		Line 20:

	You can pass the script additional parameters if you like. These parameters will be stored in the [[module]] variable RUNSCRIPT_VAR. RUNSCRIPT_VAR is a simple string, your script will need to parse it itself.		You can pass the script additional parameters if you like. These parameters will be stored in the [[module]] variable RUNSCRIPT_VAR. RUNSCRIPT_VAR is a simple string, your script will need to parse it itself.
		+
		+	'''Caution:''' Using scripts like killallhostiles may break scripted plot situations, so you should avoid using it outside of custom content testing.
		+

	For example,		For example,

← Older revision		Revision as of 20:48, 22 July 2009
Line 6:		Line 6:

	Your toolset will crash when using some of them so make sure you save your work before trying them.		Your toolset will crash when using some of them so make sure you save your work before trying them.
		+
		+	== Using the console in-game ==
		+
		+	The in-game console is normally not accessible. To enable it run the game with a command line parameter "enabledeveloperconsole". Then, when the game is running, press the tilde key (~) to bring up the console. This is a prompt in the upper left corner of the screen. The console was used extensively in development for debugging and testing purposes, but in the finished version of the game there's only one console command available; "runscript".
		+
		+	The runscript command does exactly as it says - it runs a script, given as a name typed after a space. So for example:
		+
		+	<pre>
		+	>runscript killallhostiles
		+	</pre>
		+
		+	will cause the script named "killallhostiles" to be run.
		+
		+	You can pass the script additional parameters if you like. These parameters will be stored in the [[module]] variable RUNSCRIPT_VAR. RUNSCRIPT_VAR is a simple string, your script will need to parse it itself.
		+
		+	For example,
		+
		+	<pre>
		+	>runscript usespecificobject demo100pl_lever
		+	</pre>
		+
		+	calls the script "usespecificobject" and puts "demo100pl_lever" into the module RUNSCRIPT_VAR. The script can then call
		+
		+	<dascript>
		+	string sParam = GetLocalString(GetModule(),"RUNSCRIPT_VAR");
		+	</dascript>
		+
		+	to retrieve it.
		+
		+	If you need more than one parameter, pick a separator (a space is usually most appropriate) and split up the string in RUNSCRIPT_VAR appropriately. For example:
		+
		+	<dascript>
		+	//parse out first parameter - the object to use.
		+	nSpaceLoc = FindSubString(sParam," ");
		+	sTemp = SubString(sParam,0,nSpaceLoc);
		+	oDestination = GetObjectByTag(sTemp);
		+	</dascript>