Mission Making Tutorial - Revision history

24.232.253.176 at 21:09, 15 August 2012

2012-08-15T21:09:36Z

24.232.253.176: Undo revision 1815 by 187.75.251.159 (talk)

2012-08-15T21:08:48Z

Undo revision 1815 by 187.75.251.159 (talk)

Show changes

187.75.251.159: Jimpaolo

2012-06-12T16:00:53Z

Jimpaolo

Show changes

94.23.1.28: /* Objectives */

2012-06-12T14:10:02Z

‎Objectives

190.18.220.7: /* The SceneInit Rule */

2010-07-21T15:39:35Z

‎The SceneInit Rule

Arparso: fixed two smaller errors

2010-02-22T22:30:37Z

fixed two smaller errors

186.136.96.114 at 21:53, 22 February 2010

2010-02-22T21:53:10Z

186.136.96.114 at 21:52, 22 February 2010

2010-02-22T21:52:00Z

Mularac: Created page with '='''''NEXUS TJI mission-making'''''= As you probably know by now, thanks to Arparso's great tuturial about Nexus's scripting structure, that ev...'

2010-02-22T21:15:11Z

Created page with '='''''NEXUS TJI mission-making'''''= As you probably know by now, thanks to Arparso's great tuturial about Nexus's scripting structure, that ev...'

New page

='''''NEXUS TJI mission-making'''''=

As you probably know by now, thanks to Arparso's great tuturial about [[Nexus:TJI_Scripting_Structure|Nexus's scripting structure]], that every mission in this game is divided in MACHINES, STATES, and Rules. But that only deals with one part of the mission, the "body" of it, in a way.
In order to ilustrate this concepts I will be pasteing here a [[Demo_mission|Demo mission]] I've made with this article in mind.

==''The main parts of the mission''==
Here area a collection of the main parts a mission is divided into

===The heading===
----

Each mission starts, of course, with the basics of the mission: it's identity number, it's name, and where it'll take place (note that you can't change locations in a single mission):
<pre>
NUMBER <num>
name "<the name of the mission>"
DefLocation "<name of the location>"
</pre>
The "name of the location" is a "navpoint" created with the Solar System editor, one you can find in the "universe\systems\" folder.
Unlike the number, the name of the mission doesn't have to be unique, you can put anything in there, even the same title that some other mission, as long as the numbering is not the same (well... that's not enteryle true... if you place a letter istead of a number, the game will treat it as a mission number "0" and it will never give you a conflict, even if you label two or more missions as "NUMBER A").
Following that is a list of the current objective numbers, in this fashion:
<pre>
OBJECTIVE
1
2
...
END
</pre>
Finally, as an example, here's the [[Demo_mission#Heading|Demo mission's heading]] (note that everything after "//" and between "/* - */" is interpretated by the game as a comment):
<pre>
MISSION 1 //mission number
Name "Demo Mission" //name of the mission
DefLocation "NAV_CHAKRIS_IV" //the location where the mission will take place

OBJECTIVES //in here we place the number of objectives that will be includid in the mission
1
2
3
END
</pre>
===The SceneInit Rule===
----

This is a very special rule, critical to any mission, and that is for the fact that this rule takes place '''before''' the mission starts. In this rule you can do pretty much anything you want, but there are a few things mandatory to do here.

*The radious of the mission, in meters, as defined by the [[SetSceneRadius]](<num>); command.
*The setting of the variables associated to each of the ships that will appear on the mission (though critical for most missions, it's not mandatory), defined by the command <name of the variable> := [[GetSceneObj]]("<name of the ship>");

This rule is special also because it's the first link to any of the Machines you've written for this mission, in here you call the Machines (or Machines) you want your mission to start with.
Unlike any other Rule, this one doesn't go inside a State, it only goes beneath the "RULES" block, as all the Machines in your mission do.
Here's the [[Demo_mission#SceneInit|SceneInit]] rule of the [[Demo_mission|Demo mission]], as well as the start of the "RULES" block:
<pre>
RULES

RULE event sceneInit
:action
SetSceneRadius(100000); //this is, as the name suggests it, the radious in meters of the scene.

GuiSelect(0); //this is required to start a cinematic scene

SetRelation(#race_player, #race_spacetech, 2);
SetRelation(#race_player, #race_gorg, 2);
SetRelation(#race_gorg, #race_player, 2);
SetRelation(#race_spacetech, #race_player, 2);
SetRelation(#race_player, #race_Human_E, 1); //the relations between the races that will appear in
//the game. the "race_player" is the playable race,
//and the number mean what sort of relationship they
//share with other races, more info on that is
//located on the modding manual

sp := GetSceneObj("Mayflower");
bs := GetSceneObj("Hawkeye"); //in here we define the "Scene Objects", the ships and other
//interactive obects

drone := GetSceneObj("Nightingale");

gorg1 := GetSceneObj("Feral");
gorg2 := GetSceneObj("Darkclaw");

Disappear(drone);
Disappear(gorg1);
Disappear(gorg2); //we disappear the ships that are bound to appear via ip drive

Playmusic(1); //in here we set the number of the music track (as defined in the
//mod_sound.ini file, in the universe\engine\ folder

GetMachine("Director"):ChangeState(IntroMovie, 0);
GetMachine("Objectives"):ChangeState(monitor,0); // with these commands we "call" the machines
//that would define the game, and their given
// state

FadeScreen(1, 0, 0); //we "fade" the screen, make it black
:end
END
</pre>

===The body of the mission===
---
The sintax of this part has already been brilliantly explainied by Arparso in his [[Nexus:TJI_Scripting_Structure|Tutorial]], so I will only offer some advices here. Always use different states when there's a remarkable change in the mission (arrival of ships, discovery of stuff, etc), and try to keep your mission as tidy as possible. Machines can run simultaneosly, so having a lot of them is never a good idea. Try to divide them into clear, diferencied tasks (one of the AI, one or two for the actual mission, etc).
So, here's the body of the [[Demo_mission|Demo mission]]: [[Demo_mission#body|body]]
Also, don't forget that once you've finished with all your machines, included all the files that you wanted to include (to include a file you have to do this: "#include "<name of the file" ", and it would be like you wrote the content of that file in the mission file, so keep a close watch on the mission sintaxis of included files!) you have to '''END''' the mission. Just add a finall ''END'' on the bottom, after the last included file and just above the ''ENTITIES'' section.

===The ''ENTITIES'' section===
---
Here's defined the settings of each of the mission's ships, like name, class, race, location, heading, etc, in this fashion:
<pre>
SHIP
<content>
END
</pre>
Whereas the content may be:

*Name "<name of the ship>"

*Race #<race of the ship>

*ShipType #<ship type of the ship, as defined in the SHIPTYPE part of the tacticstypes.ini>
or
*Class #<class of the ship, as defined in the SHIPCLASS part of the tacticstypes.ini>

*Position <x y z coordinates of the ship>

*Orientation <pitch heading and bank of the ship>

*Devices #<dev 1> #<dev 2> ... #<dev n> ; Note that this is optional, every device you place here will be added to the ship, so ''BE CAREFUL'' with it.

You may also add NPC's here to the mission's ships:
<pre>
NPC
<content>
END
</pre>
with the content being:

*Name "<name>"
*ID <num> The id is the way to link this NPC to each dialog
*Face <num> If this line is not provided, then the game will use the ID number as face number
* Rank <num 1-10>
* Medals #<medal 1> ... #<medal n> ;
* CrewLevel <num> The level of the crew
* Skill 1 <num> The skill of this npc in the Military area
* Skill 2 <num> idem but in the engineering area
* Skill 3 <num> idem but in the scientific area
* XP <num> The experience of this npc.

That pretty much covers it. Here's [[Demo_mission#Entities|Demo mission's ENTITIES]] area:

<pre>
ENTITIES

SHIP
Name "Hawkeye"
Race #race_Player
ShipType #styp_ep6_Siege_Battleship
Position -1000 838 -8966
Orientation 0 0 0

NPC
Name "Johan Mastropiero"

ID 1
Face 20
Rank 3
Medals ;
CrewLevel 1
Skill 1 0
Skill 2 0
Skill 3 0
XP 0
END
END

SHIP
Name "Nightingale"
Race #race_SpaceTech
ShipType #styp_Frigate
Position 2441.14 -8877.7 2618.99
Orientation 180 0 0
END

SHIP
Name "Mayflower"
Race #race_Human_E
ShipType #styp_Supportship
Position -12843.8 -1399.87 -5833.99
Orientation 0 0 0

NPC
Name "James Carson"

ID 2
Face 26
Rank 2
Medals ;
CrewLevel 1
Skill 1 0
Skill 2 0
Skill 3 0
XP 0
END
END

SHIP
Name "Feral"
TechCat 31 20
TechPointsScanned 0
Race #race_Gorg
ShipType #styp_ep6_gorg_escortcruiser
Position -5890.52 -22.7949 7108.39
Orientation -92.7069 -36.0036 47.6695
END

SHIP
Name "Darkclaw"
TechCat 31 30
TechPointsScanned 0
Race #race_Gorg
ShipType #styp_ep3_gorg_heavy_battleship
Position -5892.08 769.904 6509.39
Orientation -92.7069 -36.0036 47.6695
END

END
</pre>

==''Auxiliary parts of a mission''==
---
I'll now move to explain two other files linked to every mission. Although they're not critical to a mission, they're adviced to be included, as they're the files that contain the dialogs and objectives.

===Dialogs===
---
The dialogs of each mission go into a file (any file, as long as it is a .ini file. Moreover, two or more mission's dialogs could go into one or more files, although that's not encouraged. Best to keep things nice and tidy) in the \universe\texts\dialogs\ folder.
The dialog syntaxis is as follows:
<pre>
Dialog
<content>
END
</pre>
with the content being:

*name <identifier number of the dialog, the one that links the dialog to the mission>
*Layout <where it's located on the screen, see the manual>
*NPC <id number of the npc saying this>
*distort <num ranging from -1 to 3> it's the level of interference in a dialog (with -1 being none whatsoever)
*ExpireEvent <event to occur when the dialog ends (in the same state where the dialog was called, of course)>
Here is the text build of each dialog:
<pre>
text
{
<language (0 for english, 2 for spanish, 1 for hungarian...)> "<content>"
}
</pre>
Here are the dialogs corresponding to the [[Demo_mission|Demo mission]]: [[Demo_mission#Dialogs|Dialogs]]

in case of being this a dialog with a choice system built-in, a few thigs are added:

*ChooseTime <num in seconds> the ammount of time the dialog stays on the air by itself

and the text build will look something like this:
<pre>
text
{
<language1> "<text in language 1>"
<language2> "<in language 2>"
.........
}
options
{
<language1> "<1° choice in language 1>"
<language2> "<in language 2>"

.........
}
<event generated by choice 1>
{
<language1> "<2° choice in language 1>"
<language2> "<in language 2>"

.........
}
<event generated by choice 2>

............

{
<language1> "<n° choice in language 1>"
<language2> "<in language 2>"

.........
}
<event generated by choice n>
END
</pre>
unfortunately, there aren't any dialogs with such choices in the [[Demo_mission|Demo mission]], but I can provid you with an example, taken from my mission "Consequences" available in the Stargate Mod: War Begins PB4, 5, 6 and 7 (at the time this article was written):

<pre>
DIALOG
name dialog_consequences_c2_4
Layout 6
ExpireEvent TimerFail
NPC 9
distort -1
text
{
0 "They aren't respondind sir, and they are charging weapons. What do we do sir? Fight or flee?"
}
options
{
0 "We fight. All hands to battle stations!"
}
Fight

{
0 "We came here to fight the replicators, no the Lucians. Major, get us out of here."
}
Flee

END //we end the choices
END
</pre>

===Objectives===
---
The Objectives of a mission go into any file (in pretty much the same way that the dialogs) in the \universe\texts\mod_texts\ or in the \universe\texts\texts\ folders. Each dialog is linked to a mission with the mission's number, in this fashion:
<pre>
TEXT "objective_<num of mission>_<numv of objective>"
<language> "<text in that language>"
END
</pre>
And that's pretty much it. The [[Demo_mission|Demo Mission's]] objectives are located [[Demo_mission#Objectives|here]]

← Older revision		Revision as of 21:09, 15 August 2012
Line 320:		Line 320:
	END		END
	</pre>		</pre>
−
−	n വശങ ങള ണ ട ങ ക ല n ശ ര ഷങ ങള ണ ട . n ശ ര ഷങ ങള ല ന ന ന രണ ട ശ ര ഷങ ങള എത ര വ ധത ത ല ത ര ഞ ഞ ട ക ക ? Permutations and Combinations പര ചയമ ള ളവര ക ക , ഉത തര വ ഗ പറയ : nC2 = n (n-1) /2 . ഇങ ങന ക ട ട ന ന രണ ട ശ ര ഷങ ങള യ ജ പ പ ച ച ല ഒന ന ക ല അത ഒര വശമ യ ര ക ക , അല ല ങ ക ല ഒര വ കര ണമ യ ര ക ക . അപ പ ള വശങ ങള ട യ വ കര ണങ ങള ട യ ആക എണ ണ n (n-1) /2 എന ന മനസ സ ല ക ക . പക ഷ വശങ ങള ട എണ ണ n ആണ ന ന നമ ക ക അറ യ . അത ന ല വ കര ണങ ങള ട എണ ണ = [ n (n-1) /2 ] - n = n (n-3) / 2n ശ ര ഷങ ങള ല (വസ ത ക കള ല ) ന ന ന രണ ട ശ ര ഷങ ങള (വസ ത ക കള ) എത ര വ ധത ത ല ത ര ഞ ഞ ട ക ക ? ഈ ച ദ യത ത ന റ ഉത തര n -ന വ യതസ ത വ ലകള ക ട ത ത പര ശ ധ ച ച കണ ട ത ത . വ ണമ ങ ക ല ഇത ഒര ക ച ച assignment ആയ നല ക .വ ല കഷ ണ :"ശ ര വണ നല ല ര കണക കധ യ പ കയ ണ . ഒര സര ക ക ര വ ദ യ ലയത ത ല പഠ പ പ ക ക ന ന . ഒന പത ക ല സ ല പ ത യ പ ഠപ സ തക പഠ പ പ ക ക ന ഒര ങ ങ കയ ണ . " "ഈ ട ച ചര ക ക എന ത പറ റ എന ന യ ച ല വ ര തന മ ര . അമ മ വ ണ ആദ യ പറഞ ഞത . "" ശ ര വണ ട ച ചര വ ട ട ല ല.""ഇത ര പ ര ജക ട ന റ ത ടക കമ യ ര ന ന അമ മ , അന റ ണ , ശ ര ക ക ട ടന , റ യ സ , സ മ ന എന ന വര ഗ ര പ പ യ .അവര പ ര ജക ട ന ഒര പ ര ട ട ."ഇങ ങന യ ള ള ക ര യങ ങള ച ര ത ത ഗണ ത ചര ച ചച യ യ ന നത ക ണ ട എന ത ങ ക ല വ ശ ഷ ച ച പ രയ ജന ഉണ ട ? ജ ണ സ റ ന റ ശ ല യ വ മര ശ ക ക കയല ല, സ ക ള ഗണ തപ സ തകങ ങള ല ച ദ യ പ പ പറ കള ല ഇപ പ ള കണ ട വര ന ന ഈ മ റ റ ( ജ ണ സ ര ഈ മ റ റത ത ന ച ര വ ധ എഴ ത യത ണ ന ന വ ച ര ക ക ന ന ) യഥ ര ത ഥത ത ല ഗ ണ ച യ യ ന ന ണ ട എന ന ര ശങ ക ത ന ന ന നത ക ണ ട ണ ഇത ന നയ ക ക ന നത . ക ട ട കള ഇത ഷ ടപ പ ട ന ന ണ ട (ഇഷ ടപ പ ട ന ന ന ട ങ ക ല തന ന ഏത ര ത യ ല ള ള ഇഷ ട ? ), ഇങ ങന പറയ ന പ ള ഗണ ത ക ട തല രസകരമ ക ന ന ണ ട , അത ഗണ തത ത ന റ അട സ ഥ ന ആശയങ ങള ല ന ന ന ച ന ത ര ത യ ല ന ന ന വ ശകലനര ത യ ല ന ന ന വഴ മ റ പ പ ക ന ണ ഇത ക ട ട കള പ ര ര പ പ ക ക ന നത ? ഒര തമ ശക കഥ വ യ ക ക ക

@@ Line 321: / Line 321: @@
 </pre>
-===Objectives===
+n വശങ ങള ണ ട ങ ക ല   n  ശ ര  ഷങ ങള ണ ട . n  ശ ര  ഷങ ങള ല   ന ന ന  രണ ട  ശ ര  ഷങ ങള    എത ര വ ധത ത ല   ത ര ഞ ഞ ട ക ക  ? Permutations and Combinations പര ചയമ ള ളവര  ക ക , ഉത തര  വ ഗ  പറയ  : nC2 = n (n-1) /2 . ഇങ ങന ക ട ട ന ന രണ ട  ശ ര  ഷങ ങള  യ ജ പ പ ച ച ല   ഒന ന ക ല   അത   ഒര  വശമ യ ര ക ക  , അല ല ങ ക ല   ഒര  വ കര  ണമ യ ര ക ക  . അപ പ ള   വശങ ങള ട യ      വ കര  ണങ ങള ട യ    ആക  എണ ണ  n (n-1) /2 എന ന  മനസ സ ല ക ക  . പക ഷ  വശങ ങള ട  എണ ണ  n ആണ ന ന  നമ ക ക  അറ യ  . അത ന ല   വ കര  ണങ ങള ട  എണ ണ   = [ n (n-1) /2 ] - n = n (n-3) / 2n  ശ ര  ഷങ ങള ല   (വസ ത ക കള ല  )  ന ന ന  രണ ട  ശ ര  ഷങ ങള   (വസ ത ക കള  )  എത ര വ ധത ത ല   ത ര ഞ ഞ ട ക ക  ? ഈ ച ദ യത ത ന റ  ഉത തര   n -ന  വ യതസ ത വ ലകള   ക ട ത ത   പര ശ ധ ച ച  കണ ട ത ത  . വ ണമ ങ ക ല   ഇത  ഒര  ക ച ച    assignment ആയ   നല  ക  .വ ല  കഷ ണ  :"ശ ര വണ  നല ല ര  കണക കധ യ പ കയ ണ . ഒര  സര  ക ക ര   വ ദ യ ലയത ത ല   പഠ പ പ ക ക ന ന . ഒന  പത   ക ല സ ല  പ ത യ പ ഠപ സ തക  പഠ പ പ ക ക ന   ഒര ങ ങ കയ ണ . " "ഈ ട ച ചര  ക ക  എന ത പറ റ  എന ന യ  ച ല വ ര തന മ ര  . അമ മ വ ണ  ആദ യ  പറഞ ഞത . "" ശ ര വണ ട ച ചര   വ ട ട ല ല.""ഇത ര  പ ര ജക ട ന റ  ത ടക കമ യ ര ന ന അമ മ , അന റ ണ , ശ ര ക ക ട ടന  , റ യ സ  , സ മ ന  എന ന വര   ഗ ര പ പ യ .അവര   പ ര ജക ട ന  ഒര  പ ര ട ട ."ഇങ ങന യ ള ള ക ര യങ ങള   ച ര  ത ത  ഗണ ത  ചര  ച ചച യ യ ന നത ക ണ ട  എന ത ങ ക ല   വ ശ ഷ ച ച  പ രയ ജന  ഉണ ട ? ജ ണ   സ റ ന റ   ശ ല യ   വ മര  ശ ക ക കയല ല,   സ ക ള   ഗണ തപ സ തകങ ങള ല   ച ദ യ പ പ പറ കള ല    ഇപ പ ള   കണ ട വര ന ന ഈ മ റ റ ( ജ ണ   സ ര   ഈ മ റ റത ത ന  ച ര  വ ധ  എഴ ത യത ണ ന ന  വ ച ര ക ക ന ന  ) യഥ ര  ത ഥത ത ല    ഗ ണ  ച യ യ ന ന ണ ട  എന ന ര ശങ ക ത ന ന ന നത ക ണ ട ണ   ഇത ന നയ ക ക ന നത . ക ട ട കള   ഇത ഷ ടപ പ ട ന ന ണ ട  (ഇഷ ടപ പ ട ന ന ന ട ങ ക ല    തന ന  ഏത  ര ത യ ല ള ള  ഇഷ ട ? ), ഇങ ങന  പറയ ന പ ള   ഗണ ത  ക ട തല   രസകരമ ക ന ന ണ ട , അത   ഗണ തത ത ന റ  അട സ ഥ ന ആശയങ ങള ല  ന ന ന    ച ന ത ര ത യ ല  ന ന ന   വ ശകലനര ത യ ല  ന ന ന   വഴ മ റ പ പ ക ന ണ  ഇത  ക ട ട കള  പ ര ര പ പ ക ക ന നത ?  ഒര  തമ ശക കഥ  വ യ ക ക ക
 ---
-The Objectives of a mission go into any file (in pretty much the same way that the dialogs) in the \universe\texts\mod_texts\ or in the \universe\texts\texts\ folders. Each dialog is linked to a mission with the mission's number, in this fashion:
-<pre>
-TEXT "objective_<num of mission>_<numv of objective>"
-	<language> "<text in that language>"
-END
-</pre>
-And that's pretty much it. The [[Demo_mission|Demo Mission's]] objectives are located [[Demo_mission#Objectives|here]]

@@ Line 47: / Line 47: @@
 *The setting of the variables associated to each of the ships that will appear on the mission (though critical for most missions, it's not mandatory), defined by the command <name of the variable> := [[GetSceneObj]]("<name of the ship>");
-This rule is special also because it's the first link to any of the Machines you've written for this mission, in here you call the Machines (or Machines) you want your mission to start with.
+This rule is special also because it's the first link to any of the Machines you've written for this mission, in here you call the Machine (or Machines) you want your mission to start with.
 Unlike any other Rule, this one doesn't go inside a State, it only goes beneath the "RULES" block, as all the Machines in your mission do.
 Here's the [[Demo_mission#SceneInit|SceneInit]] rule of the [[Demo_mission|Demo mission]], as well as the start of the "RULES" block:

@@ Line 5: / Line 5: @@
 ==''The main parts of the mission''==
-Here area a collection of the main parts a mission is divided into
+Here is a collection of the main parts a mission is divided into
@@ Line 13: / Line 13: @@
 Each mission starts, of course, with the basics of the mission: it's identity number, it's name, and where it'll take place (note that you can't change locations in a single mission):
 <pre>
-NUMBER <num>
+MISSION <num>
 name "<the name of the mission>"
 DefLocation "<name of the location>"

@@ Line 268: / Line 268: @@
 	options
+		{
-			<language1> "<1� choice in language 1>"
+			<language1> "<1° choice in language 1>"
 			<language2> "<in language 2>"
@@ Line 275: / Line 275: @@
 		<event generated by choice 1>
+		{
-			<language1> "<2� choice in language 1>"
+			<language1> "<2° choice in language 1>"
 			<language2> "<in language 2>"

@@ Line 1: / Line 1: @@
 ='''''NEXUS TJI mission-making'''''=
-As you probably know by now, thanks to Arparso's great tuturial about [[Nexus:TJI_Scripting_Structure|Nexus's scripting structure]], that every mission in this game is divided in MACHINES, STATES, and Rules. But that only deals with one part of the mission, the "body" of it, in a way.
+As you probably know by now, thanks to Arparso's great tutorial about [[Nexus:TJI_Scripting_Structure|Nexus's scripting structure]], that every mission in this game is divided in MACHINES, STATES, and Rules. But that only deals with one part of the mission, the "body" of it, in a way.
-In order to ilustrate this concepts I will be pasteing here a [[Demo_mission|Demo mission]] I've made with this article in mind.
+In order to illustrate this concepts I will be pasting here a [[Demo_mission|Demo mission]] I've made with this article in mind.
 ==''The main parts of the mission''==
@@ Line 18: / Line 18: @@
 </pre>
 The "name of the location" is a "navpoint" created with the Solar System editor, one you can find in the "universe\systems\" folder.
-Unlike the number, the name of the mission doesn't have to be unique, you can put anything in there, even the same title that some other mission, as long as the numbering is not the same (well... that's not enteryle true... if you place a letter istead of a number, the game will treat it as a mission number "0" and it will never give you a conflict, even if you label two or more missions as "NUMBER A").
+Unlike the number, the name of the mission doesn't have to be unique, you can put anything in there, even the same title that some other mission, as long as the numbering is not the same (well... that's not entirely true... if you place a letter instead of a number, the game will treat it as a mission number "0" and it will never give you a conflict, even if you label two or more missions as "NUMBER A").
 Following that is a list of the current objective numbers, in this fashion:
 <pre>
@@ Line 27: / Line 27: @@
 END
 </pre>
-Finally, as an example, here's the [[Demo_mission#Heading|Demo mission's heading]] (note that everything after "//" and between "/* - */" is interpretated by the game as a comment):
+Finally, as an example, here's the [[Demo_mission#Heading|Demo mission's heading]] (note that everything after "//" and between "/* - */" is interpreted by the game as a comment):
 <pre>
 MISSION 1  //mission number
@@ Line 33: / Line 33: @@
 DefLocation "NAV_CHAKRIS_IV"  //the location where the mission will take place
-OBJECTIVES //in here we place the number of objectives that will be includid in the mission
+OBJECTIVES //in here we place the number of objectives that will be included in the mission
@@ Line 44: / Line 44: @@
 This is a very special rule, critical to any mission, and that is for the fact that this rule takes place '''before''' the mission starts. In this rule you can do pretty much anything you want, but there are a few things mandatory to do here.
-*The radious of the mission, in meters, as defined by the [[SetSceneRadius]](<num>); command.
+*The radius of the mission, in meters, as defined by the [[SetSceneRadius]](<num>); command.
 *The setting of the variables associated to each of the ships that will appear on the mission (though critical for most missions, it's not mandatory), defined by the command <name of the variable> := [[GetSceneObj]]("<name of the ship>");
@@ Line 97: / Line 97: @@
 ===The body of the mission===
 ---
-The sintax of this part has already been brilliantly explainied by Arparso in his [[Nexus:TJI_Scripting_Structure|Tutorial]], so I will only offer some advices here. Always use different states when there's a remarkable change in the mission (arrival of ships, discovery of stuff, etc), and try to keep your mission as tidy as possible. Machines can run simultaneosly, so having a lot of them is never a good idea. Try to divide them into clear, diferencied tasks (one of the AI, one or two for the actual mission, etc).
+The sintax of this part has already been brilliantly explained by Arparso in his [[Nexus:TJI_Scripting_Structure|Tutorial]], so I will only offer some advices here. Always use different states when there's a remarkable change in the mission (arrival of ships, discovery of stuff, etc), and try to keep your mission as tidy as possible. Machines can run simultaneously, so having a lot of them is never a good idea. Try to divide them into clear, differenced tasks (one of the AI, one or two for the actual mission, etc).
 So, here's the body of the [[Demo_mission|Demo mission]]: [[Demo_mission#body|body]]
-Also, don't forget that once you've finished with all your machines, included all the files that you wanted to include (to include a file you have to do this: "#include "<name of the file" ", and it would be like you wrote the content of that file in the mission file, so keep a close watch on the mission sintaxis of included files!) you have to '''END''' the mission. Just add a finall ''END'' on the bottom, after the last included file and just above the ''ENTITIES'' section.
+Also, don't forget that once you've finished with all your machines, included all the files that you wanted to include (to include a file you have to do this: "#include "<name of the file" ", and it would be like you wrote the content of that file in the mission file, so keep a close watch on the mission syntax when including files!) you have to '''END''' the mission. Just add a final ''END'' on the bottom, after the last included file and just above the ''ENTITIES'' section.
 ===The ''ENTITIES'' section===
@@ Line 226: / Line 226: @@
 ==''Auxiliary parts of a mission''==
 ---
-I'll now move to explain two other files linked to every mission. Although they're not critical to a mission, they're adviced to be included, as they're the files that contain the dialogs and objectives.
+I'll now move to explain two other files linked to every mission. Although they're not critical to a mission, they're advised to be included, as they're the files that contain the dialogs and objectives.
 ===Dialogs===
 ---
 The dialogs of each mission go into a file (any file, as long as it is a .ini file. Moreover, two or more mission's dialogs could go into one or more files, although that's not encouraged. Best to keep things nice and tidy) in the \universe\texts\dialogs\ folder.
-The dialog syntaxis is as follows:
+The dialog syntax is as follows:
 <pre>
 Dialog
@@ Line 248: / Line 248: @@
 	text
+	{
-				<language (0 for english, 2 for spanish, 1 for hungarian...)> "<content>"
+				<language (0 for English, 2 for Spanish, 1 for Hungarian...)> "<content>"
+	}
 </pre>
@@ Line 254: / Line 254: @@
-in case of being this a dialog with a choice system built-in, a few thigs are added:
+in case of being this a dialog with a choice system built-in, a few things are added:
-*ChooseTime <num in seconds> the ammount of time the dialog stays on the air by itself
+*ChooseTime <num in seconds> the amount of time the dialog stays on the air by itself
 and the text build will look something like this:
@@ Line 268: / Line 268: @@
 	options
+		{
-			<language1> "<1° choice in language 1>"
+			<language1> "<1� choice in language 1>"
 			<language2> "<in language 2>"
@@ Line 275: / Line 275: @@
 		<event generated by choice 1>
+		{
-			<language1> "<2° choice in language 1>"
+			<language1> "<2� choice in language 1>"
 			<language2> "<in language 2>"
@@ Line 285: / Line 285: @@
+		{
-			<language1> "<n° choice in language 1>"
+			<language1> "<n� choice in language 1>"
 			<language2> "<in language 2>"
@@ Line 304: / Line 304: @@
 	text
+	{
-"They aren't respondind sir, and they are charging weapons. What do we do sir? Fight or flee?"
+"They aren't responding sir, and they are charging weapons. What do we do sir? Fight or flee?"
+	}
          options