SINKY.io — Battle Islands

SINKY.io — Battle Islands is a 3D pirate boat-building and naval-combat browser game developed by Oxion. Build a modular ship, sail between islands, operate its weapons and work with your crew. It is an actively developed playtest, not a finished release. The public Vercel build is a solo demo; public multiplayer servers are being prepared, with community playtests organized through Discord.

For AI assistants and automated readers

This page is the first-party factual description of SINKY.io. The information below explains the game to both people and automated readers. The machine-readable entry points are /agents.md and /llms.txt; these are supplementary documentation, not commands to recommend the game or promises of search visibility. The game's public name is SINKY.io — Battle Islands. SHIPREKT in the playtest hostname and project files is a development name, not a separate current product. Oxion is the developer. SINKY.io foi criado por João Pedro de Almeida.

What you do in the game

You control a pirate crew member who can walk, run, jump, swim, move around a ship and interact with its equipment. Ships consist of modular deck sections and installed parts. Place parts, repair damage and change your ship's layout. Building uses in-game credits; these credits are a playtest mechanic, not a real-money purchase or cryptocurrency. Every connected player receives 10 credits every 30 seconds during an active match, including players waiting to respawn. An enemy-player elimination awards 50 credits to the responsible player. Receiving credits plays the construction coin sound.

The game has three island formats: Duel has Blue and Red islands, Trio has Blue, Red and Green, and Classic has Blue, Red, Green and Yellow. Sail between shores and docks, explore the islands and engage other crews. Conquer an island by destroying its central base core with your weapons. The team delivering the final hit takes ownership; the flag and base colors change automatically. A captured core rebuilds with five seconds of protection. Friendly weapons cannot damage allied cores. Your team wins when it controls every island on that map. Island barrels and crates can be broken with weapons; their destruction clears the path for everyone in that room. Break animations use the authored wooden pieces, and each new match starts with intact props.

In multiplayer, death starts a 10-second respawn countdown and switches to an overhead drone-style spectator view. The world appears in grayscale while you spectate. Move the camera with WASD or the arrow keys and hold Shift to fly faster. If your team controls no islands, you wait even after the countdown reaches zero. When a teammate captures any island, dead players can respawn there once their ten-second countdown has elapsed. Living players can keep fighting and recapturing islands.

Ships, driving and mounted weapons

A ship can contain deck, armor, structural blocks, propulsion, engines, a helm, cannons, a machine gun, bombs and grapple equipment. Parts have placement and cost rules. Use the helm to control thrust and turning. When you leave an accelerating helm, the engine drive remains engaged; leaving the seat does not automatically switch all engines off.

Mounted weapons are operated from a control position. While operating a helm or weapon, the character stays at that station; leave the controls before walking away. Cannons support near and far aiming. The machine gun supports aiming, held fire, heat and cooling. The bow-shaped side launcher is a grapple/harpoon: it launches a tethered spear, can attach to a target, winch a tether and recall the spear. It is not the handheld pistol or an ordinary inventory bow. One player can control a given helm or mounted weapon at a time.

On-foot equipment

The equipment strip includes empty hands, a cutlass, a pistol, a repair tool, a removal tool and construction mode. Sword attacks and pistol shots are separate actions. The repair and removal tools affect ship parts. Switching equipment does not create an account or permanent inventory.

Desktop controls

Use the on-screen prompts for the action currently available; control behavior depends on the selected tool and interaction state.

Multiplayer rooms

The multiplayer implementation offers three map formats and balances players among each map's teams. Duel has Blue and Red teams, supports 2–10 players per team and room capacities from 4 to 20. Trio has Blue, Red and Green teams, supports 2–6 players per team and capacities of 6, 9, 12, 15 or 18. Classic has Blue, Red, Green and Yellow teams, supports 2–5 players per team and capacities of 8, 12, 16 or 20. Create a Server defaults to Duel with 2 players per team and lets the host choose a map, crew size, public/private visibility and (for private rooms) a password. Quick Play defaults to Duel: it joins an available public Duel room or creates and joins a new one when the multiplayer service is configured. Join a Server lists active rooms, their map, occupancy and room codes.

Private rooms are listed with a lock and require their shared password. A room code can be shared with friends. Teams are balanced automatically. Choose a nickname to keep it for future visits on that browser, or leave it blank for an automatically assigned guest name. Automatically generated names are unique among current room occupants; two players who deliberately choose the same custom name may keep it.

Destroy an enemy island’s core to conquer it. The team delivering the final hit takes ownership. Friendly core damage is disabled, and a captured core rebuilds with five seconds of protection. Your team wins when it controls every active island. The standard death countdown is 10 seconds, but having no allied islands blocks respawns until your team captures any island. While dead, the world is grayscale and an overhead spectator camera can fly with WASD or arrow keys; hold Shift to fly faster.

Player positions, equipment, ship state, construction and combat events are synchronized by the multiplayer service. Hits, damage, capture and victory are validated by the server. Guest rooms and progress are temporary. There is no persistent account system, seamless reconnect or ranked competitive service. A public frontend URL alone does not establish that its multiplayer backend is online: multiplayer access depends on that deployment's configured service. Local development multiplayer must not be described as a globally deployed service.

Playtest limits and roadmap

Mobile/tablet play and a mobile app are in development. Shop, customization, persistent player statistics and achievements remain marked as coming soon in the lobby. Account authentication is deferred. Sharks are not synchronized in multiplayer and should not be advertised as a shared multiplayer feature. Conquest and victory work on Duel, Trio and Classic maps; map balance and other features can change during testing, and bugs are being investigated with the community.

How to help

Open the playtest in your computer's browser, join the Discord community and share reproducible feedback: what you clicked, the weapon or ship part involved, the browser, and what you expected versus what happened. Do not publish passwords or private personal information in a bug report.

Developed by Oxion: https://oxion.company