Arcane Fedora Wiki uses official Roblox pages first, then reliable trackers and clearly labeled community reports. It never publishes fake claims, login flows, or guaranteed value predictions.
Source hierarchy
Official Roblox pages come first. The official catalog page is used for item existence and official naming. Roblox Support pages are used for Marketplace and trading rules. If Roblox changes a rule, this wiki should follow Roblox rather than older community summaries.
The Arcane Fedora source policy is intentionally conservative because item status can change quickly. Every Arcane Fedora source policy update should say whether a claim comes from Roblox, Rolimon’s, Roblox Wiki, or a community report. If a source is missing, the Arcane Fedora source policy requires the page to say unknown rather than guess.
Rolimon’s is used for item tracker fields such as sale status, listed price, favorites, and Limited eligibility. Roblox Wiki is used for item history, offer-window notes, technical details, and appearance descriptions. Community sources such as DevForum, YouTube, Reddit, or X can show what players are asking, but they do not override official or tracker data.
What gets labeled as unknown
Arcane Fedora’s future Limited status is unknown unless Roblox or reliable trackers confirm a new state. Future value is unknown. Exact ownership count is unknown unless a reliable source provides it. Whether a reported visual issue is fixed is unknown unless there is official confirmation or repeatable testing.
This wording is intentional. A good item wiki should be useful without pretending to know more than the sources show.
Safety rules
Arcane Fedora Wiki does not sell Robux, does not broker trades, does not ask for Roblox passwords, does not ask for browser cookies, and does not host free-claim pages. Any reader who needs account help should use official Roblox Support.
The site also avoids investment framing. It can explain Robux-listed price, Off Sale status, Limited eligibility, RAP, value, and demand if those fields become relevant, but it should not promise profit or tell readers that a virtual item is a financial asset.
Update method
When a source changes, update the affected page, homepage status pulse, source notes, sitemap date, and update log together. If sources disagree, say which source says what. If the live status cannot be checked, mark the page as last checked rather than implying real-time monitoring.