THE DNIPRO GATEHISTORICAL EXPERIENCE / 001 ENTER 1635
VOL. I / THE DNIPRO FRONTIERSUMMER, 163548° / THE LOWER RAPIDS
AN INTERACTIVE HISTORICAL RECONSTRUCTION

THE DNIPRO
GATE.

Kodak Fortress, 1635. A new stronghold rises above the rapids. A Cossack flotilla returns. The river is about to change hands.

01THE FORTRESS
1635THE YEAR
4BASTION FRONTS
An evidence-led reconstruction.
Not a literal record of the assault.
01 / ENTER THE FRONTIERLIVE HISTORICAL SIMULATIONWEBGL 2.0
KODAK / 1635THE APPROACH TO THE FORTRESS
SEED 532610
SCENARIO ACTIVEPHASE I / RECONNAISSANCE
✳
05:30 · DAWN
CLEAR SKIES · WIND 8 KT
CURRENT OBJECTIVEScout the unfinished approachesProtect the Cossack landing
✣
THE DNIPRO GATEPreparing the frontier
Building terrain & fortifications
00:00SIMULATED TIME
NEXT: LANDING BEGINS
SPEED
BATTLE INTELLIGENCE / LIVE

The river is contested.

Sulyma's detachment approaches the fortress. Its earthworks guard the route to the rapids.

K / 35
COSSACK STRENGTH—Field combatants
GARRISON STRENGTH—Fort defenders
FORT INTEGRITY100%Earthworks & gate
HOST MORALE—Will to fight
CAMPAIGN CHRONICLE SIMULATED EVENTS
    FIELD CARTOGRAPHY
    COSSACKSGARRISONDNIPRO

    Interpretation notice. The 1635 assault and named historical figures are documented; troop totals, battle positions, exact fort dimensions, minute-by-minute tactics, and victory conditions are illustrative game mechanics. This is not an archaeological-grade replica.

    02 / THE HISTORICAL RECORDTHE GREAT DNIPRO RIVER / UKRAINE
    WHY THIS MOMENT MATTERS

    A fortress built
    to command a river.

    The Dnipro was more than a waterway. Its rapids marked a strategic gateway between the settled lands farther north and the Zaporizhian Cossacks' southern frontier. In the summer of 1635, the Polish–Lithuanian Commonwealth constructed Kodak Fortress near the rapids to supervise movement and strengthen its authority on the lower river.

    The French military engineer Guillaume Le Vasseur de Beauplan designed the early fortress, whose garrison was commanded by the French officer Jean de Marion. Soon after it was built, an expedition under the Cossack leader Ivan Sulyma captured Kodak and destroyed its defenses. This dramatic clash foreshadowed longer struggles over jurisdiction, military autonomy, and the southern frontier.

    01 / LOCATION

    The Kodak Rapids

    Kodak stood above the Dnipro's rapids in present-day Ukraine, a natural chokepoint where navigation, trade, and military movement were difficult to separate.

    02 / CONSTRUCTION

    A new earthwork fort

    The first fortress was built rapidly in July 1635. In this scene, angular earth-and-timber ramparts evoke early modern bastion design without claiming a proven 1635 footprint.

    03 / THE ASSAULT

    Sulyma's strike

    In August 1635, Zaporizhian forces led by Ivan Sulyma seized Kodak in a surprise attack. The defenders were defeated, and the fortification was destroyed.

    04 / AFTERMATH

    Not the end of Kodak

    Sulyma was later arrested and executed in Warsaw. The Commonwealth subsequently rebuilt and enlarged the fortress, meaning many later drawings do not necessarily depict its first form.

    03 / THE SIMULATION MODEL

    Not just a view.
    A living frontier.

    The world changes under your command. The model translates a documented historical confrontation into an explicitly fictionalized tactical sandbox.

    ⚑

    Troops with orders

    Six Cossack detachments move in formations, obey advance, hold, flank, or coordinated-volley instructions, and lose cohesion as morale and numbers fall.

    ✦

    Garrison & defense

    The fortress reacts with simulated musket fire, artillery, defensive strength, gate damage, losses, and changing territorial control.

    ≋

    River movement

    Procedural boats traverse the Dnipro and discharge simulated landing parties; reeds, waving standards, water highlights, and trees respond to wind.

    ◐

    World conditions

    Control sunlight from dawn to nightfall, toggle mist or rainfall, vary wind, and adjust rendering quality for desktop or mobile performance.

    04 / FIELD GUIDE

    Your command.
    Your perspective.

    Every command changes the running model. Set a detachment to flank, advance the clock, inspect the fortifications, and read the campaign chronicle as it unfolds.

    01
    NAVIGATE THE LANDSCAPE

    Drag to orbit, scroll or pinch to zoom, and right-drag to pan. Choose FREE for WASD movement with Q/E altitude and drag-to-look; choose FORT, ARMY, or RIVER for cinematic focus points.

    02
    ORDER A DETACHMENT

    Select a Cossack unit in the command panel or by clicking one of its soldiers in the world. Issue advance, flank, hold, or volley orders; monitor operational responses.

    03
    CHANGE THE CONDITIONS

    Pause, reset, change simulation speed, shift the sun, select clear weather, river mist, or rain, and adjust the wind and command initiative.

    04
    FOLLOW THE CHRONICLE

    The timed campaign ledger records the advance, landings, defense, and outcome. The tactical map and historical object card update while the simulation runs.

    05 / WHAT IS DOCUMENTED?

    History and
    hypothesis.

    We distinguish evidence from interpretation rather than pretending a modern computer can replay an unrecorded minute of 1635.

    DOCUMENTED

    The construction of Kodak in 1635, its location near the rapids, Beauplan's involvement, its attack by Sulyma's Cossacks, and its later reconstruction.

    DOCUMENTED

    Seventeenth-century Cossack familiarity with firearms, sabres, boats, and garments such as shirts, trousers, and coats; material culture varied by rank and means.

    INTERPRETIVE

    Specific rampart layout, troop deployment, numbers on the field, village location, boat timing, uniforms, ammunition and damage calculations.

    INTERPRETIVE

    Alternative outcomes, commander decisions, loss curves, dynamic weather, and mission objectives; these are educational what-if systems.

    06 / QUESTIONS FROM THE FRONTIER

    The field
    questions.

    What was Kodak Fortress, and why was it built?+

    Kodak was a new Polish–Lithuanian Commonwealth fortification built in 1635 above the Dnipro rapids. It helped the Commonwealth monitor river traffic and limit the autonomous activities of Zaporizhian Cossacks on the southern frontier.

    Who was Ivan Sulyma?+

    Ivan Sulyma was a Zaporizhian Cossack leader remembered for commanding the successful assault on Kodak Fortress in August 1635. He was subsequently seized and executed in Warsaw.

    Is the 3D fortress an exact reconstruction?+

    No. The scene represents early modern earthen bastions, a timber-defended compound, and the Dnipro high bank. Surviving plans associated with Kodak are not conclusive blueprints of the original, rapidly built 1635 fort. Dimensions, interior buildings, and tactical layouts are intentionally interpretive.

    Can I change the historical outcome?+

    Yes. The interactive siege system can generate different tactical outcomes based on your orders, weather, initiative, and the performance of both sides. These are counterfactual simulation results, not assertions about what happened in 1635.

    Does this Ukrainian Cossack simulator work on mobile?+

    Yes, on current mobile browsers with WebGL2 and sufficient graphics memory. Touch to rotate and pinch to zoom. The renderer automatically limits graphics quality on constrained devices, and a manual quality selector is provided.

    FIELD CONTROLS

    Orbit camera

    Left-drag: orbit around the scene
    Right-drag: pan
    Wheel or pinch: zoom
    Click: inspect a location or unit

    Free camera

    W A S D: move
    Q / E: down / up
    Shift: move faster
    Drag: look around

    Simulation

    Space: pause/resume
    1 / 2 / 3 / 4: simulation speed
    M: show/hide minimap
    R: reset campaign

    Troop counts, losses, fort effects and tactical outcomes are modeled, not documented historical measurements.

    Historical context

    This is an educational, family-friendly simplification of a historical episode (Kodak Fortress 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