This Jujutsu Legacy source policy publishes Roblox and high-trust facts first, labels community data clearly, and refuses to invent active codes, drop rates, formulas, or rankings.
Source hierarchy
The Jujutsu Legacy source policy starts with the official Roblox game page. That source is best for playability, creator listing, title themes, official description text, and community-link prompts. Third-party code pages are useful for discovery, but code status should be retested. Community wikis are useful for player tasks and broad system labels, but they are not official proof of current values.
What this wiki can publish
This site can publish hub pages for codes, Trello and Discord checks, beginner routes, Technique names, Vessel names, clans, races, bosses, quests, locations, raids, updates, FAQ, and general gameplay. It can also publish cautious checklists and planners when the page explains what is confirmed and what still needs testing.
What this wiki will not publish
- Fake active-code guarantees.
- Permanent Trello or Discord invite promises.
- Exact drop rates without current evidence.
- Damage formulas or cooldowns without testing.
- Tier rankings that would waste player spins.
- Build pages that rely on old or unstated versions.
- Private Discord rumors presented as public fact.
Update method
When a Jujutsu Legacy claim changes, the visible page, source panel, related links, sitemap date, and updates log should change together. If a source cannot support a page anymore, the page should become a cautious overview or be held until better evidence exists.
Analytics and privacy boundary
Jujutsu Legacy Wiki uses Google Analytics 4 for aggregate traffic measurement, such as page views, traffic sources, countries, device categories, and engagement signals. This analytics setup is used to understand site health and player questions. It is not evidence for active codes, drop rates, boss rewards, account status, Roblox login details, or official Jujutsu Legacy support.