How Raffy handles sources, estimates, and uncertainty.
Raffy is most useful when a player can tell what an answer means, where its boundaries are, and what to check before acting on it.
Read the label before the number
Different kinds of information carry different levels of certainty. Raffy keeps those roles separate in player-facing language.
Observed
A value or event recorded from a named source. It describes what was available at the stated observation time.
Calculated
A result produced from player inputs and a reviewed formula or model. It is only as complete as that model’s stated coverage.
Inferred
A conclusion derived from observed records or explicit rules. It is not presented as a direct announcement.
Predicted
A future-facing estimate. It remains separate from announced dates and should not be read as a guarantee or probability.
Manual correction
A reviewed adjustment applied when a source record needs a documented exception. Corrections are expected to be narrow and checkable.
Unknown
The available material is missing, unclear, or insufficient. Raffy keeps that gap visible instead of filling it with a guess.
Source classes serve different jobs
Acknowledging a source does not make every field equivalent. The page or feature should still explain whether it is showing a record, a model, or a player choice.
Official announcements
Used for announcement text, dates, and campaign windows when Raffy presents an official observation. The original notice remains the place to confirm late changes.
Canonical game data
Items, monsters, maps, and other game records are normalized into stable identities so tools and search can refer to the same thing consistently.
Reviewed calculations
Raffy’s calculators use bounded models with explicit supported inputs. A model may cover one action or condition without claiming to reproduce every game mechanic.
Player-owned information
Roster, loadout, and scenario choices belong to the player. Local or account storage does not turn those choices into reference data.
Source acknowledgements and fan-project attribution live on Sources, Credits & Attribution.
Freshness is a timestamp, not a promise
Raffy checks that published products are internally consistent before release and keeps related files on the same release. That does not guarantee an upstream page, game rule, or live campaign has not changed since the last observation.
Campaign windows retain their stated time zone. Official Toram timing is shown in JST where applicable instead of silently converting the source record.
Incomplete records, unsupported conditions, and invalid inputs should become “Unknown” or “Not available,” not a plausible-looking zero.
Release checks catch missing pieces and mismatched versions before publication. Player-facing pages still explain any important coverage limit.
What Raffy does not claim
These boundaries are part of the answer, not fine print.
- A calculated result does not imply complete simulation of every skill branch, combat state, equipment condition, or live-game interaction.
- A forecast is not an official announcement, a calibrated probability, or a promise that an item will return.
- A source timestamp describes the last checked material; it cannot guarantee a later correction or announcement has not appeared.
- Reference material may contain omissions or mistakes. Raffy can preserve uncertainty while a claim is reviewed.
- Player-entered builds and shared build pages describe a player’s choices. They are not verified game records.
A useful correction is specific.
Send the affected page, the value or wording that looks wrong, what you expected, and the source or in-game evidence you checked. Raffy can then review the smallest responsible change without hiding the earlier uncertainty.