How to Play rogueclacks: Tips, Controls & Strategy

1. Customize your Weapon Ball (weapon identity and starting kit).
2. Enter a wave — the ball fights automatically against an enemy ball that gets tougher as the run goes on.
3. Win the bout (or learn from a loss) — success opens an intermission.
4. Pick a Perk from three options; you may reroll once that intermission if the offer is trash.
5. Repeat as enemies receive more random stat upgrades each wave, while your perk stack defines whether you snowball or stall.

Runs sit around a half-hour when things go well; the game is still in development, so balance and content can shift.

1. Open the itch.io page for rogueclacks and launch the HTML5 build in the browser (or grab the free zip if you prefer offline).
2. Start a run and pick a weapon/ball setup you understand from the UI labels—do not rush past tooltips if the build shows them.
3. Let the first auto-battle play out. Watch how damage lands (melee pressure, projectiles, healing ticks) rather than mashing during combat.
4. After the wave, read all three Perks before clicking. Ask: does this fix a weakness I just saw (survivability, damage uptime, utility), or only pad a stat I already win with?
5. If all three options are dead ends for your weapon, use the one reroll immediately—do not “save” it for a perfect future offer that never arrives.
6. Note enemy growth: each wave the game randomly upgrades enemy stats, and higher waves stack more of those upgrades. Plan for mid-run walls, not only free early wins.
7. Keep stacking perks that synergize with your weapon’s rules (some weapons do not use “damage” perks the way you expect—see Tips).
8. Push until you lose; then restart with one clearer rule: *one synergy theme per run*, not a grab-bag of unrelated buffs.

Public listing tags mouse and touchscreen as inputs. Combat is auto-battler style—you are not expected to steer every bounce mid-fight the way you would in an action arena game.

What to look for on the host UI (without inventing keybinds):

• Menus / start / weapon select: click or tap options and confirm buttons.
• Intermission perk row: select one of three cards; look for a reroll control used once per break.
• Pause / mute / restart: check the in-game chrome or browser tab if present; itch HTML5 builds vary.

If something does not respond, confirm the game canvas has focus and that you are on the interactive frame, not a static screenshot.

1. Spend the intermission like a shop, not a lottery. After each fight, name the problem you just felt (dying first, winning too slowly, missing sustain). Pick the perk that answers that problem.
2. Use the single reroll early when the offer is anti-synergy. One bad forced pick early can brick a weapon more than a slightly suboptimal mid-run choice.
3. Respect weapon-specific perk math. Example from the creator’s notes: Bow does not treat damage-increasing perks like flat hit power—the perk often changes how many arrows fire, not the listed “damage” the way a club might. Read effects for *your* weapon, not for a generic RPG.
4. Chase explicit synergies. Another spoiled combo: Scepter gets double self-healing while Inner Peace’s debuff is active. That is the kind of pair that turns “okay sustain” into a real win condition—hunt similar pairings instead of stacking three mild unrelated buffs.
5. Assume enemies scale sideways. Random stat upgrades mean one run the foe becomes tanky, another bursty. Prefer perks that keep you flexible (sustain + reliable damage) over fragile glass-cannon stacks until you know the wave curve.
6. Theme the ball. A coherent identity (heal-and-outlast, multi-hit projectile spam, chip-and-debuff) usually beats a buffet of “+something” cards that never interact.
7. Watch the fight you just won. If you barely scraped by, the next intermission is for defense or tempo, not greed. If you crushed it, you can invest in scaling that pays off later.
8. Expect half-hour session length. Plan one focused run with a hypothesis (“this weapon + sustain path”) rather than five aborted starts.

• Clicking the first perk without reading all three. Auto-battlers punish autopilot upgrades more than they punish slow reading.
• Hoarding the reroll for a mythical perfect board while accepting a build-killing option now.
• Applying universal “+damage” logic to every weapon. Bow-style systems and similar outliers waste those picks; you are optimizing the wrong lever.
• Ignoring enemy progressive upgrades. Early easy waves are not proof your build is finished—late waves get *more* random stat rolls.
• Splitting the run across unrelated mechanics (a little heal, a little crit fantasy, a little utility) so nothing comes online before the curve spikes.
• Treating combat as a place to “play better with keys.” Skill expression here is mostly prep and perk sequencing; dying and blaming “aim” misses the genre.

Is rogueclacks free? Yes—play the HTML5 version on itch.io or download the free package listed on the page.

Do I need to download it? No for browser play. A download exists if you want a local copy; the listing is HTML5-first.

Is it single-player? Yes. You customize one Weapon Ball and climb the Rogue League against generated opponents.

How long is a run? About a half-hour is the listed average session when a run goes the distance.

Any beginner tip if I keep dying mid-run? Use the post-wave screen aggressively: fix the failure mode you just saw, spend the reroll when the three options do not match your weapon, and prioritize weapon-true synergies over generic stat stickers.

Is the game finished? It is marked in development on itch.io, so expect iteration; core idea (auto ball fights + perk intermissions) is already playable.

Play free on itch.io via /game/rogueclacks.