Current Build a Base RNG community guides connect boss progression with relic rewards and crafting. A stable official relic index, exact drop table, and effect database were not available for this source pass. The safest relic guide is therefore a verification workflow: identify the live item, preserve evidence, understand its destination, and only then decide whether to spend or rank it.
Confirm that the reward is a relic
Capture the exact display name, icon, category label, rarity wording, quantity, and reward screen. Then open inventory, Index, relic storage, upgrades, and crafting to locate the same item. A material with a dramatic icon is not automatically an equippable relic, and a similar name in another Roblox game is not evidence.
Record the boss or event name, entry screen, date, and server update label. If the reward came from a code, quest, shop, or event claim instead, keep that source distinct. The source determines whether the item is farmable, limited, or merely a one-time grant.
Use the Official Links guide to verify the game identity before relying on screenshots from outside the official Place ID.
Read the live effect and destination
If the interface displays an effect, copy its wording exactly into personal notes and identify whether it applies to one item, the whole base, rolling, income, bosses, or crafting. Do not convert a vague label into an exact percentage. If no effect panel exists, mark the purpose unknown until another first-party screen explains it.
Check whether the relic can be equipped, consumed, upgraded, combined, or used as a recipe input. Look for slot limits, replacement warnings, binding, or confirmation dialogs. Preserve the first copy rather than testing an irreversible action while its destination is unclear.
An effect observed during one run can be evidence, but isolate it. Keep the layout and permanent upgrades stable, equip only the relic under test, and compare the same normal or boss wave. Record what changed and what did not.
Evaluate a claimed drop rate
The reward preview is the best place to find an official live chance if the game exposes one. Capture the exact wording and whether boosts, event states, luck, difficulty, or pity modify it. If no chance is shown, do not fill the gap with a precise number from a search snippet.
Repeated runs can estimate behavior but require enough observations and stable conditions. Log each attempt, encounter, difficulty, boost state, and result. A small sample can confirm that a drop is possible; it cannot establish a reliable exact rate.
When a community guide supplies a number, check its publication date, game version, named encounter, and screenshot source. Label it Community reported until the live interface or a sufficiently controlled dataset supports it.
Compare relics by progression goal
Avoid a universal tier list until effects are verified. Compare a relic against the problem it is meant to solve. A base failing early contact needs a different improvement from one that reaches a boss but lacks sustained pressure. Rolling or income effects have value only if the extra access changes the next bottleneck.
Use four questions: Does the relic improve the measured failure? Does it replace another effect or stack with it? Is the benefit active in waves, bosses, offline battles, or only one mode? What scarce material or slot does it consume?
Retest the same baseline after equipping or using it. If the result does not move, remove it when reversible and inspect placement before spending more resources.
Preserve event relic evidence
The official description confirms the current Tsunami event and hourly activity as of 2026-08-05, but it does not publish a relic list. If an event reward appears, record the exact event name, timer, claim screen, and whether the item remains visible outside the event interface.
Do not assume an event-title relic is permanent, tradable, craftable, or superior. Verify each property in the live inventory. Old event pages and videos can remain indexed after the reward pool changes.
Save screenshots privately if useful, but use text notes for exact names and conditions. A screenshot without a date, source panel, or Place ID is difficult to audit later.
Relic record template
- Exact display name and capitalization.
- Icon and category or rarity label.
- Boss, event, code, quest, or shop source.
- Date, update label, and server condition.
- Visible chance, guarantee, boost, or pity wording.
- Quantity and storage destination.
- Effect text and applicable mode.
- Equip, consume, combine, or crafting behavior.
- One controlled before-and-after test.
Continue to Crafting only after the live recipe identifies the relic as an input. Return to Boss Waves when another controlled reward attempt is needed.
Relic mistakes and FAQ
- Naming an icon without checking its live label.
- Treating a material and an equippable relic as the same type.
- Consuming the first copy before discovering its use.
- Publishing a precise chance from a small run sample.
- Comparing effects across different layouts or permanent upgrades.
- Assuming an event reward remains after the event changes.
What relics are in Build a Base RNG?
This page does not publish an unverified entity list. Use the live reward, inventory, and Index panels to establish exact names before adding them to a future audited index.
Do bosses guarantee relics?
A universal guarantee was not verified. Read the encounter reward panel and record actual results without converting them into an unsupported rate.
Should I use or save my first relic?
Save it until its effect, destination, recipe role, and any irreversible warning are clear.