+1 Backflip Obby Escape source policy is simple: official Roblox pages and public APIs come first, high-trust guides can support context, and unverified code, map, exploit, or secret claims stay out.
Source hierarchy
+1 Backflip Obby Escape source policy starts with official Roblox sources: the experience page, Roblox public games API, Roblox thumbnail API, and creator group identity. Those sources are used for the experience name, creator, play link, created date, updated date, genre fields, maxPlayers, Wins, Boots, and the basic gameplay loop.
High-trust media or hands-on coverage can support beginner context, but it does not override Roblox data. Community videos and stats pages can help spot questions players ask, yet they are not enough to publish exact map routes, active codes, upgrade formulas, or secrets.
What this wiki will not publish
This +1 Backflip Obby Escape source policy blocks pages that would mislead players. The site will not publish fake active codes, exploit scripts, auto-farm downloads, executor links, copied patch notes, invented stage names, secret route claims, or tier lists without visible criteria.
If a topic is popular but unsupported, it may appear as a “held topic” inside a real page. That lets players know the site checked the question without turning uncertainty into a fake guide.
How pages become eligible
A new page becomes eligible when it answers a distinct player task and has enough evidence. For example, Wins and Boots are eligible because the Roblox description names them. A stage map is not eligible until stage names and routes can be checked. A codes page is eligible because players need a safe answer, but it must say no verified active code until a reliable source confirms one.
The +1 Backflip Obby Escape source policy also requires updates to stay visible. When a claim changes, this wiki updates the page, related links, sitemap dates, news log, and source notes together.