Talk:How to Script - Revision history

IMAJOEL: /* Done */

2016-12-17T22:21:54Z

Done

← Older revision		Revision as of 17:21, 17 December 2016
Line 59:		Line 59:
	I think that pretty much covers it. Anyone else see something that's missing? -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 02:16, 12 August 2013 (UTC)		I think that pretty much covers it. Anyone else see something that's missing? -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 02:16, 12 August 2013 (UTC)

	It would be nice if the page called "How to Script" actually included instructions on how to script and not just how to write a script.		It would be nice if the page called "How to Script" actually included instructions on how to script and not just how to write a script. -JT 12/2016

IMAJOEL: /* Done */

2016-12-17T22:21:25Z

Done

← Older revision		Revision as of 17:21, 17 December 2016
Line 58:		Line 58:

	I think that pretty much covers it. Anyone else see something that's missing? -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 02:16, 12 August 2013 (UTC)		I think that pretty much covers it. Anyone else see something that's missing? -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 02:16, 12 August 2013 (UTC)

			It would be nice if the page called "How to Script" actually included instructions on how to script and not just how to write a script.

ABSOLON: /* If Statements */

2014-11-13T19:46:51Z

If Statements

← Older revision		Revision as of 14:46, 13 November 2014
Line 46:		Line 46:
	setvariable 1 Hello		setvariable 1 Hello
	:I can't recall if you can directly override certain system variables such as %0-9, %t, %s, etc., but it is possible that the above might work. One way to change the command line variables is to call the script from within the script, essentially restarting it. E.g.:		:I can't recall if you can directly override certain system variables such as %0-9, %t, %s, etc., but it is possible that the above might work. One way to change the command line variables is to call the script from within the script, essentially restarting it. E.g.:
	.myscript new variables go here ~~exit~~		.myscript new variables go here
			exit
	:The script will start from the beginning using the new variables. This doesn't work for all situations, and I don't know what your situation is, but it's possible to get creative with it.		:The script will start from the beginning using the new variables. This doesn't work for all situations, and I don't know what your situation is, but it's possible to get creative with it.
	:Re: emptying a variable. To empty a global variable, simply use:		:Re: emptying a variable. To empty a global variable, simply use:

ABSOLON: /* If Statements */

2014-11-13T19:43:59Z

If Statements

← Older revision		Revision as of 14:43, 13 November 2014
Line 41:		Line 41:

	-[[User:SEGGERING\|SEGGERING]] ([[User talk:SEGGERING\|talk]]) 13:19, 13 November 2014 (CST)		-[[User:SEGGERING\|SEGGERING]] ([[User talk:SEGGERING\|talk]]) 13:19, 13 November 2014 (CST)
			:I haven't scripted in StormFront for years, but I think I remember enough of it's quirks to help you out.
	:I haven't scripted in StormFront for years, but I think I remember enough of it's quirks to help you out.:Re: If_#. This only works off of the command line variables, and only then at the level of 'does this variable exist?' StormFront does not have a more robust if/then statement, so you will have to use matches to emulate that.:Re: Command line variables set within script. You don't actually need to use the '=' in there, which might be why it is not working for you. Try instead: setvariable 1 Hello:I can't recall if you can directly override certain system variables such as %0-9, %t, %s, etc., but it is possible that the above might work. One way to change the command line variables is to call the script from within the script, essentially restarting it. E.g.: .myscript new variables go here exit:The script will start from the beginning using the new variables. This doesn't work for all situations, and I don't know what your situation is, but it's possible to get creative with it.:Re: emptying a variable. To empty a global variable, simply use: setvariable <variable>:without putting a value. If you want to delete the variable entirely, so that the variable name doesn't even exist anymore then use: deletevariable <variable>:Be aware that this might cause errors if the variable doesn't actually exist. It's usually not necessary to do this in most cases anyway.--[[User:ABSOLON\|ABSOLON]] ([[User talk:ABSOLON\|talk]]) 13:42, 13 November 2014 (CST)
			:Re: If_#. This only works off of the command line variables, and only then at the level of 'does this variable exist?' StormFront does not have a more robust if/then statement, so you will have to use matches to emulate that.
			:Re: Command line variables set within script. You don't actually need to use the '=' in there, which might be why it is not working for you. Try instead:
			setvariable 1 Hello
			:I can't recall if you can directly override certain system variables such as %0-9, %t, %s, etc., but it is possible that the above might work. One way to change the command line variables is to call the script from within the script, essentially restarting it. E.g.:
			.myscript new variables go here exit
			:The script will start from the beginning using the new variables. This doesn't work for all situations, and I don't know what your situation is, but it's possible to get creative with it.
			:Re: emptying a variable. To empty a global variable, simply use:
			setvariable <variable>
			:without putting a value. If you want to delete the variable entirely, so that the variable name doesn't even exist anymore then use:
			deletevariable <variable>
			:Be aware that this might cause errors if the variable doesn't actually exist. It's usually not necessary to do this in most cases anyway.--[[User:ABSOLON\|ABSOLON]] ([[User talk:ABSOLON\|talk]]) 13:42, 13 November 2014 (CST)

	== Done ==		== Done ==

ABSOLON: /* If Statements */

2014-11-13T19:42:44Z

If Statements

← Older revision		Revision as of 14:42, 13 November 2014
Line 41:		Line 41:

	-[[User:SEGGERING\|SEGGERING]] ([[User talk:SEGGERING\|talk]]) 13:19, 13 November 2014 (CST)		-[[User:SEGGERING\|SEGGERING]] ([[User talk:SEGGERING\|talk]]) 13:19, 13 November 2014 (CST)
			:I haven't scripted in StormFront for years, but I think I remember enough of it's quirks to help you out.:Re: If_#. This only works off of the command line variables, and only then at the level of 'does this variable exist?' StormFront does not have a more robust if/then statement, so you will have to use matches to emulate that.:Re: Command line variables set within script. You don't actually need to use the '=' in there, which might be why it is not working for you. Try instead: setvariable 1 Hello:I can't recall if you can directly override certain system variables such as %0-9, %t, %s, etc., but it is possible that the above might work. One way to change the command line variables is to call the script from within the script, essentially restarting it. E.g.: .myscript new variables go here exit:The script will start from the beginning using the new variables. This doesn't work for all situations, and I don't know what your situation is, but it's possible to get creative with it.:Re: emptying a variable. To empty a global variable, simply use: setvariable <variable>:without putting a value. If you want to delete the variable entirely, so that the variable name doesn't even exist anymore then use: deletevariable <variable>:Be aware that this might cause errors if the variable doesn't actually exist. It's usually not necessary to do this in most cases anyway.--[[User:ABSOLON\|ABSOLON]] ([[User talk:ABSOLON\|talk]]) 13:42, 13 November 2014 (CST)

	== Done ==		== Done ==

SEGGERING: /* If Statements */

2014-11-13T19:36:48Z

If Statements

← Older revision		Revision as of 14:36, 13 November 2014
Line 38:		Line 38:
	== If Statements ==		== If Statements ==
	I want an if statement to be run off of a variable that is set in the script.		I want an if statement to be run off of a variable that is set in the script.
	Is there any way to use If_ on other variables than 1-9~~? Is there a way to set the console line variables in-script~~?		Is there any way to use If_ on other variables than 1-9?
	<pre>
	:echo %1
	:setvariable 1 = Goodbye
	:echo %1</pre>

	Running it like this ".AScript Hello" outputs
	:Hello
	:Hello

	It creates a new variable called "1" but that variable is unusable because the console line variable 1 overrides it, or so it seems.
	Also, is there a way to empty a variable?
	-[[User:SEGGERING\|SEGGERING]] ([[User talk:SEGGERING\|talk]]) 13:19, 13 November 2014 (CST)		-[[User:SEGGERING\|SEGGERING]] ([[User talk:SEGGERING\|talk]]) 13:19, 13 November 2014 (CST)


	== Done ==		== Done ==

SEGGERING at 19:24, 13 November 2014

2014-11-13T19:24:08Z

← Older revision		Revision as of 14:24, 13 November 2014
Line 39:		Line 39:
	I want an if statement to be run off of a variable that is set in the script.		I want an if statement to be run off of a variable that is set in the script.
	Is there any way to use If_ on other variables than 1-9? Is there a way to set the console line variables in-script?		Is there any way to use If_ on other variables than 1-9? Is there a way to set the console line variables in-script?
			<pre>
	[AScript]
	:echo %1		:echo %1
	:setvariable 1 = Goodbye		:setvariable 1 = Goodbye
	:echo %1		:echo %1</pre>

	Running it like this ".AScript Hello" outputs		Running it like this ".AScript Hello" outputs

SEGGERING at 19:19, 13 November 2014

2014-11-13T19:19:49Z

@@ Line 35: / Line 35: @@
 :::{{tt|Goodbye}}
 ::Hope that helps answer your question.  If you want, you can also download the Wizard from play.net and there's a help section on scripting that has details about the SAVE command as well.--[[User:Evran|Evran]] 20:55, 1 August 2010 (UTC)
 == Done ==

CARAAMON: /* Done */ new section

2013-08-12T02:16:53Z

Done: new section

← Older revision		Revision as of 21:16, 11 August 2013
Line 35:		Line 35:
	:::{{tt\|Goodbye}}		:::{{tt\|Goodbye}}
	::Hope that helps answer your question. If you want, you can also download the Wizard from play.net and there's a help section on scripting that has details about the SAVE command as well.--[[User:Evran\|Evran]] 20:55, 1 August 2010 (UTC)		::Hope that helps answer your question. If you want, you can also download the Wizard from play.net and there's a help section on scripting that has details about the SAVE command as well.--[[User:Evran\|Evran]] 20:55, 1 August 2010 (UTC)

			== Done ==

			I think that pretty much covers it. Anyone else see something that's missing? -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 02:16, 12 August 2013 (UTC)

Maintenance script: /* Save */

2010-08-01T20:55:39Z

Save

← Older revision		Revision as of 15:55, 1 August 2010
Line 26:		Line 26:
	It would nice to see SAVE explained, even if it's deprecated. I'm still trying to figure out what it does exactly so I understand other people's scripts. --[[User:Ateles\|Ateles]] 16:45, 1 August 2010 (UTC)		It would nice to see SAVE explained, even if it's deprecated. I'm still trying to figure out what it does exactly so I understand other people's scripts. --[[User:Ateles\|Ateles]] 16:45, 1 August 2010 (UTC)
	:As I recall, it basically acted as a no option SETVARIABLE command, saving it to "%s". -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 20:44, 1 August 2010 (UTC)		:As I recall, it basically acted as a no option SETVARIABLE command, saving it to "%s". -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 20:44, 1 August 2010 (UTC)
			::This is correct. In addition, despite it being listed as obsolete, it will still work. The command is simply a hold-over from Wizard where you can't set variables from within the script. Redundant would be a better word to describe it, since obsolete implies that it no longer functions. I.e. everything SAVE can do, SETVARIABLE can do. The main differences from SETVARIABLE is that the variable %s created by the save command only exists as long as the script is running and you can only SAVE a single variable at a time, any successive SAVE commands replacing the previous value. For example:
			:::{{tt\|SAVE Hello}}
			:::{{tt\|echo %s}}
			:::{{tt\|SAVE Goodbye}}
			:::{{tt\|echo %s}}
			::When run, this would output:
			:::{{tt\|Hello}}
			:::{{tt\|Goodbye}}
			::Hope that helps answer your question. If you want, you can also download the Wizard from play.net and there's a help section on scripting that has details about the SAVE command as well.--[[User:Evran\|Evran]] 20:55, 1 August 2010 (UTC)

← Older revision		Revision as of 15:55, 1 August 2010
Line 26:		Line 26:
	It would nice to see SAVE explained, even if it's deprecated. I'm still trying to figure out what it does exactly so I understand other people's scripts. --[[User:Ateles\|Ateles]] 16:45, 1 August 2010 (UTC)		It would nice to see SAVE explained, even if it's deprecated. I'm still trying to figure out what it does exactly so I understand other people's scripts. --[[User:Ateles\|Ateles]] 16:45, 1 August 2010 (UTC)
	:As I recall, it basically acted as a no option SETVARIABLE command, saving it to "%s". -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 20:44, 1 August 2010 (UTC)		:As I recall, it basically acted as a no option SETVARIABLE command, saving it to "%s". -Moderator [[User:Caraamon\|Caraamon Makdasi]]<sup>([[User talk:Caraamon\|talk]])</sup> 20:44, 1 August 2010 (UTC)
			::This is correct. In addition, despite it being listed as obsolete, it will still work. The command is simply a hold-over from Wizard where you can't set variables from within the script. Redundant would be a better word to describe it, since obsolete implies that it no longer functions. I.e. everything SAVE can do, SETVARIABLE can do. The main differences from SETVARIABLE is that the variable %s created by the save command only exists as long as the script is running and you can only SAVE a single variable at a time, any successive SAVE commands replacing the previous value. For example:
			:::{{tt\|SAVE Hello}}
			:::{{tt\|echo %s}}
			:::{{tt\|SAVE Goodbye}}
			:::{{tt\|echo %s}}
			::When run, this would output:
			:::{{tt\|Hello}}
			:::{{tt\|Goodbye}}
			::Hope that helps answer your question. If you want, you can also download the Wizard from play.net and there's a help section on scripting that has details about the SAVE command as well.--[[User:Evran\|Evran]] 20:55, 1 August 2010 (UTC)