You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+75-3Lines changed: 75 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,13 +80,58 @@ In general ModVerify has two operation mods.
80
80
1.`verify` Verifying a game or mod
81
81
2.`createBaseline` Creating a baseline for a game or mod, that can be used for further verifications in order to verify you did not add more errors to your mods.
82
82
83
-
### Example
84
-
This is an example run configuration that analyzes a specific mod, uses a the FoC basline and writes the output into a dedicated directory:
83
+
### Examples
85
84
86
-
```bash
85
+
#### Example 1: Auto-detection with a custom baseline
86
+
Analyzes a specific mod, uses the FoC baseline and writes the output into a dedicated directory:
#### Example 3: Layering a mod-specific baseline on top of the default baseline
120
+
A typical mod-dev workflow: filter the base game's known findings with the embedded default baseline, *and* filter your mod's own accepted findings with your own baseline. The two baselines stay independent — you can regenerate your mod baseline without touching the default.
### Creating a mod baseline on top of a base baseline
177
+
178
+
If you maintain a mod and only want your baseline to contain findings your mod is responsible for, supply the base baselines you want to subtract out. Findings already covered by the base baselines are excluded from the new file. The base baselines themselves are not modified, so they can keep being maintained independently.
0 commit comments