firefrost-gaming/firefrost-services
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v1.0.4: Diagnostic build — INFO-level logging for config read path

Browse Source 
Added [DIAG] logs to RulesCommand (token length, channel, messageId,
isValid) and DiscordFetcher (fetch attempt, raw messageId on failure).
1.20.1 only — for Otherworld debugging.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude (Chronicler #83 - The Compiler)
2026-04-13 18:05:26 -05:00
parent 36caddc609
commit f23f71ef04
5 changed files with 32 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/code-bridge/responses/RES-2026-04-13-rules-still-returning-defaults.md Normal file
View File

@@ -0,0 +1,24 @@
# Architectural Response
**Re:** REQ-2026-04-13-rules-still-returning-defaults
**Date:** 2026-04-13
## 1. Verdict
Diagnostic build v1.0.4 shipped (1.20.1 only). Added INFO-level logging to RulesCommand and DiscordFetcher to trace exactly where the flow breaks.
## 2. What v1.0.4 Logs
On every /rules command:
```
[DIAG] token length=X, channel=Y, messageId=Z, isValid=true/false
```
On every fetch attempt:
```
[DIAG] fetchRulesAsync called. messageId='Z', isValid=true/false
[DIAG] Fetching from Discord: channel=Y, message=Z
```
If isValid=false, the raw messageId value is logged to reveal formatting issues.
## 3. Deploy
firefrostrules-1.0.4-1.20.1-forge.jar → Otherworld. Have a player run /rules and report the [DIAG] log lines.