Skip to content

Expose when a guild member's stored equipment reached us - #12

Open
uga wants to merge 1 commit into
Thaoky:developmentfrom
uga:fix/guild-equipment-timestamp
Open

Expose when a guild member's stored equipment reached us#12
uga wants to merge 1 commit into
Thaoky:developmentfrom
uga:fix/guild-equipment-timestamp

Conversation

@uga

@uga uga commented Aug 4, 2026

Copy link
Copy Markdown

Independent of #11 — different file, no overlap.

MSG_EQUIPMENT_TRANSFER writes lastUpdate next to the inventory it
stores, and has done since the guild comm was written. Nothing has ever
read it.

That matters more here than elsewhere in DataStore, because this data does
not refresh on its own. It arrives only when the member, or their main, is
online and answers a request. A copy received months ago sits in the table
unchanged and is handed out exactly like one received a second ago, and a
consumer showing it has no way to tell the two apart.

This adds a reader, registered next to GetGuildMemberInventoryItem.

Our own characters return nothing, deliberately: those are answered from
our own tables, which are written as we play, so there is no timestamp to
give and none is wanted.

Used by Thaoky/Altoholic_Cata#29, where the guild equipment panel now shows
the date under the character's name — and says so when it is waiting for an
answer that may never come.

🤖 Generated with Claude Code

MSG_EQUIPMENT_TRANSFER writes lastUpdate next to the inventory it stores,
and has done since the guild comm was written. Nothing has ever read it.

That matters more here than anywhere else in DataStore. This data does not
refresh on its own: it arrives only when the member, or their main, is
online and answers a request, so a copy received months ago sits in the
table unchanged and is handed out exactly like one received a second ago.
A consumer showing it has no way to tell the two apart, and no way to warn
anyone.

Adds a reader for it, registered next to GetGuildMemberInventoryItem. Our
own characters return nothing, deliberately: they are answered from our own
tables, which are written as we play, so there is no timestamp to give.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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