Separate `passive` abilities from others #402

New issue

Closed

opened 2025-10-17 05:57:52 +00:00 by LunarTides · 0 comments

LunarTides commented

2025-10-17 05:57:52 +00:00

(Migrated from github.com)

Use the new ability infrastructure from #400 to separate the passive (owner, self, key, value, eventPlayer) from the others (owner, self).

This makes things less confusing by not including parameters that don't get passed in the non-passive abilities, and only includes them if they are actually used.

Use the new ability infrastructure from #400 to separate the passive `(owner, self, key, value, eventPlayer)` from the others `(owner, self)`. This makes things less confusing by not including parameters that don't get passed in the non-passive abilities, and only includes them if they are actually used.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

LunarTides/Hearthstone.js#402

No description provided.

Rows
Columns

Separate passive abilities from others #402

Separate `passive` abilities from others #402