65
edits
This wiki is a read-only version of the Stardew Valley Wiki. The official editable wiki maintained by ConcernedApe can be found at stardewvalleywiki.com
Changes
Created page with "← Index This page is a collection of notes and hypotheses about how the game stores schedule data for NPCs. Schedule data determines the times and locatio..."
← [[Modding:Index|Index]]
This page is a collection of notes and hypotheses about how the game stores schedule data for NPCs. Schedule data determines the times and locations where the relevant NPC actor is, moves to, and the animations it displays meanwhile.
==Data==
The schedule data is stored under /Content/Characters/schedules/ and its subfolders in character-specific XNB files.
===Format===
;Note: most of this section is unconfirmed and presumed to work similarly to the format of dialogue data.
<source lang="yaml">
"<preface>[heart level]_[date]_[year][suffix]": "String"
</source>
...where:
* {{t|preface}} is an arbitrary key which identifies the occasion(s) the schedule is for.
* {{o|heart level}} is the ''minimum'' heart level the player must have reached with the NPC for this schedule to be executed.
* {{o|date}} is the numeric day of the month (like _28_), or the three-character weekday (like _Mon_).
* {{o|year}} is _1_ for year one, or _2_ for any year after that.
* {{o|suffix}} is any string further identifying the dialogue (like <tt>_inlaw_Abigail</tt>, for dialogue that only appears when you're married to Abigail).
If multiple dialogues are eligible, the game prioritises by the following:
# marriage status;
# preface;
# suffix;
# in-law status;
# day of month;
# year;
# heart level;
# day of week.
<source lang="yaml">
"<key>": "schedule event/schedule event/schedule event",
</source>
==Format==
Schedule events are separated by slashes (/) and written in the following format:
<source lang="yaml">
<time> <map> <coord x y> <?> <animation>
</source>
* {{t|time}} is the time at which the schedule event begins, in 24 hour format, without a colon
* {{o|map}} is the map on which the target location is
* {{o|coord x y}} is the x and y coordinates of the target location, without a comma
* {{o|?}} TODO; possibly the direction the NPC actor shall stand once reaching the target location
* {{o|animation}} (optional): is the animation the NPC actor will execute at reaching the target location.
At {{t|time}} the NPC begins to travel to the target location. Once there, {{a|animation}} is executed until the next schedule event begins. There is possibly no limit to how many schedule events one schedule entry may contain.
[[Category:Modding]]
This page is a collection of notes and hypotheses about how the game stores schedule data for NPCs. Schedule data determines the times and locations where the relevant NPC actor is, moves to, and the animations it displays meanwhile.
==Data==
The schedule data is stored under /Content/Characters/schedules/ and its subfolders in character-specific XNB files.
===Format===
;Note: most of this section is unconfirmed and presumed to work similarly to the format of dialogue data.
<source lang="yaml">
"<preface>[heart level]_[date]_[year][suffix]": "String"
</source>
...where:
* {{t|preface}} is an arbitrary key which identifies the occasion(s) the schedule is for.
* {{o|heart level}} is the ''minimum'' heart level the player must have reached with the NPC for this schedule to be executed.
* {{o|date}} is the numeric day of the month (like _28_), or the three-character weekday (like _Mon_).
* {{o|year}} is _1_ for year one, or _2_ for any year after that.
* {{o|suffix}} is any string further identifying the dialogue (like <tt>_inlaw_Abigail</tt>, for dialogue that only appears when you're married to Abigail).
If multiple dialogues are eligible, the game prioritises by the following:
# marriage status;
# preface;
# suffix;
# in-law status;
# day of month;
# year;
# heart level;
# day of week.
<source lang="yaml">
"<key>": "schedule event/schedule event/schedule event",
</source>
==Format==
Schedule events are separated by slashes (/) and written in the following format:
<source lang="yaml">
<time> <map> <coord x y> <?> <animation>
</source>
* {{t|time}} is the time at which the schedule event begins, in 24 hour format, without a colon
* {{o|map}} is the map on which the target location is
* {{o|coord x y}} is the x and y coordinates of the target location, without a comma
* {{o|?}} TODO; possibly the direction the NPC actor shall stand once reaching the target location
* {{o|animation}} (optional): is the animation the NPC actor will execute at reaching the target location.
At {{t|time}} the NPC begins to travel to the target location. Once there, {{a|animation}} is executed until the next schedule event begins. There is possibly no limit to how many schedule events one schedule entry may contain.
[[Category:Modding]]
