Send the Right Raven
Ravenbreath is still being built, tested, revised, expanded, and occasionally rescued from its own machinery. If something breaks, looks wrong, locks you out, confuses you, or raises a concern, this page points the right raven in the right direction.
Support is handled through request types rather than public email links. Choose the path that best matches the problem, include useful details, and the message can be routed where it belongs without leaving addresses sitting in the open for every spam goblin with a net.
- General Help
- Useful Details
- Clear Reports
Contact Support
For general help, account confusion, broken pages, missing images, strange behavior, or anything that does not clearly belong somewhere else, send a general support request.
The best support messages include what happened, what page or feature was involved, what device or browser was used, and what you expected to happen instead. Screenshots are helpful when something looks wrong, because “the thing is doing the thing” is emotionally valid but technically cursed.
Support cannot promise instant replies, but clear reports make problems easier to find, reproduce, and fix. If the road vanished, say where you were walking. If the lantern exploded, mention which lantern.
The best support messages include what happened, what page or feature was involved, what device or browser was used, and what you expected to happen instead. Screenshots are helpful when something looks wrong, because “the thing is doing the thing” is emotionally valid but technically cursed.
Support cannot promise instant replies, but clear reports make problems easier to find, reproduce, and fix. If the road vanished, say where you were walking. If the lantern exploded, mention which lantern.
- Login Help
- Two-Factor Issues
- Account Recovery
Account and Access Help
If an account is acting cursed, send an account support request. This includes login problems, two-factor authentication issues, missing confirmation messages, account recovery questions, saved preference problems, or access that suddenly stops behaving like it was raised properly.
Include the email address associated with the account if the form asks for it, but do not send passwords, authentication codes, backup codes, or other secrets. Support should never need the kind of information that lets someone else walk through the door wearing your face.
Account help may require confirming ownership, checking logs, or making sure a security feature is working as intended. Some fixes are quick. Some require poking the machinery carefully so the wrong gear does not bite.
Include the email address associated with the account if the form asks for it, but do not send passwords, authentication codes, backup codes, or other secrets. Support should never need the kind of information that lets someone else walk through the door wearing your face.
Account help may require confirming ownership, checking logs, or making sure a security feature is working as intended. Some fixes are quick. Some require poking the machinery carefully so the wrong gear does not bite.
- Broken Links
- Missing Images
- Display Bugs
Broken Roads and Bad Doors
Ravenbreath is a growing archive, which means some paths may occasionally break, vanish, point to the wrong shadow, or lead somewhere that clearly has not swept in a while. Broken links, missing images, layout problems, failed searches, strange redirects, and unexpected errors can be reported through a site issue request.
When reporting a site issue, include the page address, what you clicked, what went wrong, and whether the problem happens more than once. If the issue appears on a specific device or browser, include that too. The more specific the report, the easier it is to track the footprints.
Some problems may be fixed quickly. Others may wait for a larger update, especially if they involve layout, image replacement, account systems, search behavior, or deeper code. Either way, reports help keep the archive from turning into a haunted maze with opinions.
When reporting a site issue, include the page address, what you clicked, what went wrong, and whether the problem happens more than once. If the issue appears on a specific device or browser, include that too. The more specific the report, the easier it is to track the footprints.
Some problems may be fixed quickly. Others may wait for a larger update, especially if they involve layout, image replacement, account systems, search behavior, or deeper code. Either way, reports help keep the archive from turning into a haunted maze with opinions.
- Legal Questions
- Rights Concerns
- Content Issues
Legal and Content Concerns
For legal concerns, rights questions, ownership issues, copyright concerns, takedown requests, content disputes, or questions about Ravenbreath’s terms, send a legal support request.
Useful legal or rights messages should explain the concern clearly, identify the specific page or material involved, describe the claimed issue, and include enough contact information for follow-up. Vague warnings from the fog are atmospheric, but they are difficult to resolve.
Lore corrections, typos, continuity issues, broken canon, or “this page says something weird” can usually go through general support instead. If the concern is about rights, ownership, permissions, or legal use of content, use the legal request path so it lands in the correct pile of ominous paperwork.
Useful legal or rights messages should explain the concern clearly, identify the specific page or material involved, describe the claimed issue, and include enough contact information for follow-up. Vague warnings from the fog are atmospheric, but they are difficult to resolve.
Lore corrections, typos, continuity issues, broken canon, or “this page says something weird” can usually go through general support instead. If the concern is about rights, ownership, permissions, or legal use of content, use the legal request path so it lands in the correct pile of ominous paperwork.
- Privacy Questions
- Request Routing
- Response Timing
Privacy Questions and Replies
For privacy questions, account data questions, cookie concerns, personal information requests, or anything related to how Ravenbreath handles visitor information, send a privacy support request.
Support is not currently a live service, and reply times may vary depending on the issue, workload, and whether the machinery is behaving that day. Ravenbreath is still growing, so some answers may require investigation, code review, database checks, or updates to the site itself.
Please send one clear request through the most relevant path when possible. Repeated messages, scattered reports, or twelve ravens carrying the same note may slow things down rather than speed them up. The lantern is lit. Send the right raven, include useful details, and give it a little time to find the tower.
Support is not currently a live service, and reply times may vary depending on the issue, workload, and whether the machinery is behaving that day. Ravenbreath is still growing, so some answers may require investigation, code review, database checks, or updates to the site itself.
Please send one clear request through the most relevant path when possible. Repeated messages, scattered reports, or twelve ravens carrying the same note may slow things down rather than speed them up. The lantern is lit. Send the right raven, include useful details, and give it a little time to find the tower.
- False Positives
- VPN or Shared IP
- Access Disputes
Blocked Network Access
If you are seeing a 403 error or being turned away at the door, your network address may have been flagged due to suspicious automated activity originating from that IP. The archive monitors access patterns and blocks addresses associated with scanning, probing, or repeated bad-faith requests. The machinery is not perfect, and it does not care about your intentions — it flags patterns.
Not everyone behind a flagged address caused the problem. VPNs, shared hosting environments, office networks, university systems, and cloud exit nodes can carry a history that has nothing to do with the person trying to read about a faction or check a rumor. If your address was caught in someone else's nets, that is a correctable situation.
To request a network access review, include your current IP address if you know it — it may be visible at a tool like whatismyip.com — the approximate date and time you first noticed the issue, and any context that might explain why the flag is a false positive. Disputes are reviewed manually. There is no automatic unblock system, and not every dispute will result in removal, but false positives are taken seriously.
Not everyone behind a flagged address caused the problem. VPNs, shared hosting environments, office networks, university systems, and cloud exit nodes can carry a history that has nothing to do with the person trying to read about a faction or check a rumor. If your address was caught in someone else's nets, that is a correctable situation.
To request a network access review, include your current IP address if you know it — it may be visible at a tool like whatismyip.com — the approximate date and time you first noticed the issue, and any context that might explain why the flag is a false positive. Disputes are reviewed manually. There is no automatic unblock system, and not every dispute will result in removal, but false positives are taken seriously.