added wiki link + updated some wiki pages
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
Never directly edit the system compendiums.
|
||||
They will be erased anytime you update the system.
|
||||
|
||||
The better options to keep the links between items and properties for exemple, is to fill a custom compendium using babel.
|
||||
The better options to keep the links between items and properties for example, is to fill a custom compendium using babel.
|
||||
This way, the system compendiums will be overridden by this module.
|
||||
|
||||
You will need to manually download the following module, and edit json files.
|
||||
|
||||
@@ -6,14 +6,14 @@ These fields have special constraints, you will find theirs rules below.
|
||||
## Difficulty
|
||||
Can be :
|
||||
- A integer number : `1` to `9`.
|
||||
- Or specific syntaxe "@`S`:`prop1`" or "@`T`:`prop1`|`max`" or "@`T`:`prop1`|`max`(`prop2`)" :
|
||||
- Or specific syntax "@`S`:`prop1`" or "@`T`:`prop1`|`max`" or "@`T`:`prop1`|`max`(`prop2`)" :
|
||||
- `@` fixed, trigger the parser
|
||||
- `T` or `S` : `T`arget or `S`elf, define the actor to get the value.
|
||||
- `prop1` / `prop2` : Can be any property in `actor` or `actor.system`. Limitations: currently no `size`, `distance` (range) or computation (a+b).
|
||||
- `|` separator, optional if no min/max.
|
||||
- `min` or `max` : Between the selected targets, search for the min/max of `prop2`. If no `prop2` provided, take `prop1` as `prop2` (irrelevant for `@S`).
|
||||
- `(prop2)` : define the property for the actor selection in multiple target, can be omitted if same as `prop1`.
|
||||
- Exemples :
|
||||
- Examples :
|
||||
- `@S:vigilance` : Difficulty will be my own `vigilance`.
|
||||
- `@T:vigilance|min` : Difficulty will be the `vigilance` from the target with the minimum vigilance (implicit) value. it's the same to wrote `@T:vigilance|min(vigilance)`.
|
||||
- `@T:vigilance|max(statusRank)` : Difficulty will be the `vigilance` from the target with the maximum `statusRank` value.
|
||||
@@ -24,7 +24,7 @@ Can be :
|
||||
- Any `Skill` id : `melee`, `fitness`...
|
||||
- Any `SkillCategory` id : `scholar`, `martial`...
|
||||
- Or both in list, coma separated.
|
||||
- Exemples :
|
||||
- Examples :
|
||||
- `theology`
|
||||
- `melee,ranged,unarmed`
|
||||
- `martial,fitness,performance`
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Updating - Bests practices
|
||||
|
||||
- Anytime you update to a major version make a backup of foundry's data directory (default : `%localappdata%/FoundryVTT/data/`).
|
||||
- Take time to upgrading to a major version (ex FoundryVTT v9->v10).<br>A lot of bugs can be on firsts patchs, and a lots of systems/modules won't upgrade fast and will be incompatible or not tested (a lot of us do it only on our free time).<br>If you need some timing windows: let à least 2 weeks to 1 month.
|
||||
- Take time to upgrading to a major version (ex FoundryVTT v9->v10).<br>A lot of bugs can be on firsts patchs, and a lots of systems/modules won't upgrade fast and will be incompatible or not tested (a lot of us do it only on our free time).<br>If you need some timing windows: let at least 2 weeks to 1 month.
|
||||
|
||||
Reference in New Issue
Block a user