A frontier landscape
Travel across procedural river bluffs, meadows, river islands, groves, fields, and the churning Kodak rapid. Terrain altitude affects sightlines and movement.
This experience requires WebGL2 and a current browser with hardware acceleration. The historical article below remains available.
In 1635, the Polish-Lithuanian Commonwealth established Kodak Fortress above a dangerous rapid of the Dnipro. The stronghold was designed to check the movement of Zaporizhian Cossacks into the lower riverlands—and toward the Black Sea.
The Cossacks were not simply irregular soldiers. They were an evolving military and political community rooted in the frontier of the Dnipro, with traditions of river navigation, raids, military councils, and fiercely negotiated privileges. Kodak placed an armed garrison at a crucial point on their route.
That same year, Ivan Sulyma led Cossacks against the new fortress, captured it, and destroyed the works. His success was temporary. Some registered Cossacks later handed Sulyma over to Commonwealth authorities, and he was executed in Warsaw in December 1635. The fortress would subsequently be rebuilt.
Travel across procedural river bluffs, meadows, river islands, groves, fields, and the churning Kodak rapid. Terrain altitude affects sightlines and movement.
Inspect earthworks, timber palisades, defensive bastions, watch posts, guns, and camp structures. The fort’s plan is schematic, not an exact 1635 survey.
Hundreds of individually updated Cossack and garrison agents move in companies, reorganize at objectives, exchange fire, and respond to morale, losses, and orders.
Use scouts, boats, field artillery, a reserve, volleys, and regroup orders. Supplies, powder, intelligence, defense strength, and both sides’ morale evolve over time.
The simulation begins in reconnaissance. The clock advances and autonomous life continues. Launch the assault to begin the crossing and contested engagement.
Drag to orbit, use the wheel or pinch to zoom, choose camera presets, and click forts, boats, towers, or military units for explanations. Click the minimap to relocate the camera target.
Select the western gate or one of two rampart sectors, then begin the assault. Companies advance using formation offsets and seek the chosen objective.
Scout to raise intelligence, redirect the chaikas, expend powder on volleys and field cannon, commit the reserve, or regroup when morale falters.
Set the time rate, pause, change atmospheric conditions, toggle attack-route overlays, switch between orbit and WASD free-flight, and reset the entire scenario.
Kodak was established in 1635 as a barrier on the Dnipro; Sulyma’s Cossacks captured and destroyed it; the frontier was contested between Cossack autonomy and Commonwealth control.
The exact 1635 fort plan, assault routes, company strengths, weather, initial troop positions, riverboats at the assault, battle timetable, detailed combat results, and village layout are game-model conjecture. Later plans cannot simply be projected onto the first fort.
This is an educational simulation—not a claim to recreate a fully documented battlefield. The scenario uses an intentionally abstract loss model and avoids presenting its invented sequence as historical fact.
Ivan Sulyma led a force of Zaporizhian Cossacks that captured and demolished the new Commonwealth fortress. This was part of a wider struggle over Cossack military activity and autonomy.
It was intended to control movement on the Dnipro near the first major rapid, particularly Cossack traffic to the lower riverlands and Black Sea. The site had substantial tactical value.
No. The place, broad motivations, and historical event are documented. Exact tactical dispositions and the first fortress’s detailed plan remain uncertain; game systems are openly interpretive.
Ivan Sulyma was a Cossack military leader associated with campaigns against Ottoman domains. After the capture of Kodak, he was surrendered to Commonwealth officials and executed in Warsaw in 1635.
Yes. You can remain in reconnaissance, pause the simulation, inspect structures and troop groups, explore the geography, and alter weather and lighting before choosing to fight.
Historical references guide this project’s dates, names, military setting, and caution about ambiguous plans. All rendered visuals and code are original procedural work; no reference imagery is redistributed.