Automation backlog: non-defensive and healing spells #104
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Athemis/ds4#104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Use the existing consume-effect primitives (
heal,damage,activeEffect) to automate a focused subset of spells, starting with non-defensive healing/buff spells.Assumption for this backlog: spell automation triggers after a successful spell check.
Quick wins (single-target / low ambiguity):
heal= spell result to selected target.heal= spell result to selected target.activeEffect(Abwehr bonus from spell result, fixed duration).activeEffect(+Abwehr until next round).activeEffect(movement boost for duration).Requires small extensions:
Out of scope for this track (for now):
Context
Current engine reference:
src/apps/actor/consume-flow.js.This list is intentionally pragmatic and not exhaustive. Priority recommendation: healing + simple combat buffs first.
Update: groundwork from phase 1 is now available in PR #107.
What is now in place:
ActionEffectServiceruntime contractWhat is not included yet:
This gives us the technical base to implement the quick-win spell items in follow-up commits/PRs with lower risk.