✦FRONTIER / ATLASHISTORICAL WORLDS · VOL. 01
UKRAINIAN FRONTIER48° N · DNIPRO RAPIDS
AUGUST 1635 · LOWER DNIPRO FRONTIER · INTERACTIVE HISTORY

KODAK 1635

THE NIGHT THE RAPIDS AWOKE

Before the fortress became a legend,
the river already had its own law.

Command a Cossack column through moonlit steppe and river mist. Approach the newly constructed Kodak fortress, outwit its guards, and witness a turning point in the struggle over the Dnipro passage. Real history. An alternate tactical outcome shaped by you.

3D IMMERSIVE SIMULATIONSEED 890783THREE.JS r161 · WEBGL2
LIVE OPERATION / RECONNAISSANCE
23:40 / NIGHT WATCH / 1635
✥
RECONSTRUCTING THE FRONTIER
The Dnipro remembers.
Preparing terrain and river…
OPERATION
THE SULYMA ASSAULT
RIGHT BANK · KODAK RAPIDS
SIMULATED TIME23:40
VISIBILITYLOW
FRAME RATE—
+
DRAG ORBIT · SCROLL ZOOM · CLICK INSPECT · SHIFT+CLICK MOVE
SIM SPEED
MORALE 100%GATE · SECUREDMIST · 46% MOON
COSSACK GARRISON FORTRESS
APPROACHTHE WATCHTHE GATECOURTYARD

In the dark, the approaching columns must choose when to make themselves known.

01 / THE HISTORY

A RIVER OF EMPIRES

A fortress built to close a frontier.

In 1635, on a high bank above the Dnipro rapids, the Polish–Lithuanian Commonwealth established a new military post. Its purpose was as much political as strategic: monitor passage to the Zaporizhian heartland, discourage unsanctioned river expeditions, and tighten supervision of a frontier military society.

Kodak, also rendered Kudak or Kodack, occupied a commanding position near a stretch of treacherous rapids. The river was a vital thoroughfare linking inland Ukrainian lands with the lower Dnipro and Black Sea. A fortress at this choke point could observe movement of boats, goods, and people. For the Zaporozhian Cossacks, who relied on mobility, regional connections, and access to their lower-river bases, such a checkpoint posed a direct challenge.

Military engineer Guillaume Le Vasseur de Beauplan is linked to the original fort's construction on the orders of Crown Grand Hetman Stanisław Koniecpolski. The original 1635 work was a compact earthen redoubt, rather than the larger, more intricate bastioned structure shown on later plans. Surviving drawings and later reconstructions cannot simply be treated as photographs of its first weeks.

1635YEAR OF THE INITIAL FORT
DNIPRORIVER PASSAGE & RAPIDS
SULYMACOSSACK LEADER OF THE ATTACK
1639DATE ASSOCIATED WITH A LATER PLAN
02 / THE ASSAULT

Ivan Sulyma's bold strike.

In August 1635, an expedition led by Cossack commander Ivan Sulyma attacked and destroyed the new Kodak fort. Contemporary and subsequent narratives differ in details, and the precise tactics of the encounter are not recoverable as a reliable minute-by-minute battle plan. The broad event, however, is historically documented: a recently built Commonwealth fort was overwhelmed by Cossacks on the Dnipro frontier.

The victory did not secure Sulyma's future. After the uprising, registered Cossack leaders transferred him to Commonwealth authorities. He was executed in Warsaw later in 1635. The fort was subsequently rebuilt and enlarged, so the fortification visible in later drawings represents a different construction phase.

WHY THE SCENE IS AN INTERPRETATIONThis interactive mission uses fictional detachments, watch routes, weather, and objective sequences. It does not pretend that the exact timing, garrison losses, or assault formation is established from an eyewitness tactical record.
03 / THE SIMULATION

History you can move through.

The simulation combines historical constraints with a transparent alternate-outcomes model. Hundreds of individually moving, instanced figures inhabit a procedurally modeled river valley. A compact earth-and-timber defensive work overlooks boat landings, wagon routes, forest margins, and the lower approach.

Patrols follow watch circuits and react to nearby opponents, visibility, movement pace, and alarms. Cossack squads obey your orders, maintain basic cohesion, advance along waypoints, and contest the gate and courtyard. Simulated morale, reinforcement response, line-of-sight checks, injury attrition, and timed control of objectives determine the outcome. Rain and mist alter visibility and the mood of the environment. A tactical minimap allows a precise destination to be issued without leaving the 3D scene.

These rules are educational abstractions. They illuminate the problems of military movement, surprise, fortification, and river geography without claiming numerical predictive accuracy for a 17th-century battle.

04 / FIELD NOTES

Observe. Decide. Reconsider.

What matters to the historian is not only the outcome, but what the environment makes possible.

01

Earth before stone

The initial Kodak post is represented as a small earthen redoubt with timber revetment and two schematic half-bastions, not a fully developed later star fort.

02

The Dnipro corridor

River bends, rapids-inspired shallows and a high right bank shape approaches, sight lines, and troop routes through an otherwise open frontier landscape.

03

Matchlocks, sabres and coats

Soldiers carry period-inspired early modern firearms, curved blades and layered garments. Individual uniforms and equipment remain artistic approximations.

04

The danger of a night watch

Guard awareness rises through visibility and proximity. Your choices trade surprise against speed, reflecting a general historical military dilemma.

05

A frontier, not an empty map

Camp kitchens, wagons, supply buildings, grazing animals, moving sentries and anchored river craft suggest the daily logistical world behind the conflict.

06

Choices leave traces

Squad movement, the gate, local engagements, alarms, and control of the interior influence a persistent operational state. Restart to test another approach.

05 / USER GUIDE

How to explore Kodak 1635.

  1. Survey the landscape. Drag to orbit; scroll or pinch to zoom. Use the location shortcuts to visit the fort, river, Cossack camp and watch post.
  2. Inspect history. Click an architectural landmark or a unit to open historical notes and see whether its design is verified, approximate or fictional.
  3. Command a detachment. Choose a squad and order it to advance, hold, rush the gate, or withdraw. Shift-click the terrain or tap the tactical map to set a specific destination.
  4. Change the conditions. Adjust moonlight, weather, overlays, render quality and simulation speed. Free-camera mode supports WASD movement; cinematic mode follows a moving path.
  5. Watch the operation evolve. Complete the three tactical objectives or replay the mission. A fictional outcome never changes the actual historical record.
06 / RESEARCH BASIS

Facts, evidence and uncertainty.

The event and basic strategic setting are supported by reference works and institutional research. Details of the first fort's geometry are more contested: a Swedish-archive study warns that a surviving plan attributed to Getkant and Beauplan may represent the rebuilt fortress around 1639 rather than the original structure destroyed in 1635.

The 3D fort's dimensions, exact bank contour, structures, uniforms, characters, timing and AI behavior are speculative. The mission uses neither a modern reservoir landscape nor later 18th-century military technology. The water surface and rapids are artistic visualizations of a pre-dam river corridor.

07 / FREQUENTLY ASKED

Questions from the frontier.

What was Kodak Fortress, and why was it built in 1635?

Kodak was a Commonwealth defensive work near the Dnipro rapids, built to monitor an important corridor between settled territories and Zaporizhzhia. It also aimed to restrict unapproved Cossack movement and expeditions, part of an effort to tighten frontier control.

Did Ivan Sulyma really destroy the fortress?

Yes. Historical reference works record that Cossack forces led by Ivan Sulyma attacked and destroyed the recently constructed fort in August 1635. Our game's precise route, squad assignments, and objectives are fictional because no complete tactical account survives.

Is the 3D fortress an exact archaeological reconstruction?

No. The initial 1635 fort was a relatively small earthwork. Some prominent historical plans show a later or enlarged iteration, and their dating is debated. The model presents a compact, interpretive early redoubt and explicitly avoids presenting its dimensions as settled fact.

What weapons did Ukrainian Cossacks use at this time?

Firearms, sabres, knives, spears and other weapons were used in different settings; Cossack dress and equipment varied by individual and resources. The simulation suggests early-17th-century firearms and layered garments rather than pretending all warriors wore one modern standardized uniform.

Can I win the game differently from what happened historically?

Yes. Tactical outcomes change with patrol awareness, squad choices, troop losses, gate access and courtyard control. This is an alternate-path learning model. The recorded 1635 assault and Sulyma's subsequent fate remain historical facts regardless of what you achieve in the simulation.

FIELD MANUAL

Navigate the frontier

Orbit: left mouse-drag / one-finger drag. Pan: right drag / two fingers. Zoom: wheel / pinch. Inspect: click soldiers or landmarks. Issue a destination: Shift-click terrain or click the minimap.

Free camera: choose World → Free fly, use WASD for ground movement, Q/E to descend/ascend, Shift to move faster, and right-drag to turn. Command: select a squad then choose Advance, Hold, Rush Gate, or Withdraw. Pause: button or Space (when not typing). Fullscreen: stage button.

The mission is not a claim of precise military chronology. The victory and defeat conditions are designed for replayable learning.

Historical context

This is an educational, family-friendly simplification of a historical episode (Kodak 1635). Unit numbers, terrain, timing and outcomes are interpretive; losses appear only as abstract numbers and the game is not an accurate reconstruction. Consult historians and primary sources for the real record.

Made with 🤖 ChatGPT · Three.js