Luck of the Dwarves - Vault Ledger

LuckyFriend · 2026-01-03 23:48:25

Luck of the Dwarves — Vault Ledger (Alt1 Plugin)

Luck of the Dwarves — Vault Ledger is a community-built Alt1 plugin for RuneScape 3 that
passively watches your on-screen game chat using OCR and records specific, loot-related chat messages
associated with Luck of the Dwarves (LoTD) and Hazelmere’s Signet Ring (HSR).

It’s designed for transparent, community-verifiable logging of these rare ring-triggered loot events,
with optional cropped screenshot evidence when capture is available.

What is this plugin?

This plugin runs inside Alt1 and continuously reads new lines in your currently visible chatbox.
When it detects a supported LoTD/HSR-related loot line, it automatically:

Identifies the relevant loot/proc line from the chat stream
Extracts the item name (and quantity when present)
Optionally captures a cropped image of the chatline area as evidence
Submits the event to a public, append-only ledger

No clicking, no keypresses, no gameplay interaction. It only reads pixels and logs matching lines.

Why does this exist?

LoTD and HSR events are rare, easily missed, and often argued from screenshots or memory.
Vault Ledger exists to create a shared record that is:

Automatic (no manual forms)
Consistent (same parsing rules across everyone)
Resistant to spam (duplicate protection)
Community-visible (public stats + recent entries)

The goal is simple: turn “trust me bro” into verifiable receipts.

Core Features

Passive OCR reading of the RuneScape chatbox via Alt1
Detection of supported LoTD / HSR-related loot lines
Parses item name and quantity when available
Optional cropped evidence image capture (chatline region)
Duplicate protection to prevent repeated submits of the same event
Public-facing stats: recent drops, uniques, and trends (site-side)

How it works (Alt1-side)

You open the plugin in Alt1 while RS3 is running
The plugin locates one or more visible chatboxes
It continuously reads new chat lines using OCR
When a supported line is found, it extracts the relevant fields
If enabled and possible, it grabs a cropped screenshot as evidence
It submits the event to the public ledger

If the same event is seen again (re-read lines, redraws, UI jitter), duplicate protection prevents it from being counted repeatedly.

Requirements

RuneScape 3 (desktop client)
Alt1 Toolkit
At least one chatbox visible and readable on screen
Loot/proc messages visible in the active chat tab you’re reading

Recommended Settings

For best OCR accuracy:

Keep the chatbox visible and unobstructed
Avoid extreme transparency and heavy background blur
Use a standard or high-contrast UI theme
Avoid constant resizing/moving while the plugin is running
Make sure the tab you’re watching actually shows the relevant loot lines

What gets logged?

Each ledger entry may include:

Timestamp
Item name
Quantity (when present in the line)
Ring source label (LoTD or HSR when determinable)
Raw OCR text (for audit/verification)
Cropped evidence image (when capture succeeds)

RSN submission is optional.

Privacy Notes

The plugin does not upload your full chat history
Only supported loot/proc-related lines are processed for submission
Evidence images are cropped to the chatline region (not your whole screen)
No botting, no macros, no automated input: it does not control RuneScape

Troubleshooting

Plugin stuck on “Initializing”

Open it inside Alt1 (not a normal browser tab)
Confirm RuneScape is running and visible
Ensure the chatbox is on-screen and readable

Event not detected

Confirm the loot/proc message appears in the chat tab being read
Check chat filters (don’t hide game/loot messages)
Increase UI contrast and reduce transparency
Don’t cover the chatbox with other windows/overlays

Evidence image missing

The event can still log without an image
Evidence capture depends on stable chatbox geometry and readable pixels

What this plugin is NOT

Not a bot or input automation tool
Not a macro/script that plays the game
Not a drop-rate predictor or RNG calculator
Not a RuneMetrics replacement

It is a passive OCR-based logging tool for specific chat messages only.

Installation

Open this link inside Alt1:
alt1://addapp/https://luckofthedwarves. … onfig.json

Or visit:
https://luckofthedwarves.com
and click Open in Alt1.

Project Philosophy

Append-only
Evidence-friendly
Community-verifiable
Transparent by design

If it can’t be proven, it doesn’t belong in the ledger.

Feedback, bug reports, and suggestions are welcome.
This is a community-driven Alt1 plugin built for transparency and trust.

Last edited by LuckyFriend (2026-01-14 16:21:32)

badboy4eva · 2026-01-13 04:58:25

Hi are you able to add selecting which chatbox to detect? I have 2 that just has game messages and broadcasts seperate from player chats

LuckyFriend · 2026-01-13 16:53:40

badboy4eva wrote:

Hi are you able to add selecting which chatbox to detect? I have 2 that just has game messages and broadcasts seperate from player chats

Yep, totally get the use-case.

Right now, due to how Alt1 reads/detects chat areas, “select chatbox #1/#2” isn’t reliably something we can toggle like a normal setting in all layouts.

Best workaround:

On app initialization, cover the chatbox(es) you do NOT want read (drag another window over them, resize them, etc.).
Keep the one you do want detected visible and unobstructed.
If possible, place the chatbox you want detected above the others in your UI layout, as Alt1 tends to latch onto the first valid match it finds.

Last edited by LuckyFriend (2026-01-13 16:55:14)

Ex Inferi · 2026-01-13 21:15:03

LuckyFriend wrote:

Right now, due to how Alt1 reads/detects chat areas, “select chatbox #1/#2” isn’t reliably something we can toggle like a normal setting in all layouts.
Best workaround:
On app initialization, cover the chatbox(es) you do NOT want read (drag another window over them, resize them, etc.).
Keep the one you do want detected visible and unobstructed.
If possible, place the chatbox you want detected above the others in your UI layout, as Alt1 tends to latch onto the first valid match it finds.

Respectfully, I disagree. If your app can detect one chatbox, it should be able to detect all of them. I don't see a GitHub link, so I assume your app isn't open source. But I've written a TS example in the past of how the chatbox detection works that you can take a look at here.

LuckyFriend · 2026-01-14 15:52:32

Ex Inferi wrote:

LuckyFriend wrote:
Right now, due to how Alt1 reads/detects chat areas, “select chatbox #1/#2” isn’t reliably something we can toggle like a normal setting in all layouts.
Best workaround:
On app initialization, cover the chatbox(es) you do NOT want read (drag another window over them, resize them, etc.).
Keep the one you do want detected visible and unobstructed.
If possible, place the chatbox you want detected above the others in your UI layout, as Alt1 tends to latch onto the first valid match it finds.
Respectfully, I disagree. If your app can detect one chatbox, it should be able to detect all of them. I don't see a GitHub link, so I assume your app isn't open source. But I've written a TS example in the past of how the chatbox detection works that you can take a look at here.

Thanks for the correction, and sorry about my earlier reply. I’d assumed reliable chatbox selection wasn’t something we could expose cleanly across layouts, but it turns out there is a working approach for proper chatbox targeting. Appreciate you sharing the code and setting the record straight, that’s super helpful. I’ll update my guidance/docs for the correct solution going forward.

LuckyFriend · 2026-01-14 16:14:09

Luck of the Dwarves (Alt1 App)

Update Log
Upgrade: 2026.01.3.8 → 2026.01.14.4b

Highlights

✅ Multi-Chatbox Support (Selector UI Added)

Added a chatbox selector row so the app can handle multiple detected chatboxes instead of assuming “the only one.”
Selector is button-based (not a dropdown) and is populated automatically when chatboxes are found.
Includes a Re-scan button to re-detect chatboxes without needing to fully reinstall or manually reset anything.

✅ “Selected Chatbox” Persistence

Your chosen chatbox is now remembered and reused automatically (so you don’t have to re-pick it every launch)./*]
Session reload/restore behavior now keeps your chatbox selection instead of wiping it during cleanup.

✅ Better Chatbox Detection Reliability

Chatbox discovery was updated to be more stable:
Uses a fresh captured frame for scanning (improves detection consistency).
Avoids accidental timer stacking or repeated “start loops” while searching.
Cleansly restarts detection when you hit Re-scan.

✅ Visual Feedback for Selection

When a chatbox is selected, the app can optionally highlight the chosen chatbox region (safe “no-op” behavior if overlay features aren’t available).

UI / Layout Changes

Header area updated

The header now has a dedicated area for:
Active username badge
Status indicator
App version badge
Chatbox selector row (buttons + hint text + rescan)

Helpful “no chatbox found” hint

If the selector has no options, a hint appears telling the user what to do (open RS3 and reload so scanning can occur).

User Notes

If you run multiple chatboxes (or RS UI variants), you may see multiple chatbox buttons. Pick the one that corresponds to the chatbox where the loot/proc messages appear.
If it looks wrong, hit Re-scan and select again.

Last edited by LuckyFriend (2026-01-14 16:18:18)

LuckyFriend · 2026-01-17 17:57:56

Luck of the Dwarves — Vault Ledger (Alt1 Plugin) Update

Version: v2026.01.14.4b → v2026.01.17.2

Summary
This update fixes proc messages that wrap across multiple chat lines (some UI scales/font settings only show part of the LoTD/HSR message on the first line). The logger now stitches the proc line together safely before parsing, so item names are logged correctly.

✅ Fixes & Improvements

Fixed wrapped proc message truncation
- If a proc message splits across lines (example: "You receive: 1 x Sealed clue" + "scroll (elite)."), the logger now stitches the lines together before parsing.
Added 3-line safety stitching (A + B + C)
- The logger now reads the detected proc line plus the next two visual lines below it, just in case the message wraps twice.
Lowercase continuation detection
- If the line after the proc begins with a lowercase letter, it is treated as a continuation and appended (typical wrap behavior like "scroll (elite).").
Wrap-after-quantity recovery (capital continuation)
- If the proc line ends at "You receive:" or "You receive: 1 x" (wrap happens before the item name), the next line is appended even if it starts with a capital letter.
Fallback retry when OCR produces a bogus item
- If the parsed item looks invalid (example: "1 x"), the logger automatically retries parsing using stitched lines to recover the real item name.
Correct “next line” selection using visual order
- Instead of relying on read order, lines are now sorted by their on-screen position (rect.y then rect.x) so the “next line” is the one actually rendered beneath the proc.
Added local dedupe window to prevent double-logging
- A short signature-based dedupe window prevents the same proc being logged multiple times across successive reads.
Better evidence capture for stitched messages
- When multiple lines are stitched, the screenshot rectangle now merges the involved line rects so evidence includes the full proc message.

Examples now handled correctly

Two-line wrap (lowercase continuation)
- Line A: "… You receive: 1 x Sealed clue"
- Line B: "scroll (elite)."
- Logged as: "1 x Sealed clue scroll (elite)."
Wrap after quantity (capital continuation)
- Line A: "… You receive: 1 x"
- Line B: "Saradomin's whisper."
- Logged as: "1 x Saradomin's whisper."
Three-line wrap safety
- Proc line + 2 continuation lines are stitched when needed, preventing partial item names.

Notes

No user action required besides updating.
If you encounter a proc that still logs oddly, post a screenshot of the chatbox lines so we can tighten heuristics further.

LuckyFriend · 2026-01-17 18:28:00

Luck of the Dwarves — Vault Ledger Update

Version: v2026.01.17.2 → v2026.01.17.03

Summary
This update changes how auto-updates refresh the app. When a new version is detected, the app now performs a true full-page refresh (same as pressing the browser refresh button), while still preserving your current session settings.

Changes

True refresh on version change
When version.json changes, the app now saves your session and triggers a full page reload (location.reload) so updated JS/CSS reliably apply.
Session retained across refresh
Your current RSN (if set) and selected chatbox index are preserved across the reload using the existing reload-session handoff.
Cache-bust retained
The refresh still updates the URL with _v and _r parameters before reloading to avoid stale cached assets.

Files updated

script.js
version.json

Notes

No user action required other than updating files.
If you were in an active session, it will restore automatically after the refresh.

LuckyFriend · 2026-01-17 19:15:12

Luck of the Dwarves — Vault Ledger Update

v2026.01.17.03 → v2026.01.17.04

Summary
Ease-of-access update: added an optional “Remember username” checkbox on the intro screen so users can save their RuneScape Name locally and skip re-entering it on future launches.

Changes

Remember Username (opt-in)
Adds a checkbox on the username entry screen to store your RSN on this device.
Auto-fill on launch
If enabled and a username is saved, the RSN field will be pre-populated next time you open the app.
Privacy-friendly
If unchecked, the app will not store the username. If previously saved, the stored value is removed.
Update-safe
Saved username preference is retained across version-update reloads so users don’t have to re-configure after updates.

Notes

This update is an addition only (no fixes or behavior changes to proc detection/logging).
Username saving uses local storage on your device (not shared publicly).

RuneApps forums

#1 2026-01-03 23:48:25