✥THE SIEGEWORKSMY SIMULATOR / HISTORICAL LAB
HISTORICAL EDITION 1649
✥
INITIALISING THE CAMPAIGN
ZBARAZH 1649

Preparing the landscape and historical formations…

CHAPTER 01 JULY–AUGUST 1649

ZBARAZH 1649

THE SIEGEWORKS / A LIVING HISTORY

CAMPAIGN CLOCK
10 JUL 1649
DAY 01 / 48 · DAWN
CAMPAIGN OVERVIEW● LIVE MODEL
Garrison provisions100%
Siege works complete10%
Fortification strength100%
Besieger provisions100%
☀
Clear skiesWind · W 6 km/h
21°
FROM THE FIELD JOURNAL / DAY 01
The ring tightens

The Cossack and Crimean Tatar forces form a siege ring around the Commonwealth's fortified position.

◉ SELECT A UNIT OR STRUCTUREGPU READY
✣
CAMPAIGN CONTROLDECISION LABORATORY
0.25×1×4×
CAMERA / VIEW
ORDERS HYPOTHETICAL OUTCOMES
More sappers build faster but consume more supply.
DISPLAY / CONDITIONS
Awaiting orders from the field command.
THE FORTY-EIGHT DAYS10 JUL — ENCIRCLEMENT
10 JUL21 JUL01 AUG12 AUG26 AUG
AN INTERACTIVE HISTORICAL RECONSTRUCTION · WESTERN UKRAINE, 1649

Forty-eight days of earth, smoke and strategy. Explore how a Cossack army surrounded a fortified camp—and why a siege could be decided far beyond its walls.

EXPLORE THE HISTORY ↘

The Siege of Zbarazh: a summer of fortifications

In the summer of 1649, during the Khmelnytsky Uprising, the Ukrainian Cossack forces of Hetman Bohdan Khmelnytsky and their Crimean Tatar allies confronted a Polish–Lithuanian Commonwealth army defending Zbarazh, in present-day Ternopil Oblast, Ukraine. It became an intense test of siege engineering, supplies, morale and political timing.

PERIODSummer 1649Julian and Gregorian dates differ in some sources
LOCATIONZbarazhHnizna River, western Ukraine
CONFLICTKhmelnytsky UprisingCossack–Commonwealth War

The forces and the stakes

Khmelnytsky's military movement, joined by forces under Crimean Khan Islam III Giray, encircled the Commonwealth troops at a strongly defended position near Zbarazh. The defenders relied on the castle precinct, an entrenched field camp, earth ramparts and successive defensive lines. This simulator depicts distinct Cossack infantry groups, mounted allied forces, Commonwealth defenders, artillery crews, engineers and camp followers—not as exact regimental rosters, but as representative systems.

Earthworks rather than a single charge

Contemporary warfare was shaped by digging as much as fighting. The besieging army worked on approach trenches, embankments and artillery positions while defenders strengthened their own works and sometimes counterattacked. Historical accounts describe repeated assaults, artillery exchanges, and worsening conditions inside the besieged camp. The encircling lines shown here are schematic: the precise placement and appearance of many historical works cannot be recovered with certainty.

Why the siege did not end with a captured fortress

As the siege dragged on, the wider campaign transformed events. Khmelnytsky moved against the army led by King John II Casimir near Zboriv. Negotiations involving the Crimean Khan contributed to the Treaty of Zboriv in August 1649. The siege ended without the Cossack forces taking the Zbarazh fortified position. The model's possible tactical assaults and supply outcomes are therefore explicitly counterfactual experiments, not alternative assertions about what occurred.

HISTORIAN'S NOTE

The simulated clock is a deliberately compressed teaching tool. Troop totals, weather, supplies, losses, fortification damage and event locations are illustrative, not measured historical data. No individual figure on screen represents a verified soldier.

Explore the battlefield as a living system

Unlike a static battlefield panorama, this WebGL2 historical environment responds to changing siege preparations. Animated formations occupy different parts of the landscape. Wagons, tents, earthworks, bastions and artillery illustrate the logistics and geometry of a seventeenth-century encampment. Night lighting, cloud cover, changing wind, smoke and rain affect how the scene looks.

01 / ENGINEERING

Build the siege line

Allocate workers and commission extensions to the siege trenches. Faster progress consumes besieger stores and can improve assault readiness.

02 / ARTILLERY

Exchange fire

Launch batteries with visible ballistic shots and smoke. Battery actions cost powder and affect the modelled fortification strength.

03 / SUPPLY

Strain the camps

Watch both besiegers and defenders consume provisions. Foraging missions can restock the besiegers, with weather-sensitive uncertainty.

04 / COMMAND

Test tactical choices

Order an infantry assault and observe units advance then withdraw. Read the outcome in the field journal, where modeled results are marked as hypothetical.

Five things to notice about Cossack warfare

  1. Fortified wagon camps: mobile wagons could become part of a defensive tabor, especially useful in open country.
  2. Artillery and firearms: firearms, sabres, spears and field guns coexisted in Cossack military practice; tactics were never only sword charges.
  3. Engineering expertise: trenches, earth embankments, mines and assault equipment mattered in siege operations.
  4. Coalition warfare: the Crimean Khanate was a major ally in this campaign. Its mounted forces had their own leadership and political priorities.
  5. Logistical limits: food, ammunition, water, disease and negotiations often determined a siege more decisively than a single assault.

Your field guide

Drag the 3D view to orbit around the fortified camp; scroll to zoom and right-drag to pan. On a touch device use one finger to orbit and two fingers to zoom or pan. Switch to Free camera for WASD movement with Q/E altitude and Shift speed, or use Overview to return to a high survey camera. Select a formation or historical structure to inspect its context. The tactical mini-map is clickable.

Pause the campaign or change the time compression. Move the historical timeline to jump to a particular day and inspect the modeled evolution of the works. Try extending trenches, firing batteries, ordering an assault or dispatching foragers; these commands alter the experimental model rather than historical events. Graphics quality, unit markers and weather effects can be adjusted for your device.

Frequently asked questions

What happened at the Siege of Zbarazh in 1649?

Ukrainian Cossack forces led by Bohdan Khmelnytsky, supported by Crimean Tatar allies, besieged Commonwealth forces defending the Zbarazh fortified position. After weeks of attacks and siege work, the blockade ended in the context of the Treaty of Zboriv, not through the storming of the fortress.

Did Ukrainian Cossacks use trench warfare?

Yes. Alongside field tactics involving infantry, cavalry, artillery and wagons, Cossack forces built trenches, ramparts, gun emplacements and other siege structures. Zbarazh in 1649 is one example of their use of organized siege engineering.

Is this a precise reconstruction of Zbarazh?

No. Terrain, architecture and troop positions are a stylized, plausible educational arrangement, not a surveyed replica. The landscape and architectural language draw on the region and seventeenth-century fortification patterns. Exact uniform colors, placements, losses and daily weather are not known and have not been claimed as fact.

Who fought at Zbarazh?

The principal sides were the Ukrainian Cossack army of Bohdan Khmelnytsky with the allied Crimean Tatar forces of Khan Islam III Giray, and an entrenched army of the Polish–Lithuanian Commonwealth. Different groups in each coalition had distinct interests and responsibilities.

How can I control the 3D siege simulation?

Use the 3D camera with mouse or touch, select objects and formation markers for historical notes, pause or accelerate time, jump along the timeline, and issue hypothetical orders. The visual and numerical results illustrate relationships rather than recreating recorded outcomes.

Further reading & historical sources

Historical framing draws on the Encyclopedia of Ukraine: Zbarazh, the Encyclopedia of History of Ukraine: Zbarazh Siege, and the Encyclopedia of Ukraine: Battle of Zboriv. Interpretations and precise dates differ between historians. See source and reconstruction notes.

Made with 🤖 ChatGPT · Three.js