1
0
Fork 0
mirror of https://github.com/Acamaeda/The-Modding-Tree.git synced 2024-11-21 16:13:55 +00:00
The-Modding-Tree/docs/milestones.md

37 lines
1.5 KiB
Markdown
Raw Normal View History

#Milestones
Milestones should be formatted like this:
```js
2020-10-01 05:43:30 +00:00
milestones: {
0: {
2020-10-03 19:45:47 +00:00
requirementDesc:() => "123 waffles",
2020-10-01 05:43:30 +00:00
}
etc
2020-10-01 05:41:25 +00:00
}
```
You can use hasMilestone(layer, id) to determine if the player has a given milestone
Milestone features:
- requirementDesc: A string describing the requirement for unlocking this milestone. Suggestion: Use a "total".
2020-10-03 19:45:47 +00:00
It can also be a function that returns updating text.
- effectDesc: A string describing the reward for having the milestone. *You will have to implement the reward elsewhere.*
2020-10-03 19:45:47 +00:00
It can also be a function that returns updating text.
- done(): A function returning a boolean to determine if the milestone has been fulfilled.
- toggles: *optional*, Creates toggle buttons that appear on the milestone when it is unlocked.
The toggles can toggle a given boolean value in a layer.
It is defined as an array of paired items, one pair per toggle. The first is the internal name of the layer
the value being toggled is stored in, and the second is the internal name of the variable to toggle.
2020-10-03 19:45:47 +00:00
(e.g. [["b", "auto"], ["g", "auto"])
**Tip:** Toggles are not de-set if the milestone becomes locked! In this case, you should also check if the player has the milestone.
2020-10-03 19:45:47 +00:00
- layer: **Assigned automagically**. It's the same value as the name of this layer, so you can do player[this.layer].points or similar
- id: **Assigned automagically**. It's the id for this milestone.