eamuse: include card update time in inquiries - #19
Conversation
|
lol, that's so weird |
2f45693 to
c5955bb
Compare
|
Sorry for AI slop, I didn't realize that this was intended only as a quick local fix. Searching the game's DLLs did not reveal enough evidence to determine the exact semantics of lastupdate. The field is required in a bound-card cardmng.inquire response because the protocol layer parses it, but the parsed value is never consumed by the game code. The game later sends another inquiry with update=1, so I cannot conclude that the field is never updated. Using Date.now() is clearly not appropriate. Reusing updatedAt may not be semantically exact either, but it is a minimal persistent fallback that works for this title because the returned value is not actually used. |
c5955bb to
15fecca
Compare
Return the lastupdate attribute required by clients such as DANCE aROUND using the card record's persisted NeDB updatedAt timestamp. Co-authored-by: Codex <codex@openai.com>
15fecca to
403bd38
Compare
|
as it stands currently it doesn't hurt to just have an extra field afaik. |
Return a positive Unix timestamp from cardmng.inquire. DANCE aROUND treats a registered card response without this field as a temporarily busy reader.