Forge & NFT burning

The Forge converts supported NFTs into Nomgars. Burning permanently removes the source NFT. A confirmed burn cannot be reversed by closing the page, and mint delivery happens afterward in a separate transaction.

This guide describes the current Gem-priced Forge on Ronin mainnet. Use the official Forge interface so the source NFT, receiving account, current fee, and reward are reviewed together.

At a glance#

Paying a Forge fee does not purchase the source NFT. You must already own the eligible NFT in a wallet you can use in the flow.

Before you start#

1. Log in to the Nomgar account that should receive the Nomgars.
2. Open Account settings and add/link the wallet holding your source NFTs if it is not already available.
3. Make sure that wallet can approve and submit transactions on Ronin.
4. Have enough Gems for the selected batch. Use TOP UP if needed.
5. Be ready for the network fee shown by your wallet where gas is not sponsored.

The wallet you burn from and the receiving account address can differ. Check both. Selecting another source wallet does not mean the destination should become that wallet.

Burning RagMons step by step#

1. Open Forge and choose RagMon.
2. Select the linked wallet holding the RagMons.
3. Load your inventory. Use rarity filters, name search, or an exact token ID to locate a card. For a large wallet, use Load more or Load all when necessary; a search across loaded cards is not proof that an unloaded NFT is absent.
4. Select up to 20 RagMons from that wallet.
5. Read each conversion preview. The artwork shows the Nomgar you will receive; the source name and token ID identify the RagMon you will burn.
6. Click Review. The Forge rechecks ownership and the selected NFTs' type and level.
7. Review the exact source token IDs, resulting Nomgars and levels, total Gem fee, source collection, and receiving address.
8. If requested, choose Approve NFTs and confirm the NFT collection approval in your wallet. Approval grants permission; it does not itself burn the RagMons.
9. Choose Burn & forge and confirm the burn transaction in the correct wallet. The reviewed Gems are reserved for this authorization.
10. Wait for the burn transaction to confirm. Then watch Mint delivery or the Forge activity history for each resulting Nomgar.
11. When delivery is confirmed, open My Nomgars or refresh the game Collection.

A supported RagMon maps to its configured Nomgar while keeping the source rarity and level. Variant types can have a specific mapped appearance. Always use the selected token's preview for the actual mapping; do not infer the result just from a collection thumbnail or an old name.

See the 48-type RagMon conversion reference to look up source names and mapped species before selecting your tokens.

If a token says there is no Nomgar for its type, it is not selectable for that conversion. Tokens already burned or no longer owned cannot be used again.

Burning partner NFTs#

The public live collection list reported the following mappings enabled when checked:

Availability is checked against the active redemption configuration. An enabled collection listing is not proof that every wallet or token has passed the final burn checks. Caps, pauses, ownership, and transaction compatibility still apply. In particular, Tribes Season One was listed as enabled, but this documentation pass did not execute a successful burn for it.

To redeem:

1. Choose the partner collection/filter and the source wallet in Forge.
2. Select the eligible NFTs. Review the exact token IDs, reward species, level, receiving address, and total Gems.
3. Review NFT approval where available. Once per collection is the default for a partner batch; choose Only selected NFTs if you prefer individual token approvals. Existing approvals are reused. Confirm only the outstanding approval requests shown for your selection.
4. Confirm the batch burn. All selected NFTs in the current partner batch burn in one transaction; a batch is limited to 20.
5. Track each item's burn status and subsequent mint delivery.

Partner conversion awards the configured result shown above; the source NFT's rarity or level does not automatically carry over as it does in RagMon conversion. One selected partner NFT produces one configured Nomgar.

Approval scope for partner batches#

The collection approval update applies across the supported partner collections. Under Once per collection, multiple NFTs still needing approval in the same collection use one collection approval, rather than one approval for each NFT. Existing collection or token approvals are reused; if only one NFT still needs approval, the Forge requests a token approval for that NFT. Different collections need separate permission checks: Apeiron Apostles and Apeiron Planets are separate collections.

A collection approval lets the reviewed Forge contract transfer all current and future NFTs in that collection from the chosen wallet until you revoke the permission. The burn itself still uses only the selected NFTs shown in the review. Only selected NFTs retains individual token approvals for players who prefer that scope. Approval does not itself burn NFTs or reserve the Gem fee.

Approval rollout: these choices require the updated Forge. An older Forge can still request individual approvals for a partner batch. Check the scope in your current review before signing; do not assume an existing approval applies to another wallet, collection, or Forge contract.

Voting on the next burnable collections#

The Forge Vote page runs an advisory poll on which partner collections the Forge should burn next. It is for signed-in players: log in to see the ballot and the tallies, then pick a collection that one of your wallets holds — the site checks your linked wallets on Ronin when you vote. One vote per account per round; you can change it until the round closes. The ballot itself is set by the Nomgar team each round.

The poll is advisory. Enabling a collection in the Forge is a separate on-chain action by the Nomgar team, so a winning vote is not a guarantee or a date. The live list of what the Forge burns today is the collection disclosure linked at the bottom of this page.

Approval, burn, and delivery are different steps#

The burn receipt is not a mint receipt. “Transaction confirmed” alone is not the same as “Nomgar delivered.”

Cancelled burns, failed transactions, and refunds#

• If you cancel before a burn transaction is submitted, the source NFT remains yours.
• If Gems were already reserved, you can retry the same authorization/selection while valid without paying the fee again.
• An unused reservation returns after about 10 minutes plus confirmation time, once it is confirmed unused. The refund is not guaranteed at the exact second the countdown ends.
• A reverted burn does not successfully destroy the source NFT. Network gas can still have been spent.
• A confirmed burn consumes the source NFT and its fee. Delayed mint delivery is a recovery issue; it is not a reason to burn another NFT for the same intended result.
• An existing reservation for another selection can block a new burn. Finish that selection or wait for unused funds to return.

When something looks wrong#

No NFTs appear: check the source wallet and collection, load more inventory, clear filters, and refresh. “Inventory unavailable” is a loading failure, not a verified zero balance.

The wallet/account changed: return to selection and review again. The confirmation is intentionally tied to the account, source wallet, token IDs, and destination you reviewed.

Approval succeeded but nothing was delivered: approval is only permission. Check whether you submitted the actual burn.

Burn confirmed but the Nomgar is missing: inspect the item's Mint delivery state and receiving address. Refresh My Nomgars after delivery completes. Keep the burn transaction hash and source token IDs for support.

The page closed during the process: return using the same account. Check activity/recovery before creating a fresh burn. If there is a transaction hash, inspect its outcome first.

The Forge is paused or cannot verify a quote: wait for availability to return. The interface should not be bypassed with a manual transfer or a transaction copied from an old guide.

For support, record the source collection, source token ID, source wallet, receiving address, burn hash, timestamp, and visible status/error. Never include a seed phrase or private key.

Current collection disclosure: Nomgar redeemable collections. Current fee and limits: Nomgar configuration.