Skip to content

Add per-member party diagnostics without pasted scripts - #36

Merged
jiberishxd merged 1 commit into
mainfrom
codex/party-frame-diagnostics
Sep 28, 2026
Merged

jiberishxd merged 1 commit into
mainfrom
codex/party-frame-diagnostics

Conversation

@jiberishxd

Copy link
Copy Markdown
Owner

Party borders can report three attached frames but only one visible member, and a pasted diagnostic script may fail before printing anything. Add /jf partydebug (also /jf status party) to report each cached member's unit assignment, attachment, artwork state, and native visibility/opacity reads independently.

The command labels secret, unavailable and failed reads without printing their contents, continues past individual failures, and runs only when requested. Version 0.9.13 makes no rendering, artwork or settings changes; the remaining EllesmereUI border issue still requires the player's diagnostic output.

Validation: 427 offline Lua tests passed, including all three party providers on both client variants, protected values, throwing getters, missing units, and read-only behavior in combat. Python suite passed (26 tests; 4 optional source-art audits skipped). Cast preview matches; all 298 runtime artwork hashes and both 334-file client archives verified. No game access or in-game testing.

@jiberishxd
jiberishxd merged commit 9b533ad into main Sep 28, 2026
1 check passed
@jiberishxd
jiberishxd deleted the codex/party-frame-diagnostics branch September 29, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant