A team shooter taking shape on a cargo ship

The idea is a quick, readable first-person contest between two teams on one compact ship. The planned game should open in a browser without an installer or account. Those are goals, not features available today.

• Short routes and cover should reward awareness; the exposed deck is not the only path.
• A visible score, timer, teammate markers, and respawn cue should keep the match legible.
• Solo play against computer opponents comes first; social play is planned later.

Today you can read the plan; you cannot start a match. This page is separate from the private prototype; a room-code URL cannot open a match. There is no queue or setup step.

The next public milestone we are working toward is a browser-playable solo team match against computer opponents. Controls, rendering, and phone usability need validation first. Private rooms and adaptive opponents remain planned.

The planned arena spans the deck of a large container ship. Teams begin near opposite ends, with the long central deck drawing them toward each other. Containers, crates, and ship structures interrupt sightlines, so a straight run is quick but exposed. Side passages offer a different angle, while raised positions can watch parts of the deck. Close- and long-range play should both have a place.

• On the main deck, use containers and crates as cover before crossing a gap.
• Side corridors narrow the approach, but their exits can be watched.
• Opposite-end spawns reconnect to the center through multiple routes.

The design is continuous team combat, not a one-life elimination round. Two teams collect points from confirmed eliminations. A match ends when one side reaches the target score or the time limit expires; the higher score at the limit wins, and an even score is a draw. Players return after a short respawn delay rather than sitting out the rest of the match.

1. Choose a team and primary weapon; a sidearm, knife, and grenade fill other slots.
2. Watch the central lane and side routes; support a teammate.
3. After a respawn, change your route. Team score decides the match.

Keyboard and mouse are the reference controls for the planned game. These are design details, not instructions for a playable page. Mouse movement aims; Escape would pause. On touch devices, the design uses a movement pad, swipe-to-look area, and on-screen action buttons.

W A S D / mouse

Move through the ship / aim the view.

Shift / Space / C

Walk quietly / jump / crouch.

Left click / right click

Fire / scope the sniper or use the knife’s heavy strike.

1 2 3 4 / Q / wheel

Choose primary, sidearm, knife, or grenade / return to previous slot / cycle.

R / F / B

Reload / inspect weapon / choose a different primary for the next spawn.

Tab / Escape

Show the scoreboard / pause or open settings.

Planned touch controls put movement on the left and camera movement on the right, with buttons for firing, jumping, crouching, reloading, switching, and scope. Phone usability still needs testing.

The current loadout design contains seven choices across six roles: two primary rifles, one sniper rifle, one compact automatic weapon, a pistol, a knife, and a grenade. You choose among the four primaries; the other three fill separate slots. Each suits a different distance or tempo.

• The harder-hitting rifle rewards measured bursts. Release the trigger before recoil pulls aim away.
• The steadier rifle gives a more forgiving rhythm. Start here while learning the deck.
• The sniper rifle is built for deliberate, scoped shots and sightline control. Use it from cover.
• The compact automatic weapon favors movement and nearer corners. Close distance behind cover.
• The pistol is a backup when a reload would take too long. Make each shot count.
• The knife has a quick strike and a slower heavy strike. Use it only within reach.
• The grenade can dislodge a position or interrupt a push. One per life makes timing matter.

When a playable build arrives, start by learning one route rather than trying to master every weapon. Decide where to cross, when to stop, and who can cover you. Use each respawn to try a better route.

1. Pick the steadier rifle, follow a teammate, and notice cover around the center.
2. Pause before each uncovered crossing. Listen and look down a side lane, then move with a destination in mind.
3. After a death, check the score and change your approach.

Private rooms are planned after the first solo browser release; they cannot be opened yet. The intended room address uses https://playcsbrowser.com/?room=… as a pattern. A future host could share a link, set an optional password, assign teams, check readiness, and start.

• Planned invitation links from a Copy invitation action would let invited friends skip a room password. A normal link would still require that password.
• Planned friend rooms would support up to eight humans total, arranged as four versus four. Computer opponents would fill empty seats so a small group could still play a full match.
• The planned host flow makes readiness visible before starting.

The first planned playable milestone is a solo match against computer opponents. They should use the ship routes and cover, so you can learn the match loop. This is still in development.

A later planned improvement is adaptive computer-opponent behavior: their pressure would respond to how the human players are doing. The aim is useful pressure for different skill levels. There would be no manual difficulty selector in that future flow, so players would not have to guess a setting before understanding the game. It is not a live feature.

The game is being built for a modern browser with WebGL. A download-free experience on desktop and phones is planned, but this landing release has no playable build to benchmark. Compatibility must be tested on real devices, not inferred from this page loading.

• Planned quality presets would trade detail for motion across phones and desktop hardware.
• Planned touch controls would keep movement and aiming separate, with clear buttons rather than expecting a keyboard on a phone.
• Loading, input, and HUD readability need real-device tests.

No account is planned for the game. A future match would use an editable nickname. If country flags are introduced beside players, the planned server flow would derive coarse country information for that display and would not store the raw IP address.

• Planned names and flags would help identify players, not rank them.
• Planned private invitations and optional passwords would control room access.
• Fair play should come from understandable rules, readable feedback, and balanced paths. No paid weapon advantage is planned.

The sequence is planned, not dated. This first release explains the project and marks the game as unavailable. Next comes a browser-playable solo team match against computer opponents, after controls, rendering, and basic match flow are validated. Private friend rooms are a later step. Milestones may change after testing.

1. Now: this bilingual information page and an honest status panel.
2. Next: a planned solo browser match against computer opponents.
3. Later: planned rooms, invitations, adaptive opponents, nicknames, flags, and quality choices.