Scooter's Toolbox

Legit Builder

This tool does not mirror every rule the game uses internally—only the live game is truly authoritative. What we do is compare your item to bundled reference data shipped with this site: loot-pool manifests, catalog slots, inventory composition tags, loot timing and minimum-level hints, weapon part-weight tables, and “where this kind of item might come from” source hints. OK (data) means those checks passed and we found a matching source hint; we still do not guarantee that this exact serial can spawn in-game.
In pool = listed in manifest drop-pool data (in_pool) · Off-pool = not on manifest loot-pool export (in_pool); quests/vendors/rewards still possible — see validation FYI + Sources · Inv tags = composition basetags + per-slot tag chain from exported inv data; failures show as Inv tags: … in validation · NCS = raw catalog slot (no pool filter) · Fail (data) = breaks a rule in the validation panel (not “illegal in-game”)
← Main toolbox Save / YAML
📊 Stats

Site (server)

Page views—
Unique visitors—
Items crafted (world)—

Your browser

Items crafted (local)0

Simple 0 · Guided 0 · Legit 0

📄 Instructions 
Loading instructions…
🫶 Support / Donate
Item & Parts
Select an item type above to see available slots.
Part Stat Effects
Select parts to see their stat effects.
Build stats (core snapshot)
Core Snapshot
Stat estimate — coarse buckets, not in-game DPS. Uses PARTS_STATS_DATA, weapon init tables when a slug appears in output, or parsed text. Full lines and per-bucket breakdown below.
Debug
Output
Select an item type and parts to begin.
Deserialized Code
No code generated yet.
Numeric Spawn
Decode @U serial & check data

Paste an @U serial. The STX decoder (same as BL4 Bulk Deserializer) resolves resolvedParts, maps names to manifest slots (best-effort), then runs the same data checks as manual selection — including inv composition tags when inv_comp_tag_data.js is loaded. Empty or partial mapping still runs checks on whatever matched.

Paste a serial and click Decode & check.
Data validation

Uses manifest / NCS / schedules / weights / stats and inv tag composition rules; panel lines starting with Inv tags: come from the tag graph.

Select parts to validate.
Item info & part checklist
Select an item type to see info.
Evidence (from data)
Select parts to view proof details.
Data Sources
bl4_manifest · NCS (itempool, gbx_ue_data_table, GbxActorPart) · PARTS_STATS_DATA (parts_stats_data.js) · WEAPON_STATS_DATA · LootSchedule & weapon_part_weight_table · inv tag rules (inv_comp_tag_data.js + tag-comp-validation.js) LootSchedule / weapon_part_weight_table come from extracts; mapping a chosen part to a schedule row still uses heuristics we maintain. Status labels (OK / Fail / Uncertain) describe agreement with our tables and rules, not a private “legit” verdict from the game. Stats by idRaw / Stats known come only from PARTS_STATS_DATA here. For full part lookup (same STX idRaw layer), use Advanced Part Search in the main toolbox. For many serials at once (same checks + export alignment flags), use Bulk serial validator. Slot names are checked against NCS (with manifest aliases: mag/magazine, shield/hyperion_secondary_acc, multi/tediore_acc). Element overlap across slots is a consistency heuristic we chose (same element token in two slots); the engine may differ. Rainbow / multi-element single parts are skipped for overlap checks.