Difference between revisions of "Modding:Location data"
Jump to navigation
Jump to search
PortalInTime (talk | contribs) m (Corrected typo for winter forage section.) |
m (Replace deprecated <source> tags with <syntaxhighlight> tags) |
||
Line 5: | Line 5: | ||
Here is an example location: | Here is an example location: | ||
− | < | + | <syntaxhighlight lang="json"> |
"Beach": "372 .9 718 .1 719 .3 723 .3/372 .9 394 .5 718 .1 719 .3 723 .3/372 .9 718 .1 719 .3 723 .3/372 .4 392 .8 718 .05 719 .2 723 .2/129 -1 131 -1 147 -1 148 -1 152 -1 708 -1 267 -1/128 -1 130 -1 146 -1 149 -1 150 -1 152 -1 155 -1 708 -1 701 -1 267 -1/129 -1 131 -1 148 -1 150 -1 152 -1 154 -1 155 -1 705 -1 701 -1/708 -1 130 -1 131 -1 146 -1 147 -1 150 -1 151 -1 152 -1 154 -1 705 -1/384 .08 589 .09 102 .15 390 .25 330 1", | "Beach": "372 .9 718 .1 719 .3 723 .3/372 .9 394 .5 718 .1 719 .3 723 .3/372 .9 718 .1 719 .3 723 .3/372 .4 392 .8 718 .05 719 .2 723 .2/129 -1 131 -1 147 -1 148 -1 152 -1 708 -1 267 -1/128 -1 130 -1 146 -1 149 -1 150 -1 152 -1 155 -1 708 -1 701 -1 267 -1/129 -1 131 -1 148 -1 150 -1 152 -1 154 -1 155 -1 705 -1 701 -1/708 -1 130 -1 131 -1 146 -1 147 -1 150 -1 151 -1 152 -1 154 -1 705 -1/384 .08 589 .09 102 .15 390 .25 330 1", | ||
− | </ | + | </syntaxhighlight> |
Breaking it down: | Breaking it down: |
Revision as of 17:10, 19 February 2021
Data/Locations controls many things about locations.
Here is an example location:
"Beach": "372 .9 718 .1 719 .3 723 .3/372 .9 394 .5 718 .1 719 .3 723 .3/372 .9 718 .1 719 .3 723 .3/372 .4 392 .8 718 .05 719 .2 723 .2/129 -1 131 -1 147 -1 148 -1 152 -1 708 -1 267 -1/128 -1 130 -1 146 -1 149 -1 150 -1 152 -1 155 -1 708 -1 701 -1 267 -1/129 -1 131 -1 148 -1 150 -1 152 -1 154 -1 155 -1 705 -1 701 -1/708 -1 130 -1 131 -1 146 -1 147 -1 150 -1 151 -1 152 -1 154 -1 705 -1/384 .08 589 .09 102 .15 390 .25 330 1",
Breaking it down:
Index | Entry | Explanation |
---|---|---|
0 | "372 .9 718 .1 719 .3 723 .3" | Spring forage. Item ID chance. No particular order required. |
1 | "372 .9 394 .5 718 .1 719 .3 723 .3" | Summer forage. As above. |
2 | "372 .9 718 .1 719 .3 723 .3" | Fall forage. As above. |
3 | "372 .4 392 .8 718 .05 719 .2 723 .2" | Winter forage. As above. |
4 | "129 -1 131 -1 147 -1 148 -1 152 -1 708 -1 267 -1" | Fish data for spring. Fish is ID zoneNumber ID zoneNumber. Some locations have multiple fishing locations. To seperate fish, the zoneNumber is used. It starts at -1, and some locations have 0, or even 1, to indicate the zone. For more information, see Modding:Fish_data |
5 | "128 -1 130 -1 146 -1 149 -1 150 -1 152 -1 155 -1 708 -1 701 -1 267 -1" | Fish data for summer |
6 | "129 -1 131 -1 148 -1 150 -1 152 -1 154 -1 155 -1 705 -1 701 -1" | Fish data for autumn |
7 | "708 -1 130 -1 131 -1 146 -1 147 -1 150 -1 151 -1 152 -1 154 -1 705 -1" | Fish data for winter |
8 | "384 .08 589 .09 102 .15 390 .25 330 1" | Artifact data. (Article data TBA): Artifacts should be added in increasing likelihood, and in format: ID chance ID chance, with chance being addressed in 0 to 1. |
Note that not all fields are required: If you have no fish, you can just put -1 for the relevant fields, and if you have no forage, you can just put -1 for the relevant fields.
Examples are:
"Farm": "-1/-1/-1/-1/-1/-1/-1/-1/382 .05 770 .1 390 .25 330 1",
This has no forage or fishing data (handled programmatically) so it's just -1.
In order to have artifacts work, custom locations need to add their data to this file, which can be done with mods such as Content Patcher.