ContentDesigner:Creating Conversations - Revision history

Cynnar at 02:07, 26 September 2015

2015-09-26T02:07:43Z

Cynnar at 09:18, 11 September 2015

2015-09-11T09:18:58Z

Cynnar at 09:14, 11 September 2015

2015-09-11T09:14:20Z

Cynnar at 09:11, 11 September 2015

2015-09-11T09:11:32Z

Cynnar at 08:35, 11 September 2015

2015-09-11T08:35:12Z

Cynnar at 08:33, 11 September 2015

2015-09-11T08:33:55Z

Cynnar at 08:29, 11 September 2015

2015-09-11T08:29:31Z

Cynnar at 08:27, 11 September 2015

2015-09-11T08:27:39Z

Cynnar at 08:26, 11 September 2015

2015-09-11T08:26:33Z

Cynnar at 08:22, 11 September 2015

2015-09-11T08:22:43Z

← Older revision		Revision as of 02:07, 26 September 2015
Line 95:		Line 95:
	\|}		\|}
	As you can see this function looks a lot like the hailed function. The main changes are that ''function hailed'' was changed to ''function Chat_0_1'', is not using ''PlayFlavor'', only has one ''AddConversationOption'', now has ''Chat_0_2'' instead of ''Chat_0_1'', what the NPC is suppose to say, and the players chat option. As you can see to create the function for Chat_0_2 would be the same as creating the Chat_0_1 function. Just a quick note. Chat_0_1, Chat_0_2 doesn't have to be exactly those. For instance if you have multiple quest you could call them QuestChat_1_1_1 if you would like. Just as long as whatever you choose to call it in the ''AddConversationOption'' is what you use in the function. Otherwise the conversation is broken.		As you can see this function looks a lot like the hailed function. The main changes are that ''function hailed'' was changed to ''function Chat_0_1'', is not using ''PlayFlavor'', only has one ''AddConversationOption'', now has ''Chat_0_2'' instead of ''Chat_0_1'', what the NPC is suppose to say, and the players chat option. As you can see to create the function for Chat_0_2 would be the same as creating the Chat_0_1 function. Just a quick note. Chat_0_1, Chat_0_2 doesn't have to be exactly those. For instance if you have multiple quest you could call them QuestChat_1_1_1 if you would like. Just as long as whatever you choose to call it in the ''AddConversationOption'' is what you use in the function. Otherwise the conversation is broken.
		+
		+
		+	[[ContentDesigner:Creating_Conversations \| On to Creating Conversations]]<br/>
		+	[[ContentDesigner:SpawnScripts \| Back to SpawnScripts]]

@@ Line 94: / Line 94: @@
 |FontColor=000000}}
 |}
-As you can see this function looks a lot like the hailed function. The main changes are that ''function hailed'' was changed to ''function Chat_0_1'', is not using ''PlayFlavor'', only has one ''AddConversationOption'', now has ''Chat_0_2'' instead of ''Chat_0_1'', what the NPC is suppose to say, and the players chat option. As you can see to create the function for Chat_0_2 would be the same as creating the Chat_0_1 function.
+As you can see this function looks a lot like the hailed function. The main changes are that ''function hailed'' was changed to ''function Chat_0_1'', is not using ''PlayFlavor'', only has one ''AddConversationOption'', now has ''Chat_0_2'' instead of ''Chat_0_1'', what the NPC is suppose to say, and the players chat option. As you can see to create the function for Chat_0_2 would be the same as creating the Chat_0_1 function. Just a quick note. Chat_0_1, Chat_0_2 doesn't have to be exactly those. For instance if you have multiple quest you could call them QuestChat_1_1_1 if you would like. Just as long as whatever you choose to call it in the ''AddConversationOption'' is what you use in the function. Otherwise the conversation is broken.

@@ Line 94: / Line 94: @@
 |FontColor=000000}}
 |}
-As you can see this function looks a lot like the hailed function. The main changes are that ''function hailed'' was changed to ''function Chat_0_1'', is not using ''PlayFlavor'', only has one ''AddConversationOption'', and now has ''Chat_0_2'' instead of ''Chat_0_1''. To create the function for Chat_0_2 would be the same as creating the Chat_0_1 function.
+As you can see this function looks a lot like the hailed function. The main changes are that ''function hailed'' was changed to ''function Chat_0_1'', is not using ''PlayFlavor'', only has one ''AddConversationOption'', now has ''Chat_0_2'' instead of ''Chat_0_1'', what the NPC is suppose to say, and the players chat option. As you can see to create the function for Chat_0_2 would be the same as creating the Chat_0_1 function.

@@ Line 81: / Line 81: @@
 Notice that this has a special addition to the NPC text ''" .. GetName(Spawn) .. "''. What this does is get the name of the player and will display that players name in the conversation. When using GetName like this you have to break the text with a quote " before and after.
+{|style="table-layout:fixed; width: 100%;"
-'''''More Comming Soon...'''''
+|{{TextBox

@@ Line 77: / Line 77: @@
 The ''AddConversationOption'' functions are the players chat options. The top most ''AddConversationOption'' function is the top most chat option. The script will execute down the line so the second ''AddConversationOption'' function will be the second chat option, and so on until reaching the ''StartConverstation'' function. There are a minimum of two parameters for a ''AddConversationOption''. The first one is ''conversation'', our variable we set earlier. The second is ''"How am I to do that?"'', and is the choice the player will see for responding to the NPC. The third is ''"Chat_0_1"''. This is needed if the NPC has a response to what the player chooses, and is a function that has to be created further down the script. If the NPC has no response then ''"Chat_0_1"'' can be removed and the line would look something like this ''AddConversationOption(conversation, "I don't think I am ready yet.")''.
-The ''StartConverstation'' function will start the conversation. This is what the NPC will be saying, and everything below this function will not be included in the conversation. There are four parameters for this function. Again we need our variable that was set earlier ''conversation''. Next is ''NPC'' and this points to Verex. After that ''Spawn'' is who will be receiving the conversation. After that is the text of what the NPC is going to say. Last is to finish the function by closing it with end.
+The ''StartConverstation'' function will start the conversation. This is what the NPC will be saying, and everything below this function will not be included in the conversation. There are four parameters for this function. Again we need our variable, ''conversation'', that was set earlier. Next is ''NPC'' and this points to Verex. After that ''Spawn'' is who will be receiving the conversation. After that is the text of what the NPC is going to say. Last is to finish the function by closing it with end.
 Notice that this has a special addition to the NPC text ''" .. GetName(Spawn) .. "''. What this does is get the name of the player and will display that players name in the conversation. When using GetName like this you have to break the text with a quote " before and after.

@@ Line 75: / Line 75: @@
 Notice that we are using ''PlayFlavor'' again but this time we have a mp3 file. There is no text or emote in this ''PlayFlavor'' function so these are just the open and close quotes "" for each one. Also this mp3 file does not need any mp3 keys so they are set to 0.
-The ''AddConversationOption'' functions are the players chat options. The top most ''AddConversationOption'' function is the top most chat option. The script will execute down the line so the second ''AddConversationOption'' function will be the second chat option, and so on until reaching the ''StartConverstation'' function. There are a minimum of two parameters for a ''AddConversationOption''. The first one is ''conversation'', our variable we set earlier. The second is ''"How am I to do that?"'', and is the choice the player will see for responding to the NPC. The third is ''"Chat_0_1"''. This is needed if the NPC has a response to what the player chooses, and is a function that has to be created further down the script. If the NPC has no response then the line would look something like this ''AddConversationOption(conversation, "I don't think I am ready yet.")''.
+The ''AddConversationOption'' functions are the players chat options. The top most ''AddConversationOption'' function is the top most chat option. The script will execute down the line so the second ''AddConversationOption'' function will be the second chat option, and so on until reaching the ''StartConverstation'' function. There are a minimum of two parameters for a ''AddConversationOption''. The first one is ''conversation'', our variable we set earlier. The second is ''"How am I to do that?"'', and is the choice the player will see for responding to the NPC. The third is ''"Chat_0_1"''. This is needed if the NPC has a response to what the player chooses, and is a function that has to be created further down the script. If the NPC has no response then ''"Chat_0_1"'' can be removed and the line would look something like this ''AddConversationOption(conversation, "I don't think I am ready yet.")''.
 The ''StartConverstation'' function will start the conversation. Everything below this function will not be included in the conversation, and this is what the NPC will be saying. There are four parameters for this function. Again we need our variable that was set earlier ''conversation''. Next is ''NPC'' and this points to Verex. After that is who will be receiving the conversation. So ''Spawn'' is pointing to the player. Last is what the NPC is going to say then finish the function by closing it with end.

@@ Line 73: / Line 73: @@
 This is where we are going to start out conversation. So when Verex is hailed it will begin the dialog. Going through the hailed function we want Verex to face the player after they hail. We use the ''FaceTarget'' function for this. First we need to create a conversation. To do this we need to use ''CreateConversation()'' and assign it to a local variable and call it ''conversation''. This how we get the ''conversation <nowiki>=</nowiki> CreateConversation()'' part of the code. Now we can add options for the player to choose from by using the ''AddConversationOption'', and finally send this conversation to the player to be displayed with StartConversation().
-Notice that we are using ''PlayFlavor'' again but this time we have a mp3 file. There is no text or emote in this ''PlayFlavor'' function so these are just the open and close quotes "". Also this mp3 file does not need any mp3 keys so they are set to 0.
+Notice that we are using ''PlayFlavor'' again but this time we have a mp3 file. There is no text or emote in this ''PlayFlavor'' function so these are just the open and close quotes "" for each one. Also this mp3 file does not need any mp3 keys so they are set to 0.
 The ''AddConversationOption'' functions are the players chat options. The top most ''AddConversationOption'' function is the top most chat option. The script will execute down the line so the second ''AddConversationOption'' function will be the second chat option and so on. There are a minimum of two parameters for a ''AddConversationOption''. The first one is ''conversation'', our variable we set earlier. The second is ''"How am I to do that?"'', and is the choice the player has to respond to the NPC. The third is ''"Chat_0_1"''. This is needed if the NPC has a response to what the player chooses, and is a function that has to be created further down the script. If the NPC has no response then the line would look something like this ''AddConversationOption(conversation, "I don't think I am ready yet.")''.