Crafting in Build a Base RNG should turn a verified material into a known progression result. Current community guides connect crafting with boss and relic progression, but a stable official recipe database was not available for this source pass. Every input, quantity, cost, unlock, and output must be read from the current in-game interface before confirmation.
Find and record the live recipe
Open the crafting interface from the verified experience and capture the output’s exact name, item family, rarity label, icon, and live description. Record every input, required quantity, currency cost, unlock requirement, and timer. Check whether crafting consumes an owned base item, a relic, or only materials.
Do not rely on an image that crops out the recipe title or update state. The same icon can represent a related material, and an old recipe may remain searchable after an update. Use Place ID 99108783264633 and creator Slungpy Games to confirm game identity.
If the interface is unavailable, locked, or unclear, preserve the materials. A missing recipe is not an invitation to reconstruct one from comments.
Decide whether the output solves a bottleneck
Start from a repeatable wave or boss failure. Identify whether the base lacks contact duration, protected damage, lane coverage, fallback strength, rolling access, or economy. The craft is justified only when its live output addresses that problem better than saving the ingredients.
Compare the output with the item it would replace. Read range, behavior, upgrades, and restrictions from the live panel where available. Do not craft because the output has a rarer color or because a showcase calls it “best.” A valuable output can still duplicate a job the base already covers.
Use Boss Waves to establish the test and Items to classify the output’s role. If the recipe consumes a relic, first complete the Relics checklist.
Protect scarce and event materials
Preserve at least the first copy of an unfamiliar boss or event material until all visible recipes have been inspected. Note whether an ingredient is permanent, event-limited, code-granted, or tied to one encounter. A material with several recipe destinations should be allocated only after comparing the outputs.
The official description confirms a Tsunami update and hourly event activity on the verification date. It does not publish event recipes. Record the live timer, material name, recipe availability, and whether an output remains usable outside the event. Do not assume a current event item will be obtainable or craftable later.
Avoid converting materials immediately after a reward screen. Return to the crafting interface, verify quantities, and read any irreversible warning. If the game offers a confirmation dialog, review the before-and-after inventory instead of clicking through automatically.
Test the crafted result fairly
Save the original layout before installing the crafted item. Run the same normal wave or boss encounter with the same surrounding pieces and permanent upgrades. Replace one item or position and record the first failure, lane coverage, useful uptime, and final core condition.
If the crafted result has a different role, compare it within that role rather than declaring one universal winner. A weapon, trap, block, and utility piece solve different problems. If the output is an account upgrade or rolling benefit, compare access or progression over a defined session rather than one lucky roll.
Do not make a second craft until the first result is understood. Multiple simultaneous changes make it impossible to know which ingredient produced value.
Handle randomized or upgrade recipes
If the output is random, capture the stated pool, odds, pity, variant, mutation, or luck wording before crafting. Record the actual result without assuming a hidden rate. One craft confirms possibility, not probability.
If crafting upgrades an owned item, check whether its level, variant, upgrades, placement data, or lock state carry over. Save screenshots or notes before confirmation. If the interface warns that attributes will reset, include that cost in the decision.
If duplicate inputs are required, verify whether any copy is currently placed in the saved base. Removing a structural piece can damage offline or wave progress even when the recipe output is stronger in theory.
Crafting record template
- Recipe and output exact display names.
- Recipe screen date and update or event state.
- Every input name and quantity.
- Currency cost, timer, and unlock condition.
- Whether an owned item or relic is consumed.
- Output role, live description, and restrictions.
- Irreversible or reset warning.
- Baseline layout and intended bottleneck.
- Controlled test result after crafting.
The record makes future update checks easier. If a cost or output changes, the old observation remains dated evidence rather than an accidental current claim.
Crafting mistakes and FAQ
- Copying a recipe without checking the current game screen.
- Spending the first rare material before inspecting every use.
- Crafting for rarity instead of a measured layout need.
- Ignoring event expiry or mode restrictions.
- Replacing several layout pieces during the output test.
- Treating one randomized result as the recipe’s exact odds.
What should I craft first?
Craft the verified output that solves the next repeatable bottleneck with the lowest irreversible material risk. If no recipe clearly does that, save the materials.
Are recipes and costs listed here?
No fixed table is published because exact current recipes were not independently verified. The live crafting screen is authoritative.
Can event materials be saved?
That depends on the current item and event rules. Check the live inventory, expiry wording, and recipe availability before planning around future use.