Forge Wars Guide

Forge Wars is the strategy layer inside DustForge. The recycler is the practical tool: it helps users clean Solana wallet clutter, reclaim rent from eligible token accounts, and burn spam NFTs. Forge Wars adds a persistent Foundry loop on top: forge plots, resources, troops, NPC villages, battle reports, upgrades, and progression.

The point is not to hide the app behind a game. The point is to give active users something to do with the identity and utility they build through SMELT. A wallet cleanup product can be useful once; a Foundry can give the user reasons to return, upgrade, and experiment.

Forge Wars is local-first in spirit and deliberately lightweight. The design avoids turning the homepage into a cockpit covered with blinking buttons. Core wallet cleanup remains direct. Game features live in dedicated Foundry routes so the recycler stays understandable.

A forge plot represents a user’s permanent home base in the Foundry. Claiming or owning a forge can unlock bonuses around recycling, staking, and progression. This makes the plot more than decoration: it becomes the bridge between wallet cleanup and the longer-term game loop.

Progression uses familiar strategy-game concepts: resources, upgrades, troops, reports, and map targets. The current NPC village terminology is intentional. It avoids the old goblin-only language and makes the combat loop clearer for normal strategy-game players. Raiders belong in the archive goblin museum; troops are the standard term now.

The best Foundry design keeps information in dedicated tabs instead of overwhelming the map. Troops, reports, store items, and stats should be discoverable without burying the user under overlays. A clean strategy UI is usually a better strategy UI. Fancy clutter is still clutter, even if it wears bronze armor.

The combat loop centers on sending trained troops toward NPC villages, waiting for march timers, and reviewing battle outcomes in reports. Reports are important because they explain what happened: what was sent, what returned, what was gained, and whether the action produced meaningful progress.

NPC villages give the Foundry a predictable target type for early gameplay. They are easier to understand than live PvP and safer for an MVP loop. A user can learn timing, troop strength, and resource flow without being thrown into an adversarial economy on the first click.

Reports also separate current Forge battles from legacy local archive data. That matters because older browser-local goblin history should not confuse the active game model. The current loop should talk about troops, NPC villages, and Foundry reports. The old goblins can stay in their archive drawer, eating deprecated breadcrumbs.

Forge Wars gives SMELT more in-app context. A token with cleanup rewards and staking utility is useful, but a game layer can make the protocol feel alive. Forge ownership, upgrades, resource sinks, and strategy goals can create reasons to hold, use, and earn SMELT without pretending that the token is only a yield object.

The connection should stay honest. Forge Wars does not remove the need for safe wallet approvals. It does not guarantee staking returns. It does not make dust tokens magically valuable. It gives DustForge a broader loop: clean wallets, earn SMELT, stake for reward participation, and use the Foundry for progression.

For SEO, Forge Wars also gives the project a distinct identity. Many pages can explain Solana token account cleanup; fewer can connect cleanup to a weird little smithing strategy layer. Weird is useful when it is clear. Weird without clarity is just a fog machine with invoices.