Scenario Editor - Revision history

JYWLuca8269 at 10:17, 5 October 2021

2021-10-05T10:17:38Z

← Older revision		Revision as of 10:17, 5 October 2021
Line 1:		Line 1:
	{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}		{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}

	{{HeaderTemplate		{{HeaderTemplate
	\|welcome=Scenario Editor		\|welcome=Scenario Editor
	}}		}}

	{{SectionTemplate		{{SectionTemplate
	\|h=h3		\|h=h3

JYWLuca8269 at 16:57, 24 November 2020

2020-11-24T16:57:42Z

← Older revision		Revision as of 16:57, 24 November 2020
Line 8:		Line 8:
	\|h=h3		\|h=h3
	\|title=Scripting – Creating Scenarios		\|title=Scripting – Creating Scenarios
	\|content=		\|content=}}
	}}
	[[Scripting\|Scripting]] allows you a huge amount of control over what exactly happens on the map you are creating. You can restrict what buildings and [[Units\|units]] the players can use, set up [[Triggers\|Triggers]] to lock or unlock them, spawn units or buildings for the players or their enemies. You can send units to attack specific targets and send dialog popups to the player. Everything you need to make your own custom Scenarios.		[[Scripting\|Scripting]] allows you a huge amount of control over what exactly happens on the map you are creating. You can restrict what buildings and [[Units\|units]] the players can use, set up [[Triggers\|Triggers]] to lock or unlock them, spawn units or buildings for the players or their enemies. You can send units to attack specific targets and send dialog popups to the player. Everything you need to make your own custom Scenarios.

Line 105:		Line 104:
	*'''[[SpawnUnit\|SpawnUnit]]''' - Places a unit on the map.		*'''[[SpawnUnit\|SpawnUnit]]''' - Places a unit on the map.
	*'''[[Var_Command\|Var]]''' - Set or modify a variable. Tip: Set any variable you want to use to 0 in the initial setup trigger to avoid unpredictable results. ''All values must be integers.''		*'''[[Var_Command\|Var]]''' - Set or modify a variable. Tip: Set any variable you want to use to 0 in the initial setup trigger to avoid unpredictable results. ''All values must be integers.''


	{{SectionTemplate		{{SectionTemplate
Line 120:		Line 120:
	}}		}}
	A single trigger can do any combination of the above options. It can popup some text, spawn some units, set an objective give the player some resources and unlock some new building options. It is up to you how you want to combine and use them. Let’s take a look at some examples.		A single trigger can do any combination of the above options. It can popup some text, spawn some units, set an objective give the player some resources and unlock some new building options. It is up to you how you want to combine and use them. Let’s take a look at some examples.


	{{SectionTemplate		{{SectionTemplate
Line 127:		Line 128:
	}}		}}
	[[File:ModGuide 29.png\|frame\|center\|An attack trigger]]<br /> The above trigger is inactive, meaning it needs another trigger to call it before it will activate. Once it does it will spawn 16 units into an army and send them to attack the defined map position. This is a relatively simple trigger, but a common one. With this alone you can create scenarios that spawn waves to attack the player, grant reinforcements to the player or create surprise ambushes.		[[File:ModGuide 29.png\|frame\|center\|An attack trigger]]<br /> The above trigger is inactive, meaning it needs another trigger to call it before it will activate. Once it does it will spawn 16 units into an army and send them to attack the defined map position. This is a relatively simple trigger, but a common one. With this alone you can create scenarios that spawn waves to attack the player, grant reinforcements to the player or create surprise ambushes.


	{{SectionTemplate		{{SectionTemplate

JYWLuca8269 at 15:21, 24 November 2020

2020-11-24T15:21:55Z

← Older revision		Revision as of 15:21, 24 November 2020
Line 21:		Line 21:
	{{SectionTemplate		{{SectionTemplate
	\|h=h4		\|h=h4
	\|title=~~[[Missions (scripting)\|~~Mission Definition]]		\|title=Mission Definition
	\|content=		\|content=
	}}		}}
Line 29:		Line 29:
	{{SectionTemplate		{{SectionTemplate
	\|h=h4		\|h=h4
	\|title=~~[[Player (scripting)\|~~Player Definition]]		\|title=Player Definition
	\|content=		\|content=
	}}		}}
Line 39:		Line 39:
	{{SectionTemplate		{{SectionTemplate
	\|h=h4		\|h=h4
	\|title=[[Triggers]]		\|title=Triggers
	\|content=		\|content=
	}}		}}
Line 168:		Line 168:
	*'''Consistent Crash''' - Often happening at the start of a scenario, if you have a crash that happens every time it is likely the result of trying to spawn a unit or building with an incorrect name. For example, if the game is trying to spawn PHC_Smarty_System" it will find this building name doesn't exist and result in a crash, due to the internal reference name actually being PHC_Smarties. It's vital you get the correct internal reference names, and not all of them match their in-game display		*'''Consistent Crash''' - Often happening at the start of a scenario, if you have a crash that happens every time it is likely the result of trying to spawn a unit or building with an incorrect name. For example, if the game is trying to spawn PHC_Smarty_System" it will find this building name doesn't exist and result in a crash, due to the internal reference name actually being PHC_Smarties. It's vital you get the correct internal reference names, and not all of them match their in-game display
	*'''Empty Campaign Screen''' - If the campaign screen is empty with no campaigns or scenario missions listed, this means there is a grammar error in one of the scripts which has broken it and made it unable to be ran. You will have to identity the mistake and fix it. For example, having a Trigger without the > on the end or missing a quotation mark can cause this error. Identifying the issue can be time consuming, so it is recommended you make updates in small increments so you know where in the script the cause would be. One strategy to find these mistakes is to comment out entire sections of the script and see if the problem persists. If you have commented out a large portion of the script and then the missions are now showing up, you have narrowed down the cause and you can comment more and more specific sections to location the issue.		*'''Empty Campaign Screen''' - If the campaign screen is empty with no campaigns or scenario missions listed, this means there is a grammar error in one of the scripts which has broken it and made it unable to be ran. You will have to identity the mistake and fix it. For example, having a Trigger without the > on the end or missing a quotation mark can cause this error. Identifying the issue can be time consuming, so it is recommended you make updates in small increments so you know where in the script the cause would be. One strategy to find these mistakes is to comment out entire sections of the script and see if the problem persists. If you have commented out a large portion of the script and then the missions are now showing up, you have narrowed down the cause and you can comment more and more specific sections to location the issue.

			[[Category:Modding]]

JYWLuca8269: Updated look.

2020-11-22T21:27:03Z

Updated look.

Show changes

AlphonsoHornibro: /* Scripting – Creating Scenarios */

2018-03-13T07:13:49Z

Scripting – Creating Scenarios

← Older revision		Revision as of 07:13, 13 March 2018
Line 12:		Line 12:
	=== [[Missions (scripting)\|Mission Definition]] ===		=== [[Missions (scripting)\|Mission Definition]] ===

	First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain.[[Click here~~\|missions~~]]) to see the full list of what can be configured in mission scripting.		First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain. [[Missions (scripting)\|Click here]] to see the full list of what can be configured in mission scripting.

	=== [[Player (scripting)\|Player Definition]] ===		=== [[Player (scripting)\|Player Definition]] ===
Line 123:		Line 123:

AlphonsoHornibro: /* Scripting – Creating Scenarios */

2018-03-13T07:13:06Z

Scripting – Creating Scenarios

← Older revision		Revision as of 07:13, 13 March 2018
Line 12:		Line 12:
	=== [[Missions (scripting)\|Mission Definition]] ===		=== [[Missions (scripting)\|Mission Definition]] ===

	First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain. [[Click here]~~http://wiki.ashesofthesingularity.com/index.php/Missions_~~]~~(scripting~~) ~~for~~ the full list of what can be configured in mission scripting.		First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain.[[Click here\|missions]]) to see the full list of what can be configured in mission scripting.

	=== [[Player (scripting)\|Player Definition]] ===		=== [[Player (scripting)\|Player Definition]] ===

AlphonsoHornibro: /* Mission Definition */

2018-03-13T07:11:56Z

Mission Definition

← Older revision		Revision as of 07:11, 13 March 2018
Line 12:		Line 12:
	=== [[Missions (scripting)\|Mission Definition]] ===		=== [[Missions (scripting)\|Mission Definition]] ===

	First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain. [[Click here]]http://wiki.ashesofthesingularity.com/index.php/Missions_(scripting) for the full list of what can be configured in mission scripting.		First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain. [[Click here]http://wiki.ashesofthesingularity.com/index.php/Missions_](scripting) for the full list of what can be configured in mission scripting.

	=== [[Player (scripting)\|Player Definition]] ===		=== [[Player (scripting)\|Player Definition]] ===

AlphonsoHornibro: /* Mission Definition */

2018-03-13T07:11:32Z

Mission Definition

← Older revision		Revision as of 07:11, 13 March 2018
Line 12:		Line 12:
	=== [[Missions (scripting)\|Mission Definition]] ===		=== [[Missions (scripting)\|Mission Definition]] ===

	First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain.		First, you set up all the menu-related items (what icons/art to use in the Campaign screen, etc) and global settings like enabling/disabling creeps and hiding terrain. [[Click here]]http://wiki.ashesofthesingularity.com/index.php/Missions_(scripting) for the full list of what can be configured in mission scripting.

	=== [[Player (scripting)\|Player Definition]] ===		=== [[Player (scripting)\|Player Definition]] ===

AlphonsoHornibro at 11:34, 23 February 2018

2018-02-23T11:34:50Z

← Older revision		Revision as of 11:34, 23 February 2018
Line 123:		Line 123:






	== Fixing Issues ==		== Fixing Issues ==

AlphonsoHornibro at 11:34, 23 February 2018

2018-02-23T11:34:41Z

← Older revision		Revision as of 11:34, 23 February 2018
Line 117:		Line 117:
	[[File:Capture.jpg\|thumb\|left]]		[[File:Capture.jpg\|thumb\|left]]