Dialog editor - Revision history

Fandrfa: /* IsUserFlag */

2018-06-12T03:30:43Z

IsUserFlag

← Older revision		Revision as of 03:30, 12 June 2018
Line 828:		Line 828:
	Check if speaker's character flag has certain value. If that speaker is not present, the result will always be '''false'''.		Check if speaker's character flag has certain value. If that speaker is not present, the result will always be '''false'''.

	==== ~~IsUserFlag~~ ====		==== IsPartyFlag ====
	CONDITION IsPartyFlag(SpeakerIndex, FlagName, Bool)		CONDITION IsPartyFlag(SpeakerIndex, FlagName, Bool)

	Check if speaker's party flag has certain value. If that speaker is not present, the result will always be '''false'''.		Check if speaker's party flag has certain value. If that speaker is not present, the result will always be '''false'''.


	==== IsUserFlag ====		==== IsUserFlag ====

Tinkerer: /* HasAbility */

2018-01-11T12:29:25Z

HasAbility

← Older revision		Revision as of 12:29, 11 January 2018
Line 878:		Line 878:
	CONDITION HasAbility(SpeakerIndex, AbilityID, Level)		CONDITION HasAbility(SpeakerIndex, AbilityID, Level)

	Check speaker has ability at level "Level" or higher. AbilityID is a string from the [[Scripting_ability_types\|scripting ability types]] list.		Check that the speaker at SpeakerIndex has the specified ability at level "Level" or higher. AbilityID is a string from the [[Scripting_ability_types\|scripting ability types]] list.

	==== IsTagged ====		==== IsTagged ====

Tinkerer: /* IsUserFlag */ de-duplicated mix-up of IsUserFlag and IsPartyFlag

2018-01-11T12:28:51Z

IsUserFlag: de-duplicated mix-up of IsUserFlag and IsPartyFlag

← Older revision		Revision as of 12:28, 11 January 2018
Line 830:		Line 830:
	==== IsUserFlag ====		==== IsUserFlag ====
	CONDITION IsPartyFlag(SpeakerIndex, FlagName, Bool)		CONDITION IsPartyFlag(SpeakerIndex, FlagName, Bool)

			Check if speaker's party flag has certain value. If that speaker is not present, the result will always be '''false'''.


			==== IsUserFlag ====
			CONDITION IsUserFlag(SpeakerIndex, FlagName, Bool)

	Check if speaker's user flag has certain value. If that speaker is not present, the result will always be '''false'''.		Check if speaker's user flag has certain value. If that speaker is not present, the result will always be '''false'''.

Tinkerer: /* HasAbility */ Clarified and link to list of valid strings

2018-01-11T12:27:08Z

HasAbility: Clarified and link to list of valid strings

← Older revision		Revision as of 12:27, 11 January 2018
Line 872:		Line 872:
	CONDITION HasAbility(SpeakerIndex, AbilityID, Level)		CONDITION HasAbility(SpeakerIndex, AbilityID, Level)

	Check speaker has ability ~~no lower then of certain~~ level. AbilityID is string.		Check speaker has ability at level "Level" or higher. AbilityID is a string from the [[Scripting_ability_types\|scripting ability types]] list.

	==== IsTagged ====		==== IsTagged ====

LarIlya at 08:05, 9 January 2018

2018-01-09T08:05:31Z

← Older revision		Revision as of 08:05, 9 January 2018
Line 45:		Line 45:

	== Voice bark ==		== Voice bark ==
	A voice bark ~~behaves the same same as~~ an [[#Automated NPC Dialog\|Automated NPC Dialog]] in DOS2.		A voice bark is an [[#Automated NPC Dialog\|Automated NPC Dialog]] intended to be used with a [[Voice_Bark_editor\|voicebark]] and functions the same in DOS2.

	== Ghost Dialog ==		== Ghost Dialog ==

Tinkerer: typo fix

2017-11-26T12:02:22Z

typo fix

← Older revision		Revision as of 12:02, 26 November 2017
Line 729:		Line 729:
	Un-setting a Flag is done by unchecking the checkbox in front of the Flag's name.		Un-setting a Flag is done by unchecking the checkbox in front of the Flag's name.

	==== Visual ~~Cueu~~ ====		==== Visual Cue ====
	When a Text Node is setting Flags a little square is shown on the '''right''' of the Node. Hovering over this squares shows which Flags are being set by that Node:		When a Text Node is setting Flags a little square is shown on the '''right''' of the Node. Hovering over this squares shows which Flags are being set by that Node:
	<br/>		<br/>

Tinkerer: /* Dialog Categories */

2017-11-05T16:55:04Z

Dialog Categories

← Older revision		Revision as of 16:55, 5 November 2017
Line 45:		Line 45:

	== Voice bark ==		== Voice bark ==
			A voice bark behaves the same same as an [[#Automated NPC Dialog\|Automated NPC Dialog]] in DOS2.

	== Ghost Dialog ==		== Ghost Dialog ==
Line 68:		Line 69:
	== Automated ==		== Automated ==
	This checkbox must be checked for all automated dialogs. It is what actually determines whether a dialog is started in interactive or non-interactive mode. The difference between the automated and non-automated categories above are used by different systems (mainly sound).		This checkbox must be checked for all automated dialogs. It is what actually determines whether a dialog is started in interactive or non-interactive mode. The difference between the automated and non-automated categories above are used by different systems (mainly sound).

			All dialogs with this checkbox checked treat tag checks for the origin companions (IFAN, BEAST, ...) the same as their shapeshifted versions (SHAPESHIFT_IFAN, SHAPESHIFT_BEAST, ...).

	= Nodes =		= Nodes =

Tinkerer: /* Speakers */

2017-10-24T15:28:24Z

Speakers

← Older revision		Revision as of 15:28, 24 October 2017
Line 159:		Line 159:
	Every dialogue is written for a certain set of characters. These characters are the actors of the dialogue. Every dialogue keeps these actors in a list, called the Speakers. They indicate who says what in the dialogue. This Speaker list has a certain order. For example, say we have a dialogue between Bill and Ted. Bill would be speaker 1 (and be in the first slot) and Ted would be speaker 2 (and be in the second slot). Nodes refers to these slot to see who's saying the text contained in.		Every dialogue is written for a certain set of characters. These characters are the actors of the dialogue. Every dialogue keeps these actors in a list, called the Speakers. They indicate who says what in the dialogue. This Speaker list has a certain order. For example, say we have a dialogue between Bill and Ted. Bill would be speaker 1 (and be in the first slot) and Ted would be speaker 2 (and be in the second slot). Nodes refers to these slot to see who's saying the text contained in.

	In our dialogues players will always be the last Speakers in the list. That's because we can have dialogues where depending on the situation more than 1 player can be active in a dialogue. Since we don't want to disrupt the order of the other Speakers, we add players in the back.\		In our dialogues players will always be the last Speakers in the list. That's because we can have dialogues where depending on the situation more than 1 player can be active in a dialogue. Since we don't want to disrupt the order of the other Speakers, we add players in the back.

	For Question nodes, the Speaker of the node also determines who has to select the question.		For Question nodes, the Speaker of the node also determines who has to select the question.

Tinkerer: /* Dialog Variable Editor */

2017-10-22T17:57:19Z

Dialog Variable Editor

← Older revision		Revision as of 17:57, 22 October 2017
Line 910:		Line 910:
	If the data type of the _Value that you're passing doesn't match the data type of the variable you will get an assert and no value will be stored.		If the data type of the _Value that you're passing doesn't match the data type of the variable you will get an assert and no value will be stored.

			=== Using Dialog Variables in Dialog Text ===
			You can use use the values of dialog variables directly in the text of you dialog. To do so, copy the '''Name_UUID''' field of the dialog variable and place it your node text between square brackets. E.g.
			Give [GEN_CheckMagicPocketGold_6057ad05-9492-4630-9f0a-be548b134c54] gold pieces

	= Searching Through Dialogues =		= Searching Through Dialogues =

Tinkerer: Fixed various internal navigation links

2017-10-22T13:48:13Z

Fixed various internal navigation links

Show changes