Source table
The ledger separates data authority by topic. Roblox APIs are strongest for title, owner, update date, level cap text, current techniques, current vessels, badges, and places. Trello is strongest for compact gameplay rows such as boss health, enemy damage, teacher costs, and quest level order. Code sources are used only as a fast-moving cross-check.
This split prevents a common wiki failure: one source is treated as if it owns every topic. A codes article can be fresh for rewards but weak for boss stats. A Trello board can be strong for older enemy rows but slower for a current update title. The page model keeps those strengths separate.
External links are intentionally concentrated here. Normal guide cards point back into this site so a player can keep comparing routes, drops, and codes without being pushed out on every page. When an external source is needed for auditing, this table gives the raw location and explains exactly what field the site used from it.
A source can be trustworthy for one field and weak for another. Roblox is the authority for the public game description and badges, but it does not publish every boss drop table. Trello is the authority for its own compact gameplay cards, but it may lag behind the newest update title. Code sites are useful only when dates and reward lists are current.
| Source | URL | Used for |
|---|---|---|
| Roblox experience | https://www.roblox.com/games/15694107053/Jujutsu-Legacy | Universe, title, description, creator, level cap, techniques, vessels, visits, favorites, update date. |
| Roblox group API | https://www.roblox.com/communities/33596404/Jujutsu-Legacy-Official | Official community group owned by the same verified creator. |
| Trello board | https://trello.com/b/432tpo1k/jujutsu-legacy | Bosses, enemies, quests, locations, teachers, items, accessories, NPCs, and older code card. |
| PCGamesN codes | https://www.pcgamesn.com/jujutsu-legacy/codes | July 3, 2026 active code cross-check. |
| Destructoid codes | https://www.destructoid.com/jujutsu-legacy-codes/ | July 3, 2026 active code cross-check and redemption steps. |
| MrGuider codes | https://www.mrguider.org/roblox-codes/jujutsu-legacy-codes-wiki/ | July 1, 2026 active code cross-check and Discord link. |
Coverage boundary
The current English build covers the live Roblox description roster, public Trello cards, badge-linked recent drop signals, and July 2026 codes. It does not create separate pages for individual quest steps, plain roster names, clans, raids, or build tier lists unless the public source data contains enough fields to avoid thin guesses.
That boundary is intentional. Roblox live-service games change fast, and a guide that publishes wrong drop rates or copied build rankings loses trust. Thin entries stay inside dense lookup tables until new source data appears, then pages can be promoted into full indexable guides.
The visible competitor sitemap is broader, especially around clans, builds, raids, and individual technique guides. This build does not chase page count by generating claims from titles alone. The gap is recorded so the next iteration can add those sections after collecting reliable source rows or repeatable in-game tests.
The biggest current gap is community or in-game data, not the public Trello board. The Trello board exposes 51 open cards across information, swords, bosses, accessories, items, teachers, quests, locations, enemies, and NPCs. Those rows are already represented in this site. Clans, races, detailed builds, raid mechanics, and technique move behavior require a different evidence layer.
That evidence layer should be added deliberately. A clan page needs names, roll source, rarity or drop source, and stat effects. A raid page needs entry route, enemy or boss structure, rewards, and repeat rules. A build page needs technique, vessel, clan, race, accessory, sword, and the activity it solves. Without those fields, a page is only a search landing page with weak player value.
Next data gaps to fill
Clans and races are the first expansion target because code rewards already mention Clan Spins and Race Spins. A useful page should not simply say that spins exist; it should list each clan or race, how it is obtained, what stat changes it gives, and whether it connects to a boss, item, or raid. Community pages mention richer clan data, but that needs confirmation before becoming this site's structured table.
Builds are the second target. A build page should answer one of three player questions: what clears quests fastest, what farms bosses safely, or what performs in PvP pressure. Publishing a generic tier list without test conditions would be weaker than the current source-backed tables, so the build layer should start with repeatable route and boss tests.
Raids are the third target. Roblox places data confirms a second place named The Strongest Raid, and badge text points to update-era rare drops. That is enough to track the existence of raid content, but not enough to publish route mechanics. The next pass should collect entry steps, rewards, and run structure from public source rows or direct gameplay.
Until those gaps are filled, internal pages should keep players on confirmed tables: codes, route, bosses, techniques, vessels, teachers, items, and glossary. That is a stronger base for search traffic than a larger sitemap built from uncertain community fragments.
