
Hello, my team and I just released Siderform: Planetary Conquest, a free turn-based tactical strategy game that runs directly in the browser without installs or server-side game accounts.
The goal was to combine the territorial tension and resource management of tabletop board games like Catan with quick 1v1 web sessions. Every turn begins with a manual dice roll to harvest Solar, Metal, Bio, and Gas across a procedural grid. You then spend two Action Points to expand with Outposts, upgrade them into Living Pods, launch Bio-Takeovers on enemy sectors, or trigger Overclock to extract resources immediately from a controlled sector without waiting on RNG.
On the technical side, the entire client is built with vanilla JavaScript and HTML5 Canvas2D with zero external game engine bloat. For online multiplayer, we integrated PeerJS to establish direct WebRTC peer-to-peer connections via private room codes, allowing players to start 1v1 matches without matchmaking servers. Local progression and the 50 in-game achievements are stored client-side with a simple JSON export and import feature so players keep full ownership of their save state.
You can play it right now in a desktop browser on itch.io: https://regixlabs.itch.io/siderform-planetary-conquest
Any feedback on the WebRTC connection stability, Canvas rendering performance, or game balance is welcome.
Top comments (2)
Shipping a turn-based board game on raw Canvas2D without an engine wrapper keeps load times instant, but there are two Canvas quirks that usually bite once people test across different laptops:
For the procedural grid lines and hex or tile boundaries, sub-pixel snapping is worth watching on HiDPI displays. When scaling the canvas buffer by
window.devicePixelRatio(canvas.width = rect.width * dpr; ctx.scale(dpr, dpr)), fractional stroke coordinates cause noticeable anti-aliasing blur and seam bleeding between adjacent sectors. Rounding tile vertices to integer coordinates (Math.floor(x) + 0.5for 1px path strokes) keeps the grid razor sharp on Retina screens.Also, since turn-based gameplay is mostly idle between clicks, repainting only dirty rectangles (or drawing static board tiles once to an
OffscreenCanvasand blitting withdrawImage) drops idle CPU usage to near zero during thought time, rather than running a continuousrequestAnimationFrameloop.On the PeerJS side, default public STUN servers handle home Wi-Fi fine, but cellular hotspots or strict symmetric NATs often drop WebRTC data channels entirely without a TURN fallback. If a match drops mid-game, keeping a sequential move log (
turn_number,action_type,seed) rather than full board snapshots lets peers quickly replay and reconcile state upon reconnecting without desyncs.Building the match as a direct WebRTC peer connection sidesteps a dedicated relay/game server for 1v1, and PeerJS's room-code flow keeps the setup lightweight for a casual session. The thing that usually decides P2P game reliability is state sync rather than rendering: since it's turn-based, you can keep authoritative state on one side and send only action/intent messages over the data channel, which is simpler to reconcile than real-time state broadcasting. One thing to watch for on the networking side is NAT traversal fallback — if a direct ICE connection fails, you still need a TURN relay path or the match can stall at connection, even though the game logic itself is solid.