Modding:Dialogue - Revision history

imported>DolphinIsNotaFish at 23:07, 20 May 2026

2026-05-20T23:07:19Z

← Older revision		Revision as of 23:07, 20 May 2026
Line 205:		Line 205:
	Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.		Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.

	'''Note'''~~: for~~ location dialogue to work, an NPC must be giftable. If the NPC is not giftable (either because they lack gift tastes or have <samp>CanSocialize</samp> set to false), one workaround is to set their <samp>SocialTab</samp> field to <samp>AlwaysShown</samp>.		'''Note:''' For location dialogue to work, an NPC must be giftable. If the NPC is not giftable (either because they lack gift tastes or have <samp>CanSocialize</samp> set to false), one workaround is to set their <samp>SocialTab</samp> field to <samp>AlwaysShown</samp>.

	{\| class="wikitable"		{\| class="wikitable"

imported>DolphinIsNotaFish at 23:06, 20 May 2026

2026-05-20T23:06:54Z

← Older revision		Revision as of 23:06, 20 May 2026
Line 205:		Line 205:
	Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.		Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.

	Note: for location dialogue to work, an NPC must be giftable. If the NPC is not giftable (either because they lack gift tastes or have <samp>CanSocialize</samp> set to false), one workaround is to set their <samp>SocialTab</samp> field to <samp>AlwaysShown</samp>.		'''Note''': for location dialogue to work, an NPC must be giftable. If the NPC is not giftable (either because they lack gift tastes or have <samp>CanSocialize</samp> set to false), one workaround is to set their <samp>SocialTab</samp> field to <samp>AlwaysShown</samp>.

	{\| class="wikitable"		{\| class="wikitable"

imported>DolphinIsNotaFish at 23:06, 20 May 2026

2026-05-20T23:06:22Z

← Older revision		Revision as of 23:06, 20 May 2026
Line 205:		Line 205:
	Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.		Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.

	~~NOTE~~: ~~An NPC must have gift tastes specified~~ for location dialogue to work ~~if their <samp>CanSocialize</samp> field is set to true~~. If <samp>CanSocialize</samp> is set to false, ~~the~~ <samp>SocialTab</samp> field ~~must be set~~ to <samp>AlwaysShown</samp> ~~instead~~.		Note: for location dialogue to work, an NPC must be giftable. If the NPC is not giftable (either because they lack gift tastes or have <samp>CanSocialize</samp> set to false), one workaround is to set their <samp>SocialTab</samp> field to <samp>AlwaysShown</samp>.

	{\| class="wikitable"		{\| class="wikitable"

imported>DolphinIsNotaFish at 22:26, 20 May 2026

2026-05-20T22:26:39Z

← Older revision		Revision as of 22:26, 20 May 2026
Line 205:		Line 205:
	Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.		Unlike daily dialogue, location dialogue is endlessly repeatable as long as the trigger conditions are fulfilled, ''e.g.,'' Being in the location. They will not remove daily dialogue from an npc's dialogue rotation, but will merely overwrite it when the NPC is in the specified location.

	NOTE: An NPC must have gift tastes specified for location dialogue to work~~, even~~ if their <samp>CanSocialize</samp> field is set to false.		NOTE: An NPC must have gift tastes specified for location dialogue to work if their <samp>CanSocialize</samp> field is set to true. If <samp>CanSocialize</samp> is set to false, the <samp>SocialTab</samp> field must be set to <samp>AlwaysShown</samp> instead.

	{\| class="wikitable"		{\| class="wikitable"

imported>SwagChild: /* Item dialogue */ Added workaround for Accept Mermaid Pendant Dialogue.

2025-11-22T22:52:05Z

Item dialogue: Added workaround for Accept Mermaid Pendant Dialogue.

← Older revision		Revision as of 22:52, 22 November 2025
Line 113:		Line 113:
	\| <samp>RejectItem_{{t\|id}}</samp><br /><samp>RejectItem_{{t\|tag}}</samp>		\| <samp>RejectItem_{{t\|id}}</samp><br /><samp>RejectItem_{{t\|tag}}</samp>
	\| If set, the NPC will refuse to accept any matching item and show this dialogue instead. This can be by item ID (like <samp>RejectItem_(O)128</samp>) or context tag (like <samp>RejectItem_category_fish</samp>). This can prevent gifting, movie tickets, bouquets, mermaid pendants, etc. However it won't prevent accepting an item for an active quest or special order.<br /><br />Note: These dialogue keys will take precedence over the gift acceptance dialogue keys even if the rejection key is for a tag (less specific) and the acceptance key is for the ID (more specific). This means you cannot use these keys to reject a group of items (via a tag like <samp>category_gem</samp>, for example) and then use an <samp>AcceptGift_{{t\|id}}</samp> to accept only one item from within that group. Instead, you must individually reject all the unwanted items within that group.		\| If set, the NPC will refuse to accept any matching item and show this dialogue instead. This can be by item ID (like <samp>RejectItem_(O)128</samp>) or context tag (like <samp>RejectItem_category_fish</samp>). This can prevent gifting, movie tickets, bouquets, mermaid pendants, etc. However it won't prevent accepting an item for an active quest or special order.<br /><br />Note: These dialogue keys will take precedence over the gift acceptance dialogue keys even if the rejection key is for a tag (less specific) and the acceptance key is for the ID (more specific). This means you cannot use these keys to reject a group of items (via a tag like <samp>category_gem</samp>, for example) and then use an <samp>AcceptGift_{{t\|id}}</samp> to accept only one item from within that group. Instead, you must individually reject all the unwanted items within that group.
			\|-
			\|-
			\| <samp>''(Obsolete)'' give_pendant</samp>
			\| Would show when an NPC accepted a [[Mermaid's Pendant\|mermaid's pendant]] pre-1.6 update.
			As a workaround, add <samp>{{t\|NPCInternalName}}_Engaged</samp> as an entry to Strings/StringsFromCSFiles instead.
	\|-		\|-
	\| <samp>RejectMermaidPendant_AlreadyAccepted_Engaged</samp><br /><samp>RejectMermaidPendant_AlreadyAccepted_Married</samp><br /><samp>RejectMermaidPendant_AlreadyAccepted</samp><br />		\| <samp>RejectMermaidPendant_AlreadyAccepted_Engaged</samp><br /><samp>RejectMermaidPendant_AlreadyAccepted_Married</samp><br /><samp>RejectMermaidPendant_AlreadyAccepted</samp><br />

imported>Malevolent-bagel: added more detail to dialog choosing process

2025-10-29T17:22:46Z

added more detail to dialog choosing process

← Older revision		Revision as of 17:22, 29 October 2025
Line 8:		Line 8:
	===Characters\Dialogue directory===		===Characters\Dialogue directory===
	====Characters\Dialogue\{{t\|NPC}}.xnb====		====Characters\Dialogue\{{t\|NPC}}.xnb====
	An NPC's named file in <samp>~~Character~~\Dialogue</samp> contains most of their dialogue. The game will ~~choose~~ dialogue from one of the sections below, in the order shown ~~here~~.		An NPC's named file in <samp>Characters\Dialogue</samp> contains most of their dialogue. The game will select dialogue from one of the sections below, in the order shown. This means keys listed earlier in each table are checked first (and thus have higher priority), but note that some keys only apply in certain circumstances or have a random chance to be chosen, in which case lower-priority entries may appear.

	=====Special dialogue=====		=====Special dialogue=====

imported>Pathoschild: /* Special dialogue */ correction: GreenRain isn't year one only, it's the default if not overridden by GreenRain_2

2025-09-17T23:57:54Z

Special dialogue: correction: GreenRain isn't year one only, it's the default if not overridden by GreenRain_2

← Older revision		Revision as of 23:57, 17 September 2025
Line 30:		Line 30:
	\|-		\|-
	\| <samp>GreenRain</samp>		\| <samp>GreenRain</samp>
	\| ~~Dialogue during the~~ Green Rain ~~event in the first year~~.		\| Shown on [[Weather#Green Rain\|green rain]] days, unless overridden by <samp>GreenRain_2</samp>.
	\|-		\|-
	\|-		\|-
	\| <samp>GreenRain_2</samp>		\| <samp>GreenRain_2</samp>
	\| ~~Dialogue during the~~ Green Rain ~~event~~ in ~~the second~~ and subsequent years.		\| Shown on [[Weather#Green Rain\|green rain]] days in year two and subsequent years. If not set, defaults to <samp>GreenRain</samp>.
	\|-		\|-
	\| <samp>HitBySlingshot</samp>		\| <samp>HitBySlingshot</samp>

imported>Pathoschild: /* Dialogue commands */ + warning about when $query gets resolved

2025-08-23T19:04:33Z

Dialogue commands: + warning about when $query gets resolved

← Older revision		Revision as of 19:04, 23 August 2025
Line 618:		Line 618:
	"Mon": "$query !PLAYER_VISITED_LOCATION Current Mine#Did you know there's an old abandoned mine up in the mountain? Apparently it's crawling with monsters!\|I heard you went into the old mines up in the mountain!#Did you find anything tasty?$h"		"Mon": "$query !PLAYER_VISITED_LOCATION Current Mine#Did you know there's an old abandoned mine up in the mountain? Apparently it's crawling with monsters!\|I heard you went into the old mines up in the mountain!#Did you find anything tasty?$h"
	</syntaxhighlight>		</syntaxhighlight>

			'''⚠ Careful:''' the query is checked when the dialogue is parsed, which isn't always when the player speaks to the NPC. For example, the NPC may check its dialogue after it finishes pathfinding somewhere. You shouldn't expect the query to be realtime (e.g. checking the player's location or equipped items may reflect an earlier point in the day).
	\|-		\|-
	\| <samp>$r {{t\|response ID}} {{t\|friendship}} {{t\|reaction}} {{o\|observerfriendship}}#{{t\|answer text}}</samp>		\| <samp>$r {{t\|response ID}} {{t\|friendship}} {{t\|reaction}} {{o\|observerfriendship}}#{{t\|answer text}}</samp>

imported>Pathoschild: /* Special tokens */ remove secondary example for '||' (doesn't work as-is and we don't document similar interactions for the other tokens anyway)

2025-08-20T21:20:55Z

Special tokens: remove secondary example for '||' (doesn't work as-is and we don't document similar interactions for the other tokens anyway)

← Older revision		Revision as of 21:20, 20 August 2025
Line 526:		Line 526:

	You'll see the first dialogue during the entire first week, the second in the second week, the third in the third week, and then it loops back to the first dialogue on the fourth.		You'll see the first dialogue during the entire first week, the second in the second week, the third in the third week, and then it loops back to the first dialogue on the fourth.

	This can be combined with dialogue keys to achieve different effects. For example, the '<samp>6_*</samp>' dialogue key is shown on day six of each season, so this would be equivalent to seasonal dialogue:
	~~<syntaxhighlight lang="js">~~
	~~"6_*": "Spring dialogue.$h\|\|Summer dialogue.$h\|\|Fall dialogue.$h\|\|Winter dialogue.$h"~~
	~~</syntaxhighlight>~~
	\|-		\|-
	\| <samp>^</samp>		\| <samp>^</samp>

imported>Pathoschild: /* Special tokens */ tweak example to avoid gotcha

2025-08-20T21:10:41Z

Special tokens: tweak example to avoid gotcha

← Older revision		Revision as of 21:10, 20 August 2025
Line 527:		Line 527:
	You'll see the first dialogue during the entire first week, the second in the second week, the third in the third week, and then it loops back to the first dialogue on the fourth.		You'll see the first dialogue during the entire first week, the second in the second week, the third in the third week, and then it loops back to the first dialogue on the fourth.

	This can be combined with dialogue keys to achieve different effects. For example, the '<samp>6</samp>' dialogue key is shown on day six of each season, so this would be equivalent to seasonal dialogue:		This can be combined with dialogue keys to achieve different effects. For example, the '<samp>6_*</samp>' dialogue key is shown on day six of each season, so this would be equivalent to seasonal dialogue:
	<syntaxhighlight lang="js">		<syntaxhighlight lang="js">
	"6": "Spring dialogue.$h\|\|Summer dialogue.$h\|\|Fall dialogue.$h\|\|Winter dialogue.$h"		"6_*": "Spring dialogue.$h\|\|Summer dialogue.$h\|\|Fall dialogue.$h\|\|Winter dialogue.$h"
	</syntaxhighlight>		</syntaxhighlight>
	\|-		\|-