A Beginner's Guide to Scripting - Revision history

Fidcal at 21:08, 10 January 2009

2009-01-10T21:08:24Z

← Older revision		Revision as of 21:08, 10 January 2009
Line 1:		Line 1:
	{{A Beginner's Guide to Scripting}}		{{A Beginner's Guide to Scripting}}

	~~''written by Fidcal''~~

	Scripts will give extra power and flexibility to the way your Dark Mod Fan Mission works and let you add new effects as well as simplifying some tasks that would be complicated in mapping.		Scripts will give extra power and flexibility to the way your Dark Mod Fan Mission works and let you add new effects as well as simplifying some tasks that would be complicated in mapping.

Fidcal at 19:11, 10 January 2009

2009-01-10T19:11:58Z

← Older revision		Revision as of 19:11, 10 January 2009
Line 1:		Line 1:
			{{A Beginner's Guide to Scripting}}

	''written by Fidcal''		''written by Fidcal''

Line 275:		Line 277:
	That concludes this introduction to scripting. On the next page we shall begin writing scripts that do useful tasks in your maps...		That concludes this introduction to scripting. On the next page we shall begin writing scripts that do useful tasks in your maps...

			{{A Beginner's Guide to Scripting}}

	{{tutorial-scripting}}		{{tutorial-scripting}}

Fidcal at 14:38, 10 January 2009

2009-01-10T14:38:48Z

← Older revision		Revision as of 14:38, 10 January 2009
Line 1:		Line 1:

	''written by Fidcal''		''written by Fidcal''

			Scripts will give extra power and flexibility to the way your Dark Mod Fan Mission works and let you add new effects as well as simplifying some tasks that would be complicated in mapping.

	This first page of the Beginner's Guide is an introduction to scripting: how to set it up and get it working and gives a simple basic understanding of essentials ready to start writing your own useful Dark Mod scripts.		This first page of the Beginner's Guide is an introduction to scripting: how to set it up and get it working and gives a simple basic understanding of essentials ready to start writing your own useful Dark Mod scripts.

Fidcal at 14:31, 10 January 2009

2009-01-10T14:31:11Z

← Older revision		Revision as of 14:31, 10 January 2009
Line 1:		Line 1:

	''written by Fidcal''		''written by Fidcal''


	~~WORK IN PROGRESS...~~.		This first page of the Beginner's Guide is an introduction to scripting: how to set it up and get it working and gives a simple basic understanding of essentials ready to start writing your own useful Dark Mod scripts.

Fidcal: /* Comments, Remarks */

2009-01-10T14:27:50Z

Comments, Remarks

← Older revision		Revision as of 14:27, 10 January 2009
Line 255:		Line 255:

	==Comments, Remarks==		==Comments, Remarks==

			You can (and should) add comments to your scripts where necessary to help explain and clarify the script both for others and for yourself at some future time when you might not remember exactly. Two ways to add a comment:

			Use a double slash // followed by your text comment on one line and that line will be ignored by the script - it is purely human information. Example:

			//Script to give the player magic boots
			//That let the player fall slowly and run faster.
			//Written by Fidcal

			You can also enclose multiple lines within /* and */ if you prefer. Example:

			/*Script to give the player magic boots
			That let the player fall slowly and run faster.
			Written by Fidcal*/



			That concludes this introduction to scripting. On the next page we shall begin writing scripts that do useful tasks in your maps...



	{{tutorial-scripting}}		{{tutorial-scripting}}

Fidcal: /* Variables: Handling Values and Text */

2009-01-10T14:09:35Z

Variables: Handling Values and Text

← Older revision		Revision as of 14:09, 10 January 2009
Line 236:		Line 236:
	float testValue = 1234.55555;		float testValue = 1234.55555;

	If you type those in at the top of the script file then all ~~the~~ functions ~~in that file~~ can share them. These are called ''global variables''		If you type those in at the top of the script file (''not'' inside a function) then all script functions can share them. These are called ''global variables''

	Normally you will type them at the top of and [[within]] a function so they are only used by that function and will not conflict with other functions even if they use the same names (eg, x can be 99 in one function and x can be 7.5 in another without conflict.)		Normally you will type them at the top of and [[within]] a function so they are only used by that function and will not conflict with other functions even if they use the same names (eg, x can be 99 in one function and x can be 7.5 in another without conflict.)

Fidcal: /* Variables: Handling Values and Text */

2009-01-10T14:04:51Z

Variables: Handling Values and Text

← Older revision		Revision as of 14:04, 10 January 2009
Line 228:		Line 228:
	x=99;		x=99;
	testString="Hello World";		testString="Hello World";
	testValue = 1234.55555		testValue = 1234.55555;

	You can combine the original creating declaration and assign their contents in one instruction:		You can combine the original creating declaration and assign their contents in one instruction:

Fidcal: /* Functions */

2009-01-05T14:52:36Z

Functions

← Older revision		Revision as of 14:52, 5 January 2009
Line 118:		Line 118:
	You can have many different scripts and functions in one script file. Some may work together as part of one combined task(see later) while others may be totally unrelated and do a completely different job in your map. So you can add more scripts to your script file at any time to do other tasks. The only thing common is that they are all used by the one map with the same name as the script file. If you want to use any of them with another map you just copy and paste and maybe edit them in another script file with the same name as that other map.		You can have many different scripts and functions in one script file. Some may work together as part of one combined task(see later) while others may be totally unrelated and do a completely different job in your map. So you can add more scripts to your script file at any time to do other tasks. The only thing common is that they are all used by the one map with the same name as the script file. If you want to use any of them with another map you just copy and paste and maybe edit them in another script file with the same name as that other map.

	The function header is always preceded by its type name and followed by two normal brackets containing any data (arguments) separated by commas needed to be sent to the function. Notice that you do not add a semi-colon ; at the end - ~~they~~ are generally only to mark the end of lines of instruction. This is how the function header is set out...		The function header is always preceded by its type name and followed by two normal brackets containing any data (arguments) separated by commas needed to be sent to the function. Notice that you do not add a semi-colon ; at the end - semi-colons are generally only to mark the end of lines of instruction. This is how the function header is set out...

	type FunctionHeaderName(arg1, arg2, arg3.....)		type FunctionHeaderName(arg1, arg2, arg3.....)

Fidcal: /* Functions */

2009-01-05T14:51:56Z

Functions

← Older revision		Revision as of 14:51, 5 January 2009
Line 118:		Line 118:
	You can have many different scripts and functions in one script file. Some may work together as part of one combined task(see later) while others may be totally unrelated and do a completely different job in your map. So you can add more scripts to your script file at any time to do other tasks. The only thing common is that they are all used by the one map with the same name as the script file. If you want to use any of them with another map you just copy and paste and maybe edit them in another script file with the same name as that other map.		You can have many different scripts and functions in one script file. Some may work together as part of one combined task(see later) while others may be totally unrelated and do a completely different job in your map. So you can add more scripts to your script file at any time to do other tasks. The only thing common is that they are all used by the one map with the same name as the script file. If you want to use any of them with another map you just copy and paste and maybe edit them in another script file with the same name as that other map.

	The function header is always preceded by its type name and followed by two normal brackets containing any data (arguments) separated by commas needed to be sent to the function~~, ie~~...		The function header is always preceded by its type name and followed by two normal brackets containing any data (arguments) separated by commas needed to be sent to the function. Notice that you do not add a semi-colon ; at the end - they are generally only to mark the end of lines of instruction. This is how the function header is set out...

	type FunctionHeaderName(arg1, arg2, arg3.....)		type FunctionHeaderName(arg1, arg2, arg3.....)

Fidcal: /* Functions */

2009-01-05T14:43:54Z

Functions

← Older revision		Revision as of 14:43, 5 January 2009
Line 114:		Line 114:
	==Functions==		==Functions==

	Almost all scripting is within functions which are group structures with a header name followed by curly brackets containing the instruction lines (as described in the preceding sections.) You can have many different scripts and functions in one script file. Some may work together as part of one combined task(see later) while others may be totally unrelated and do a completely different job in your map. So you can add more scripts to your script file at any time to do other tasks. The only thing common is that they are all used by the one map with the same name as the script file. If you want to use any of them with another map you just copy and paste and maybe edit them in another script file with the same name as that other map.		Almost all scripting is within functions which are group structures with a header name followed by curly brackets containing the instruction lines (as described in the preceding sections.)

			You can have many different scripts and functions in one script file. Some may work together as part of one combined task(see later) while others may be totally unrelated and do a completely different job in your map. So you can add more scripts to your script file at any time to do other tasks. The only thing common is that they are all used by the one map with the same name as the script file. If you want to use any of them with another map you just copy and paste and maybe edit them in another script file with the same name as that other map.

	The function header is always preceded by its type name and followed by two normal brackets containing any data (arguments) separated by commas needed to be sent to the function, ie...		The function header is always preceded by its type name and followed by two normal brackets containing any data (arguments) separated by commas needed to be sent to the function, ie...