Editorial policy
How Animal Hospital Roblox Wiki checks official facts, gameplay claims, community reports, images, updates, corrections, and safety guidance.
This is an independent fan-made guide and is not affiliated with Roblox, Animal Anomaly, Roytt, or Fandom. It does not provide exploits, scripts, auto-farm, auto-heal, infinite sanity, or instructions that put an account at risk.
Every claim is limited to what its evidence can support. Official platform records establish identity and dates; direct play and complete screenshots support gameplay; community reports supply leads that remain labeled until they can be repeated.
Higher levels can support narrower, stronger claims. A source is not stretched beyond the information it actually shows.
| Level | Examples | What it can support | Limits |
|---|---|---|---|
| 1. Official | Roblox game page, verified developer group, official event listing, Roblox API | Experience name, publisher, creation time, player limit, official links, event title, and event window | An activity timestamp does not prove the contents of a patch or every gameplay mechanic. |
| 2. Direct in-game | Complete screenshots, interface captures, dialogue, item prompts, repeated play | Visible anomaly signs, treatment wording, room interactions, route objects, class text, and reproducible outcomes | One screenshot can prove an object exists without proving every trigger or later result. |
| 3. Community documented | Fandom records, Discord reports, videos, and multiple player notes | Mechanic leads, route order, historical changes, and details awaiting a fresh capture | Claims stay attributed or qualified until direct evidence or repeat reports agree. |
| 4. Theory | Identity guesses, ending interpretations, visual resemblance, and one-off comments | A clearly labeled open question or test plan | Theory is never turned into a patient decision, purchase claim, route guarantee, or confirmed ending. |
| Image type | Current handling | Replacement rule |
|---|---|---|
| Official Roblox thumbnails or event art | Used to identify the experience or official event and described accurately in alt text. | Keep the original source URL in the working record and do not imply site ownership. |
| Community wiki image | Treated as community-sourced material associated with its Fandom record. | Replace with a complete original in-game capture when the same mechanic, item, or character can be reproduced. |
| Original in-game screenshot | Capture the full clue, prompt, room, or interface context whenever possible. | Prefer the clearest current-build image and retain an older capture only when it documents a historical version. |
| Disputed or removed asset | Do not re-upload an asset whose ownership or permission cannot be resolved. | Remove it or substitute an original capture that documents the same fact without copying unrelated artwork. |
Change a checked date only after the cited source, current interface, screenshot, or mechanic has actually been reviewed.
After a major update, recheck class prices and perks, treatment wording, anomaly signs, event timing, route rewards, and progression separately.
When two current reports disagree, preserve the conflict and the conditions around each result instead of forcing one exact value.
Use a second run or independent capture before turning a one-player discovery into a fixed instruction.
Move superseded mechanics into historical context when useful; do not present an old screenshot as the current interface.
