What makes this different
Guides that expose the evidence
Many launch-week game pages optimize for speed by copying a code table, a ranking or a number without showing when it was checked. That creates a difficult problem for players: a polished answer can look current even after the game changes. Our approach is to make uncertainty visible.
Time-sensitive pages show a review date. A code string must be independently repeated before it enters our table, while its reward receives a separate agreement, majority, single-source or unresolved label. The tier list preserves the exact labels from five July 2026 rankings and shows where they agree or conflict. Trait rates disclose a published discrepancy instead of choosing the most convenient number silently. Those editorial choices are part of the product, not legal fine print.
Our source ladder
Official or in-game
The official Roblox experience, developer-controlled community posts, and values visible in the live client are the strongest evidence for access, status and current mechanics.
Attributed editorial source
A current article with a named author, visible update date and specific evidence can support code, kit or meta facts. We link it beside the claim.
Independent community report
A player report can corroborate a code or surface a change, but it stays labeled and does not automatically become a confirmed mechanic.
Our calculation or inference
Probability and team-coverage results are our own transparent analysis of published inputs. They are identified as math or inference, never presented as official data.
How a guide or tool is produced
- 1. Define the player decision. A page should help someone redeem a code, choose an investment, fill a team role or understand a system—not merely repeat a keyword.
- 2. Collect current evidence. We prefer official material, then current attributable sources. When a source has no author, date or supporting detail, its confidence is lower.
- 3. Compare before consolidating. Codes and rankings are compared across publications when possible. Repetition does not prove independent observation: publishers may share the same upstream source. A disagreement becomes part of the answer.
- 4. Separate fact from judgment. Unit abilities and trait rates are attributed source claims; a trait direction, team warning or cross-source consensus is analysis built from those facts.
- 5. Check the answer. Tool results must be reproducible from the stated inputs. Source dates, uncertainties and correction links stay visible so readers can decide whether an answer applies to their current game.
Public accountability
Verification register for every core guide
This register names the publisher, page revision date, evidence method, testing boundary and the event that should trigger the next review. Anime Expeditions Hub is the visible organizational author responsible for these guides and tools. We have not conducted firsthand gameplay testing. Game-specific reference data comes from the linked sources; worked examples are calculations, not observed player results.
A page revision date can reflect a new example or clearer explanation. It does not mean the underlying game data was rechecked. Source dates are stated beside the references; no date here claims direct reproduction inside the live client.
Eight-source code and reward ledger
The dated ledger retains only strings repeated by multiple publications, separates reward confidence from live status, and archives older codes instead of presenting them as currently active.
Testing boundary: Code status is based on dated publications. We have not redeemed these codes ourselves; your live result may differ.
Recheck after: a developer code drop, access change or failed-redemption pattern.
Registro de códigos y recompensas de ocho fuentes
El registro fechado conserva solo cadenas repetidas por varias publicaciones, separa la recompensa del estado activo y archiva códigos anteriores sin presentarlos como vigentes.
Testing boundary: El estado procede de publicaciones fechadas. No hemos canjeado estos códigos personalmente; el resultado actual puede ser distinto.
Recheck after: un nuevo código del desarrollador, un cambio de acceso, una recompensa distinta o un patrón de canjes fallidos.
Registro de códigos e recompensas de oito fontes
O registro datado mantém apenas sequências repetidas por várias publicações, separa recompensa de status ativo e arquiva códigos antigos sem apresentá-los como vigentes.
Testing boundary: O status vem de publicações datadas. Não resgatamos estes códigos pessoalmente; o resultado atual pode ser diferente.
Recheck after: um novo código do desenvolvedor, mudança de acesso, recompensa diferente ou um padrão de falhas no resgate.
Live-input calculator
The budget and exact-target probability model is original; no banner rate, pull cost or guarantee type is prefilled from a launch article.
Testing boundary: The result is conditional probability, not a prediction. Enter the exact target rate and guarantee wording from your current banner.
Recheck after: a banner, pity, carry-over or summon-cost interface change.
Calculadora con datos introducidos por el jugador
El modelo original calcula presupuesto, reserva y probabilidad del objetivo exacto; no precarga tasas, costes ni garantías a partir de artículos de lanzamiento.
Testing boundary: El resultado depende de la tasa y garantía que introduzcas del banner actual; no predice el resultado de una tirada.
Recheck after: un cambio de banner, pity, transferencia de contador, coste o interfaz de invocación.
Calculadora com dados informados pelo jogador
O modelo original calcula orçamento, reserva e chance do alvo exato; nenhuma taxa, custo ou garantia é preenchida a partir de artigos de lançamento.
Testing boundary: O resultado depende da taxa e garantia informadas do banner atual; não prevê o resultado de um pull.
Recheck after: mudança de banner, pity, transferência do contador, custo ou interface de invocação.
Current two-source chart comparison + historical five-source matrix
September 8 PGG grades cover 56 forms alongside captured Destructoid role observations. Missing support labels, preliminary placements and Toy Maker’s Unbound condition stay explicit; the 21-unit July five-source dataset remains historical.
Testing boundary: September chart observations and July historical rankings are attributed publisher judgments, not our own playtests. Shared rankings may have a common upstream source.
Recheck after: a balance patch, new banner, new mode or material ranking revision.
47 listed forms + 35 dated profiles
Four Update 2.5 profiles, nine Update 2 profiles and Cubert from Update 1 join 21 historical kit references and 12 starter identities. Four profiles now include September 26 Wiki checks for materials, mechanics and upgrade budgets. The catalog is not a complete current roster.
Testing boundary: No direct live-client roster test is claimed; the deeper analysis is limited to attributed kit records.
Recheck after: a roster addition, kit correction, evolution or balance change.
Official records + hunt calculator and collection tracker
An official badge documents one Shiny summon outcome. Community rate and transfer reports are labeled separately from official evidence. Original target-probability analysis and a direct or conditional-rate calculator support spending and time decisions.
Testing boundary: A roster entry is not proof that a Shiny version is obtainable. We have not measured Shiny rates or tested pass effects.
Recheck after: an official Shiny description, rate panel, eligibility table, transfer system, conversion preview, pass benefit or roster change.
Dated acquisition reports + historical rarity ledger
Newer Secret acquisition reports appear before the separate two-identity July ledger. Each route includes the existing profile’s source date and acquisition limits; the claim checker distinguishes official evidence from reports.
Testing boundary: July sources establish release identities. Newer publisher acquisition reports are not our own live-client tests; current availability and unresolved rates remain unverified.
Recheck after: a new Secret identity, official Index, obtain path, banner, event, rate, pity, guarantee, availability or kit change.
35-kit role model + six explicit player goals
The comparator joins source-reviewed role tags, kit summaries, evolution recipes, specific equipment records and five-source tier signals without inventing a universal power or DPS score.
Testing boundary: The comparison matches reported kit roles to your goal. It cannot establish a live performance winner or a measured DPS advantage.
Recheck after: a unit, role tag, kit, evolution, equipment, tier source or comparison-goal change.
Field-level equipment evidence ledger
Five records in the original July set have detailed corroboration, six partial and six single-source evidence. Seven Update 2 items have single-source details. Six Update 2.5 additions have dated item links and name-level corroboration only; missing stats, drop rates, pity and recipes stay unverified.
Testing boundary: Item associations come from dated references. Live drop rates, roll ranges and item effects have not been tested by this site.
Recheck after: an equipment balance, Mastery, pity or location change.
Current unit routes + historical Story reward directory
Four Update 2.5 unit routes are dated publisher reports. In the separate July Story directory, Beebom supplies all 18 normalized locations; GAMES.GG independently repeats eight exact associations in crawlable prose, and every reward badge preserves the difference between two-publisher and one-publisher location evidence.
Testing boundary: Map and reward associations are dated source reports, not sampled drops. Confirm the current stage preview before spending entries.
Recheck after: a new map, reward move, drop-table or Story progression change.
Mixed-source scope + objective model
Mode existence, scope and reward clues are source-labeled; the objective advisor is an original deterministic model that exposes missing evidence.
Testing boundary: No complete direct clear, schedule or reward-table test is claimed.
Recheck after: a mode launch, unlock, schedule, objective or reward change.
Dated raid reports + Snowy Castle preparation
The guide adds attributed Snowy Castle preparation, currency-name uncertainty, conditional totem budgeting and Auto Play diagnosis. The readiness model uses live-panel and player-entered facts.
Testing boundary: Readiness advice uses your inputs. We have not verified live unlocks, party limits, reward rates or a guaranteed clear strategy.
Recheck after: an official Raid table, Act, entry rule, party rule, schedule, reward, pity, equipment or balance change.
Dated Guild reports + original icon and session tools
Release reports establish customization; a July 30 walkthrough reports separate creation and invitation routes. Original icon downloads and attendance planning support those tasks without connecting to Roblox.
Testing boundary: The planner coordinates times and self-reported roles. It does not verify attendance, connect to Roblox or establish current Guild rules.
Recheck after: a Guild unlock, creation cost, member limit, permission, contribution, reward, party, Tournament or scheduling change.
Published rates + original probability math
Attributed trait rates and pity values feed an original odds calculator; published discrepancies are disclosed rather than silently resolved.
Testing boundary: Probabilities use the reported rates and stated assumptions. We have not collected a live reroll sample; verify rates and pity in the client.
Recheck after: a trait, rate, pity, effect or reroll-interface change.
Tasas publicadas + cálculo original con presupuesto y pity
Dos guías actuales respaldan el coste, las tasas, los efectos y los límites de pity; la calculadora original aplica el saldo, la reserva y el progreso del contador del jugador.
Testing boundary: Las probabilidades usan tasas publicadas. No hemos recogido una muestra de rerolls; verifica las tasas y el pity actuales en el juego.
Recheck after: cambie un Trait, tasa, coste, pity, efecto, filtro de Auto Reroll o interfaz.
Taxas publicadas + cálculo original com orçamento e pity
Dois guias atuais dão respaldo ao custo, taxas, efeitos e limites de pity; a calculadora original aplica saldo, reserva e progresso do contador informado pelo jogador.
Testing boundary: As probabilidades usam taxas publicadas. Não coletamos uma amostra de rerolls; confira as taxas e o pity atuais no jogo.
Recheck after: mudar um Trait, taxa, custo, pity, efeito, filtro de Auto Reroll ou interface.
Attributed kits + original deterministic analysis
The builder joins documented kit tags with eleven explicit dependency, amplification, formation, control, protection and tradeoff records; four evidence labels keep cross-source relationships, detailed single-source records, tactical inference and unresolved dependencies separate.
Testing boundary: Role coverage is inferred from attributed kit descriptions. It does not measure DPS, placement geometry or your account performance.
Recheck after: a unit kit, roster, status interaction or mode-rule change.
Six-stage passport + evidence-gated duplicate model
The saved four-state passport orders account actions from player-confirmed milestones, while the duplicate lab requires exact live cost, result, reversibility and preservation checks without inventing an Ascension boost or copy requirement.
Testing boundary: The next steps depend on the account state you enter. The tool cannot see your inventory or verify current unlock conditions.
Recheck after: an unlock, Beginner Path, resource, evolution, equipment, Potential, Trait, duplicate or Ascension-system change.
Four-source system review + local persistence model
Current sources establish the recurring claim, quest, challenge, shop and progression surfaces; the original tracker orders them without hardcoding a universal reward or reset time.
Testing boundary: Checks are your private notes. They do not claim rewards, synchronize with Roblox or establish a universal reset time.
Recheck after: a reset schedule, quest, challenge, Calendar, event, shop, Battle Pass or storage-behavior change.
Cuatro fuentes actuales + persistencia local
Las fuentes actuales respaldan los sistemas recurrentes de recompensas, misiones, desafíos, tiendas y progresión; el planificador original los ordena sin inventar recompensas ni una hora universal de reinicio.
Testing boundary: Las marcas son notas privadas. No reclaman recompensas ni se sincronizan con Roblox; confirma los reinicios en el juego.
Recheck after: cambien el horario de reinicio, las misiones, los desafíos, el Calendario, los eventos, las tiendas, el Pase de batalla o el almacenamiento local.
Quatro fontes atuais + persistência local
As fontes atuais dão respaldo aos sistemas recorrentes de resgates, missões, desafios, lojas e progressão; o planejador original organiza essas ações sem inventar recompensas nem um horário universal de reinício.
Testing boundary: As marcações são notas privadas. Não resgatam recompensas nem sincronizam com Roblox; confira os resets no jogo.
Recheck after: mudarem o horário de reinício, as missões, os desafios, o Calendário, os eventos, as lojas, o Passe de Batalha ou o armazenamento local.
Claim-level mechanics ledger + 14-grade single-publisher table
The page separates independently repeated lock and transfer mechanics from one named publisher’s complete tier table and a live-only Worthiness claim, then keeps every probability result inside that boundary.
Testing boundary: Advice combines reported grades with your inputs. We have not measured reroll rates or verified live lock costs.
Recheck after: an official Potential table, grade, Worthiness, lock-cost or reroll-interface change.
Player-input formula + reproducibility controls
The lab converts player-observed Damage, SPA, hits, placements and uptime plus optional non-duplicated modifiers into transparent rate and time-window comparisons, then grades whether both tests controlled the same conditions.
Testing boundary: The worked examples are hypothetical calculations. The model excludes unentered mechanics and does not establish actual in-game DPS.
Recheck after: an official damage formula, stat export, Showcase, Sandbox, SPA or combat-mechanic change.
Original versioned player-evidence + screenshot workflow
The lab turns player observations into portable records with explicit controls and adds a local screenshot manifest that binds real captures to one visible claim, version, scene, caption, capture method, documented reuse-rights basis, publication scope and edit disclosure.
Testing boundary: Records stay in your browser. Saving or exporting a record does not authenticate its inputs or make it an official test result.
Recheck after: a game version interface, mode taxonomy, local-storage policy, image-evidence requirement, export schema or evidence-grade rule change.
Private portable player-sample notebook
Observed rates use total rewards and total elapsed time so failures, partial payouts and variable drops remain in the player's sample; failed-attempt rewards are preserved while a separate Wilson adjustment penalizes only completion-dependent rewards.
Testing boundary: Worked examples are hypothetical. Route estimates use your recorded rewards and time; the completion adjustment is not a drop-rate confidence interval.
Recheck after: a reward table, stage duration, failure condition or farming-mode change.
Dated resource references and conditional advice
Current item, code, evolution, map and equipment sources establish the resource vocabulary; the interactive spend-or-hold rules are original and preserve source conflicts, TBA acquisition and live-panel checks.
Testing boundary: Spend-or-hold advice is conditional on your chosen goal. We have not verified your inventory, live shop rotation or current drop rates.
Recheck after: an item, shop rotation, event, recipe, banner, acquisition route or resource-name change.
Official API snapshot + six-result SXO review
The Roblox universe catalog and three product records establish pass identity, default price, sale state and creator; empty official descriptions stay unknown while the advisor requires a player-confirmed live benefit before any conditional recommendation.
Testing boundary: The listing is a dated official API snapshot. We have not purchased these passes or tested their live benefits; checkout prices may vary.
Recheck after: a pass catalog, price, sale status, description, creator, benefit panel or Roblox pricing-policy change.
Dated recipes + original account-queue math
Published recipe tables are compared, then the saved multi-unit queue totals shared materials and deterministic gaps against the player's browser-local inventory.
Testing boundary: Material totals use dated published recipes. We have not tested the live Evolve menu; check the recipe before spending inventory.
Recheck after: a recipe, material source, evolution form or cost change.
Recetas fechadas + cálculo original para toda la cuenta
Incluye nueve recetas históricas, Carrot de Update 1 y tres recetas de Update 2.5, con fuentes individuales; la cola guardada suma materiales compartidos y calcula faltantes contra el inventario local del jugador.
Testing boundary: Los totales usan recetas publicadas y fechadas. No hemos probado el menú Evolve actual; comprueba la receta antes de gastar.
Recheck after: cambie una receta, fuente de materiales, forma evolucionada, coste o comportamiento del almacenamiento local.
Receitas datadas + cálculo original para toda a conta
Inclui nove receitas históricas, Carrot de Update 1 e três receitas de Update 2.5, com fontes individuais; a fila salva soma materiais compartilhados e calcula faltas contra o inventário local do jogador.
Testing boundary: Os totais usam receitas publicadas e datadas. Não testamos o menu Evolve atual; confira a receita antes de gastar.
Recheck after: mudar uma receita, fonte de materiais, forma evoluída, custo ou comportamento do armazenamento local.
Platform identity register + private URL verifier
Roblox Place, Universe and creator Group identifiers, the public Discord Guild identity and an identity-checked YouTube channel form a small allowlist; pasted links are classified locally without being opened or uploaded.
Testing boundary: Destination checks do not establish server availability, access to private channels or a relationship with the developer.
Recheck after: a Place, Universe, creator Group, invite, Guild, official channel, Trello, X identity or safety change.
Official entity + dated launch report
Historical release coverage is separated from live server availability, and the correct creator and Roblox Place ID are checked to avoid lookalikes.
Testing boundary: The official destination is checked; continuous server availability is not claimed.
Recheck after: an official entity, access-state or material launch-history correction.
Five-claim evidence ledger + player-state decision lab
The page separates two actions repeated by multiple publishers from two one-publisher details and one live-client gate before routing the player through reversible first-session decisions.
Testing boundary: Guidance uses published references and your answers. We have not played through this onboarding flow or verified live unlocks ourselves.
Recheck after: an onboarding, Beginner Path, banner, Story or unlock change, or a cited video being removed, retitled or moved.
Official snapshot + claim-level patch triage
Update 2.5 feature reporting and its four-form roster cross-check are separated from Update 2 history, two-publication Update 1 coverage, the older official snapshot and site changes.
Testing boundary: Official listing snapshots, third-party patch reports and our site changes are separate. We have no private developer access or direct balance tests.
Recheck after: a developer announcement, patch, hotfix or material source revision.
Tool transparency
Trait odds calculator
Uses the published base rate and the standard independent-roll formula. It applies 100% only at the reported hard-pity threshold and tells players to verify the live counter.
Inspect the calculator →Team Builder
Uses explicit unit tags and kit relationships. It does not manufacture DPS, costs or scores where no reliable public dataset exists.
Inspect the builder →Corrections, rights and accountability
Every guide includes a correction link. Reports should identify the page URL, disputed sentence, current evidence and—when relevant—the game version or date observed. We review the source before changing a claim and update the visible freshness log when the change is material.
For factual corrections, technical problems, privacy questions or rights concerns, use the contact page. We do not require an account or collect public comments.
What we will not publish
- • Exploit scripts, account-selling instructions or unsafe downloads.
- • Datamined or leaked claims presented as official facts.
- • Invented evolution recipes, pity values or live stats added only to fill a keyword gap.
- • A “best” ranking without explaining mode, role, source and review date.
Editorial disclosure updated September 16, 2026. Individual source dates remain listed below.