Dialogue - Revision history

Pikoyio at 04:54, 12 July 2019

2019-07-12T04:54:11Z

Arcadiaxdev: add coming soon functions for Quest TSEs

2018-05-22T13:17:23Z

add coming soon functions for Quest TSEs

DeamonHunter: Fix formatting error.

2018-02-01T13:18:11Z

Fix formatting error.

DeamonHunter: Finish dialogue.

2018-01-22T13:13:13Z

Finish dialogue.

DeamonHunter: Tutorial almost finished.

2018-01-19T14:17:54Z

Tutorial almost finished.

Show changes

DeamonHunter: Half the tutorial finished.

2018-01-19T11:15:42Z

Half the tutorial finished.

DeamonHunter: Added one last function.

2018-01-16T15:18:30Z

Added one last function.

DeamonHunter: Add new functions.

2018-01-16T15:10:22Z

Add new functions.

Show changes

DeamonHunter: Restructure page.

2018-01-11T12:25:53Z

Restructure page.

Show changes

DeamonHunter: Updated to new category.

2017-07-08T06:57:11Z

Updated to new category.

@@ Line 11: / Line 11: @@
 # Download the latest version of the editor: http://infiniteammo.com/Yarn/Yarn-2016-08-15-win.zip (Link subject to change)
 # Extract the file to a location you want.
 # Run <tt>''Yarn.exe''</tt> in the new folder.

← Older revision		Revision as of 13:17, 22 May 2018
Line 1,040:		Line 1,040:

	If a quest is ongoing, then give the player the totem associated with the quest.		If a quest is ongoing, then give the player the totem associated with the quest.
		+
		+
		+	== Coming Soon (Village-Registered TSE Functions) ==
		+	These functions main use are to register, place and track TileObjects for use in Quests.
		+
		+
		+	=== branchQuestTseOfCategoryExists ===
		+	'''Usage: <code><<branchQuestTseOfCategoryExists category 1 targetNode>></code>'''
		+
		+	parameter 1: The category of TileObject to check the village-registered quest tileobjects list for.
		+
		+	parameter 2: The amount of the tileObject to check for (will branch if there is greater than or equal to this amount of tileObjects)
		+
		+	parameter 3: Title of the node to move to
		+
		+
		+	When this function is hit, it will check the list of village-registered tileObjects for the amount of tileObjects with the category defined.
		+	If there are equal to or more tileObjects than the count defined, it will move to the specified node.
		+
		+
		+	=== placeQuestTileObjectsAtTotem ===
		+	'''Usage: <code><<placeQuestTileObjectsAtTotem totemCode tileCode 1 10>></code>'''
		+
		+	parameter 1: The code of the totem to place tileObjects around
		+
		+	parameter 2: The code of the tileObject to place
		+
		+	parameter 3: the amount of tileObjects to place
		+
		+	parameter 4: the radius around the totem in which to place the tileObjects
		+
		+	When this function is hit, it will place the defined count of tileObjects randomly around the totem defined, using the radius defined.
		+	These entities will be registered with the village for use in other Quest TSE-based commands.
		+	(If no totem with the code exists it will not place any tileObjects)

@@ Line 308: / Line 308: @@
-== Config Options ==
+= Config Options =
 == "code" ==
 '''Valid options (String): <code>A unique string which dialogue what this object is.</code>'''

@@ Line 271: / Line 271: @@
 First click on the button Asset Path and navigate upwards to the <code>/content/</code> folder. Once there, open the <code>/mods/</code> folder and create a new folder. Name this new folder to what you want the mod to be called and then open this new folder. When you open this folder give the asset a name, then click on the drop down and select ''<tt>Dialogue Asset</tt>''. Then click save, give the item a code then click OK.
-//Rest of the tutorial coming soon.
+After the asset is created, it will have been automatically selected. With that there is only one thing to do right now. Tell the game where the <tt>''"*.json"''</tt> is.
@@ Line 297: / Line 305: @@
-In order to get this Dialogue into the game you will need to follow:
+However, this Dialogue is currently useless. You will need to follow [[Dialogue Pools#Creating New Dialogue Pools]].

@@ Line 3: / Line 3: @@
-= *.dialogue File=
-== Creating a *.dialogue File ==
+= Creating New Dialogue =
 Creating this file is very simple with only two properties. The full file looks like;
@@ Line 13: / Line 139: @@
+}
 </pre>
-Both properties are self-explanatory. Make sure the dialogue property points to a file that is created by [https://www.secretlab.com.au/yarnspinner/ Yarn] otherwise some issues can arise.
+Both properties are self-explanatory. Make sure the dialogue property points to a file that is created by  otherwise some issues can arise.
@@ Line 37: / Line 163: @@
 = The Yarn *.json file =
-[https://www.secretlab.com.au/yarnspinner/ Yarn] is the program which creates the dialogue files for Staxel. It utilises it's own scripting language which can make choices and also use conditional statements in order to provide the right dialogue. They also include an [https://github.com/InfiniteAmmoInc/Yarn editor] which helps visualise these files.
+[https://www.secretlab.com.au/yarnspinner/ Yarn] is the program which creates the dialogue files for Staxel. It utilises it's own scripting language which can make choices and also use conditional statements in order to provide the right dialogue. They also include an  which helps visualise these files.
 Look at the documentation around Yarn, particularly sections such as [https://github.com/thesecretlab/YarnSpinner/blob/master/Documentation/YarnSpinner-Dialogue/Usage.md this]. Do not Yarn is changing frequently and documentation might not line up with the implementation used in Staxel.

← Older revision		Revision as of 15:18, 16 January 2018
Line 498:		Line 498:

	Give all the unclaimed items from achievements to the player.		Give all the unclaimed items from achievements to the player.
		+
		+
		+	=== giveRandomPet ===
		+	'''Usage: <code><<giveRandomPet >></code>'''
		+
		+
		+	Give a random pet to the player.

← Older revision		Revision as of 06:57, 8 July 2017
Line 1:		Line 1:
−	[[Category:Modding]] [[Category:~~VillagerModding~~]]	+	[[Category:Modding]] [[Category:Villager Modding]]
	In Staxel, there are two files which are used to specify all villager dialogue in game. These files are the *.dialogue files which point to an associated .json file that was created using [https://www.secretlab.com.au/yarnspinner/ Yarn].		In Staxel, there are two files which are used to specify all villager dialogue in game. These files are the *.dialogue files which point to an associated .json file that was created using [https://www.secretlab.com.au/yarnspinner/ Yarn].