GameTio

Rift War: Merge & Evolve Weapons Guide: Gameplay and Controls

A reference to the published gameplay and controls for Rift War: Merge & Evolve Weapons, with the official play link.

Quick answer: Rift War: Merge & Evolve Weapons Guide: Gameplay and Controls. A reference to the published gameplay and controls for Rift War: Merge & Evolve Weapons, with the official play link. This guide covers Rift War: Merge & Evolve Weapons on GameTio. Last verified Oct 14, 2026. Source-checked; not playtested by GameTio.

Source-checked · Not playtested. View sources

On this page

Gameplay overview

A merge-style weapon evolution game. Combine two weapons into a stronger one, starting from a simple rock, and hold the line against waves of monsters.

Build, merge and deploy

Tap the station to build a weapon. Drag two matching weapons together to merge them, then drag a weapon onto the wall to make it shoot automatically. The official description says to put your best five weapons on the wall.

Collect gold and maintain the wall

Move over coins to collect them. BUY supplies a new weapon, and the wall button repairs the wall. Drag an unwanted weapon to the bin to discard it. The page also describes new ages as you continue merging, boss fights, upgrade cards and rebirth with permanent bonuses. Mouse and touch controls both use clicking or tapping, holding and dragging.

Where to play

Open the GameTio game page and select Play to open the official Rift War: Merge & Evolve Weapons page.

This reference follows the official page snapshot checked on October 14, 2026. GameTio has not played the game.

Frequently asked questions

Is this Rift War: Merge & Evolve Weapons guide playtested?

No. This guide is source-checked from official and community sources, not playtested by GameTio.

Sources & verification Checked Oct 14, 2026
Checked Source-based guide
  1. Rift War: Merge & Evolve Weapons — official CrazyGames page Official source

    Official page snapshot read offline on 2026-10-14; gameplay and live availability were not tested.

Editorial policy