Line 110: |
Line 110: |
| | | |
| ====Rain dialogue==== | | ====Rain dialogue==== |
− | <samp>Characters\Dialogue\rainy.xnb</samp> contains one dialogue entry per NPC. There's a roughly 50% chance they'll use this dialogue if one of the above didn't match, it's raining, and you're not married to or divorced from them. | + | <samp>Characters\Dialogue\rainy.xnb</samp> contains one dialogue entry per NPC. There's a roughly 50% chance they'll use this dialogue if a special or location dialogue doesn’t match, it's raining, and you're not married to or divorced from them. |
| | | |
| ====Marriage dialogue==== | | ====Marriage dialogue==== |
Line 239: |
Line 239: |
| The file has entries in the form <samp>"<key>": "dialogue string"</samp>, where the key is an arbitrary unique identifier. These must exactly match the key expected by the game, but the keys are just unique identifiers — even though most keys look like <samp>{{t|file name}}.{{t|line number}}</samp>, that's just the convention originally used to assign IDs and it has no meaning or effect (nor does it even necessarily match the current file name or line number). | | The file has entries in the form <samp>"<key>": "dialogue string"</samp>, where the key is an arbitrary unique identifier. These must exactly match the key expected by the game, but the keys are just unique identifiers — even though most keys look like <samp>{{t|file name}}.{{t|line number}}</samp>, that's just the convention originally used to assign IDs and it has no meaning or effect (nor does it even necessarily match the current file name or line number). |
| | | |
− | In most situations, if the game is unable to find a string for an NPC to say, it will default to <samp>NPC.cs.4061</samp>. (English version: "Hi.") | + | In most situations, if the game is unable to find a string for an NPC to say, it will default to <samp>NPC.cs.4061</samp> (English version: "Hi."). |
− | | |
− | '''Note while this table describes the general pattern of these comments, the _Stardrop key will not work in 1.5.6 except in Krobus's case. The other three keys can be patched to <samp>Strings/StringsFromCSFiles</samp> with the internal name of the NPC replacing <NPC> and will properly work.'''
| |
| | | |
| Some other useful NPC-specific strings stored here are as follows: | | Some other useful NPC-specific strings stored here are as follows: |
Line 250: |
Line 248: |
| ! description | | ! description |
| |- | | |- |
− | | <samp>{{t|NPC}}_AfterWedding</samp></br><samp>{{t|NPC}}_Engaged</samp></br><samp>{{t|NPC}}_EngagedRoommate</samp></br><samp>{{t|NPC}}_Stardrop</samp> | + | | <samp>{{t|NPC name}}_AfterWedding</samp> |
− | | Stored in <samp>Strings\StringsFromCSFiles.xnb</samp>. Currently only used for Krobus. Despite the name, <samp>AfterWedding</samp> is used when Krobus arrives at the farm. <samp>Stardrop</samp> is used when Krobus gifts you a [[Stardrop]]. | + | | Shown after marrying an NPC, when you talk to them on the farm on the same day. |
| + | |- |
| + | | <samp>{{t|NPC name}}_Engaged</samp></br><samp>{{t|NPC name}}_EngagedRoommate</samp> |
| + | | Shown after the NPC accepts an engagement item (e.g. [[Mermaid's Pendant|mermaid's pendant]] or [[Void Ghost Pendant|void ghost pendant]] for vanilla NPCs). |
| + | |- |
| + | | <samp>Krobus_Stardrop</samp> |
| + | | Shown when Krobus gives you the [[Stardrop#Locations|spouse stardrop]]. Other NPCs don't have an equivalent entry, and will use <samp>Strings\StringsFromCSFiles:NPC.cs.4001</samp> instead. |
| + | |
| + | {{upcoming|1.6|This no longer exists; use <samp>SpouseStardrop</samp> in <samp>Characters/Dialogue/<name></samp> instead.}}. |
| |} | | |} |
| | | |
Line 334: |
Line 340: |
| |- | | |- |
| | <samp>$0</samp> | | | <samp>$0</samp> |
− | | <samp>$k</samp> | + | | |
| | Use their neutral portrait. | | | Use their neutral portrait. |
| |- | | |- |