Skip to content

Conversation

@CarlosFdez
Copy link
Collaborator

@CarlosFdez CarlosFdez commented May 13, 2025

Mostly an API bug fix right now, this allows message.item to resolve for unarmed attack damage (currently it is only supported for real items). There are also type fixes.

Should we rename ChatMessagePF2e's _strike getter to just strike? It needs to be public, and I doubt strike retrieval will change soon.

stwlam and others added 30 commits May 9, 2025 03:03
@CarlosFdez CarlosFdez changed the title Fix message item retrieval for damage from synthetic items Support message item retrieval for damage from synthetic items May 13, 2025
@CarlosFdez CarlosFdez changed the title Support message item retrieval for damage from synthetic items Support message item retrieval for damage from synthetic strikes May 13, 2025
@stwlam
Copy link
Collaborator

stwlam commented May 13, 2025

Public is fine, but it needs to be understood as non-contractual. Maybe mark it @internal? Or just warn Idle.

@CarlosFdez
Copy link
Collaborator Author

I'll keep it as _strike then, since that can be used to understand it as non-contractual, but I added @internal. There's nothing really wrong persay with the strike getter, but more that strikes haven't jumped to the statistic api yet.

@CarlosFdez CarlosFdez force-pushed the strike-retrieval-damage branch from 769bc34 to 92b7cdc Compare May 13, 2025 06:14
@CarlosFdez CarlosFdez marked this pull request as draft May 13, 2025 19:54
@CarlosFdez CarlosFdez force-pushed the v13-dev branch 2 times, most recently from 33779b2 to 6c3556e Compare May 21, 2025 00:44
@CarlosFdez CarlosFdez force-pushed the v13-dev branch 2 times, most recently from 69ee8a9 to 504abfc Compare May 27, 2025 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants