honse-sim 0.2.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/uma_sim_wasm.d.ts +11 -6
- package/uma_sim_wasm.js +11 -6
- package/uma_sim_wasm_bg.wasm +0 -0
package/package.json
CHANGED
package/uma_sim_wasm.d.ts
CHANGED
|
@@ -116,12 +116,17 @@ export function skillActivationPercent(base_wit: number): number;
|
|
|
116
116
|
* effects and whether the skill is left inert; a fully modeled skill is omitted,
|
|
117
117
|
* so an empty array means full coverage.
|
|
118
118
|
*
|
|
119
|
-
* The engine drops effects it cannot model rather than rejecting the skill
|
|
120
|
-
* unmapped effect `type
|
|
121
|
-
*
|
|
122
|
-
*
|
|
123
|
-
*
|
|
124
|
-
*
|
|
119
|
+
* The engine drops effects it cannot model rather than rejecting the skill —
|
|
120
|
+
* an unmapped effect `type` (what it does), `valueUsage` (how much), or `target`
|
|
121
|
+
* (who receives it), or a tiered usage that did not state the
|
|
122
|
+
* `preAppliedMultiplier` already folded into its modifier — so a simulation
|
|
123
|
+
* always runs, but a dropped effect makes that skill's contribution understated.
|
|
124
|
+
* Exposed so a consumer can say which skills are affected instead of presenting
|
|
125
|
+
* partial results as complete.
|
|
126
|
+
*
|
|
127
|
+
* The answer is a property of the skill data alone, so call it once per skill
|
|
128
|
+
* pool rather than per simulation. It accepts a whole pool: no unmapped code in
|
|
129
|
+
* any submitted skill can make this throw.
|
|
125
130
|
*/
|
|
126
131
|
export function skillSupportReport(skills: any): any;
|
|
127
132
|
|
package/uma_sim_wasm.js
CHANGED
|
@@ -214,12 +214,17 @@ export function skillActivationPercent(base_wit) {
|
|
|
214
214
|
* effects and whether the skill is left inert; a fully modeled skill is omitted,
|
|
215
215
|
* so an empty array means full coverage.
|
|
216
216
|
*
|
|
217
|
-
* The engine drops effects it cannot model rather than rejecting the skill
|
|
218
|
-
* unmapped effect `type
|
|
219
|
-
*
|
|
220
|
-
*
|
|
221
|
-
*
|
|
222
|
-
*
|
|
217
|
+
* The engine drops effects it cannot model rather than rejecting the skill —
|
|
218
|
+
* an unmapped effect `type` (what it does), `valueUsage` (how much), or `target`
|
|
219
|
+
* (who receives it), or a tiered usage that did not state the
|
|
220
|
+
* `preAppliedMultiplier` already folded into its modifier — so a simulation
|
|
221
|
+
* always runs, but a dropped effect makes that skill's contribution understated.
|
|
222
|
+
* Exposed so a consumer can say which skills are affected instead of presenting
|
|
223
|
+
* partial results as complete.
|
|
224
|
+
*
|
|
225
|
+
* The answer is a property of the skill data alone, so call it once per skill
|
|
226
|
+
* pool rather than per simulation. It accepts a whole pool: no unmapped code in
|
|
227
|
+
* any submitted skill can make this throw.
|
|
223
228
|
* @param {any} skills
|
|
224
229
|
* @returns {any}
|
|
225
230
|
*/
|
package/uma_sim_wasm_bg.wasm
CHANGED
|
Binary file
|