Testing

The Rift — Alpha Tester Guide

Thanks for helping test this. The Rift is Veiled Dominion's Bluesky account — it's meant to feel like a narrator watching over the games, not a corporate feed. This alpha adds three things it can now do:

1. Post about your matches (anonymized by default — no handles, just "Rebirth lost control after 34 moves" style lines)
2. Post short lore drops ("Rift Reports") on a regular schedule
3. Cross-promote other Loptr Lab projects (Violet's Revenge, Mortis on Pulsr) from the same account

What to actually test

• Play a full match to completion on duet.loptrlab.com (remote/multiplayer mode) and check that a result post shows up on the-rift's Bluesky within a minute or two of the game ending.
• Check the tone — does the post read like something from this world, or like a generic "game over" notification? Flag anything that feels off.
• Check your privacy — you should never see your own handle or identity in a match post unless you specifically opted in somewhere. If you ever see identifying info you didn't expect, report it immediately — that's a bug, not a feature.
• Watch for duplicate or missing posts — one match should produce one post, not zero and not five.

What's not in scope for this alpha

• Nothing here touches your rpg.actor character stats — this system only posts public announcements, it doesn't read or write your saved game data.
• Fog Mode matches aren't covered yet — only base-ruleset remote matches.
• No AI opponent matches are posted (only real remote matches between two people).

How to give feedback

• If a post is wrong, missing, or feels off-brand, screenshot it and note the approximate time and what happened in the match.
• If you find a privacy issue (your identity showing up when it shouldn't), flag it as urgent — this is the one thing we want zero tolerance on during alpha.
• General "this content style works / doesn't work for me" feedback is welcome too — the Rift Report voice is still being tuned.

Where to send feedback

• Open a Discussion on this repo — no GitHub account required to read, but you'll need one to post. Use the Feedback category.
• If you found a privacy issue (your identity showing up when it shouldn't), open an Issue instead and label it bug — that gets eyes on it faster.