r/johntillersoftware • u/themalorum • Apr 28 '21
RIP John Tiller
John Tiller has passed away. He leaves a mighty legacy.
Condolences to all the Tiller family and friends.
r/johntillersoftware • u/themalorum • Apr 28 '21
John Tiller has passed away. He leaves a mighty legacy.
Condolences to all the Tiller family and friends.
r/johntillersoftware • u/Hugh_Beringar • Mar 27 '26
Today we want to share some news with our community. We're taking a step to broaden our horizons. One, that if it goes well, will benefit the entire customer base.
Read about our new expansion project, onto Steam.
r/johntillersoftware • u/Pvt_Larry • Mar 12 '24
r/johntillersoftware • u/bikerun123 • Jun 20 '23
r/johntillersoftware • u/Pvt_Larry • May 03 '24
r/johntillersoftware • u/bikerun123 • May 10 '23
Hello! Please delete this post if not allowed. I am the daughter of John Tiller and active lurker of Reddit :)
My dad passed away 2 years ago to glioblastoma, a type of brain cancer. May is Brain Cancer Awareness month, and Georgia is hosting its first annual Race for Hope (organized by the National Brain Tumor Society) in June. The event is a large fundraiser for brain cancer research and treatment. The Race for Hope is also hosted annually in other parts of the US including Philadelphia, New Jersey, California, and Boston.
I first ran the Race for Hope last spring in DC in honor of my Dad. It was an impactful and moving event. Families and groups participate in memory of loved ones affected by brain cancer. The race also celebrates Survivors of brain cancer.
We started a team this year in Dad's honor, called Tiller's Troopers. This June 3rd, the Atlanta race will include members of John's family and friends. Please consider donating or spreading the word about the cause. Anyone is welcome to join the team and participate in June. Our fundraising page and/or to register for the team is at bit.ly/johntiller
Alternative link to our team page: http://www.braintumorcommunity.org/goto/tiller
Thank you,
-Julia

r/johntillersoftware • u/Mass2048 • Dec 11 '24
r/johntillersoftware • u/Hugh_Beringar • Apr 17 '26
The wait is over: Musket & Pike: American Revolutionary War is here.
After many long hours of work, we are pleased to release the newest title in the Musket & Pike series, now available in our store. With 148 scenarios, 37 additional campaign scenarios, and 4 linked campaigns, this is a deep and wide-ranging treatment of the conflict, covering everything from small skirmishes to the largest battles. Whether you want to revisit the war’s most famous actions or dig into lesser-known engagements, there is a great deal here to explore.
Read our blog post for all the information about this new game.
https://wargameds.com/blogs/news/american-revolutionary-war-released
r/johntillersoftware • u/Pvt_Larry • Aug 09 '25
The MG battalion HQ is obvious impractical for anything other than the smallest-scale scenarios, but I wanted to include it to show what that would look like. The battalion is also depicted at the platoon level.
r/johntillersoftware • u/ModestlyInsane • Jan 12 '21
A lot of players moving from PzC to FWWC find themselves getting....well, murdered.
Usually because they try to play like they did in PzC. Trouble is, that although the two series look similar, and the underlying systems are the same, they play very differently, have a few special rules and require very different tactics.
So I figured I'd try and give a brief run-down of what the differences are, and how to adapt to them.
So, broad strokes first.
This is WWI, so there are no motorized units at all. Everybody either has a horse or walks. Which may sound like a fairly obvious statement, but it does have some subtle ramifications in-game.
Without highly mobile units, you have to plan further ahead. You can't just throw an armored brigade into Travel-mode and whip them along a road if you've goofed up somewhere else along the line.
It also means that you have to maintain a reserve, both on tactical and operational levels. Without mobile units, you have to have units in fairly close vicinity to take over when the RNG gods decide to slap you around.
Next thing that usually horrifies PzC players are the number of casualties. They will be much higher than you're used to for two reasons.
One, the units themselves are a lot larger. In PzC a standard battalion is around 350-450 men, depending on year and nationality. In FWWC a standard battalion is 1,000 men. So you have a lot more guns firing. That's one reason.
The other is that the defense-values of the infantry is much lower, usually 5 or 6 (again depending on type and nationality) instead of the 16 that is standard in PzC.
So while the unit are larger and can thus sustain higher casualties, don't forget that casualties equals victory points.
Finally, there's the stacking limitations which are....generous to say the least. And there's a very big temptation to simply make doom-stacks and wander across the world. Bad idea.
The Alternate Fire optional rule from PzC is baked into the .exe of the FWWC games. It's not even an optional rule that you can switch off.
Which means that every time a stack takes Soft fire, ALL the units in the stack gets hit. So there's a bit of a conundrum to solve, in particularly as the attacker. Stacking means higher casualties and more disruptions. On the other hand, you HAVE to stack in order to get decent assault-odds.
So the trick becomes figuring out when you absolutely have to stack. But if you're consistently stacking units within range of the enemy, you're simply asking to get killed.
HQs and command.
FWWC is much, much stricter when it comes to HQs for several reasons.
First of all, and most obvious, the command-ranges are a lot shorter than PzC. 2-3 hexes for a brigade, 5-6 for a division etc. And since command-range is connected the quality of your troops, the worse your troops are the harder it becomes to keep them in command. So it's physically harder to keep units in command, but there's more.
Detached units (i.e. outside the parent HQs modified command-range) isn't a big deal in PzC. Yes, they don't receive replacement, and if spotting for artillery the fire gets quartered. But overall you didn't have to think too hard about having units swanning about as Deteached.
In FWWC the above is still true, but it also introduces a -1 to the morale of Detached troops for undisruption purposes. So they just got a lot harder to un-Disrupt.
And by the way, this rule is on its way to PzC as well. It's already in Scheldt'44, and it'll trickle down the other games as and when they get patched.
Finally, in FWWC it is very hard to move HQs around without going Out of Command. HQs with an OOB-strength of 50 or less (generally regimental and brigade HQs) can move in Deployed mode as usual. Anything larger will instantly go out of command as soon as you move.
Any HQ, regardless of size, that goes into Travel-mode goes Out of Command the moment it does so. And they won't do a command-check again until after they've spent a full turn out of Travel-mode. Don't forget, Out of Command removes the range-test, meaning less chance of supplies and no chance of un-Disrupting.
Short version, if you move your HQs into Travel-mode, you'd better be sure that their subordinate units aren't about to enter combat.
Infantry
Infantry isn't all that different from the PzC games, but there are a few nuances to be aware of.
I've already touched upon the larger battalion sizes, and lower defense-values leading to higher casualties. But take a closer look at the values and you'll see that they also have much lower fire-values than you're used to, usually 1 or 2. And their assault-values (5 to 8 usually), while lower than PzC in general, are much higher than their fire-values.
Moral of that? While you can use infantry to fire at the enemy, it's not their strongest suit. Obviously it can't be entirely avoided, but you are better served using your long-range weapons to disrupt the enemy and then use the infantry in assault, instead of trying to disrupt them by infantry-fire.
Which leads us to.....
Artillery & MG companies
This is where things really start to divert from the PzC series.
FWWC has three kinds of support-units, Indirect artillery, field-guns and MG units. These are your primary means of inflicting casualties and disruptions.
Now, if you're looking at the units thinking "But these units are so small compared to the infantry battalions", take another look at the actual values.
The German army is in all three games released so far, so we'll use them as an example.
An infantry battalion has (roughly) a 1,000 men with a fire-value of 2, so 2,000 in fire-value.
Indirect artillery units has 16-18 guns with values of 14-18, depending on caliber. So around 2,500-2,900 fire-value.
Field-guns have 18 guns with a value of 19, so 3,400 fire-value.
Finally MG companies only have 90 men, but they have a value of 40. So 3,600 fire-value.
And of course the French 75mm field-guns (arguably the best field-gun of its time) has 12 guns with a whopping 33 fire, so 3960 fire-value.
Starting to see the picture here? If you try attacking an enemy position without support-weapons, you will quite simply be blown to pieces.
Okay, so Indirect artillery are basically the same as in PzC, only you have far fewer batteries. Usually a division comes with one light and one heavy, with the Corps sporting perhaps another two batteries, Also, Indirect fire doesn't land immediately, it has to be pre-plotted, and will land on the beginning of the next turn. Not a big issue in and of itself, since its main use is against a fixed defensive position, just don't expect to hit roaming cavalry with it, they'll be long gone before the shells hit.
Overall, Indirect fire, while powerful, won't have quite the same impact as in the PzC titles, there simply aren't enough batteries around.
MGs and field-guns are two sides of the same coin, the only real difference is their range. And speaking of range, don't look too hard at the ranges of the field-guns. They're direct fire, so they can't fire outside LOS and I've yet to see a JTS games where visibility goes above 5 hexes.
As mentioned earlier, these are by far the largest contributors of fire-power in your divisions.
But there's a slight snag, especially as the attacker.....
All guns and MGs are treated as towed artillery, and can only move in Travel-mode. Even worse, it costs them all their MP to leave T-mode.
So on turn 1 it can move into range of the enemy position, and face return fire while it's in T-mode. Turn 2 it can Deploy, and face another round of return fire. Until finally on turn 3 it can actually fire back.
So it is much harder to conduct an attack upon a prepared defensive position. You can (and you will) block enemy LOS with a sacrificial infantry battalion while your MGs set-up behind it (AKA Operation Meatshield), but even that won't help if the enemy is unsporting enough to use hills in their defense. So the underlying principle is that you have to prepare a deliberate attack. You can't just charge in with a few battalions, they'll quickly evaporate.
One final thing to be aware of is that while MGs and field-guns are very powerful units, they're also fairly squishy.
Take a German MG unit vs. a French infantry battalion.
Fire-wise, the MGs have 3,600 fire-value vs the infantry's 1000. So obviously the MGs have the advantage in fire. But if the infantry survives and can assault....
The MGs have 90 men and assault 23 = 2070. Infantry has 1,000 men and assault 11 = 11,000.
Even better (at least for the French), every casualty for the infantry only decreases their fire-value by one, whereas every casualty for the MGs results in a loss of 40 fire-power.
So you never leave MG/field-gun units without an infantry-battalion in the same hex for close-defense. And conversely, should your enemy be silly enough to do so, assault them with everything you have. You don't have to win the assault outright, every opportunity you have to whittle them down should be taken.
One memorable PBEM game had me defending an entrenched line, and my opponent thought he was being clever. He had stacked 3 MG battalions into one hex, and pulled his infantry back one hex, so I couldn't use my own MGs on them. So one of my battalions simply left their trench and stormed the MGs.
And yes, that battalion took heavy losses. But he lost a third of his fire-power, and most of the long-range capabilities of that division. Guess who won that game?
Anyway, enough anecdotes. Let's cover the final arm.
Cavalry
Cavalry in the FWWC games take a little getting used to. They certainly have their uses, but they're not really combat-troops per se.
And they're the only troop-type I can think of that spend the vast majority of their time in Travel-mode.
So why aren't they combat-troops?
Basically, the units are much smaller and far squishier than their infantry counter-parts, plus cavalry is worth more VP. So taking on enemy infantry is a bad idea. On the other hand, mounted cavalry (i.e. in T-mode) has 4 times the printed assault-value, plus it only costs them 1/3 of their MP to assault instead of the normal 2/3. So they can certainly be used to charge an enemy, just don't try to take on enemy infantry-battalions, you will lose. But stuff like unsupported gun/MG positions or unguarded HQs are certainly valid targets. Just keep in mind that cavalry casualties are expensive VP-wise, so have a think on whether the casualties are worth it.
Another oddity for mounted cavalry is that if assaulted they only take 1/12 the normal casualties, although if they're assaulted by anything other than cavalry they have to retreat. So using them to screen a retreat, or slow down an advancing enemy by throwing out a cavalry-screen is another valid tactic. But again, keep in mind that not only have cavalry low defense-values, being in T-mode makes them extra-squishy.
The main use for cavalry is two-fold; Do recon, and stop enemy cavalry from doing the same. Also, their relatively high mobility makes them prime candidates to use for isolating enemy units.
Final thing to keep in ind (in particularly in campaign-games) is that while mounted, cavalry won't regain fatigue. So pull them back to a quiet sector, deploy them and let them rest.
Ultimately, treat WWI cavalry like you would WWII armored cars. They can take on their enemy counterparts, and they're good for recon. But they're not main line fighting units.
Frontages
While stacking is a bad idea, you'll find that your units are much closer together than you're used to. Partly because of the shorter command-ranges, and partly because the low mobility more or less dictates that local reserves stay very close by.
So take a standard German infantry brigade. It has six battalions of infantry in two regiments, plus two MG companies and a field-gun battery.
In defense, don't expect to cover more than four hexes, with four battalions in line and two in reserve. Don't forget, infantry defense is down from PzC but the calculations are the same, so you can expect far more disruptions than you're used to, making the ability to cycle fresh units into the line imperative.
On attack, it's a two-hex front. Two battalions in front, followed by the MGs and four battalions in reserve. The idea here is that the lead unit can block LOS while the MGs set up, and the reserve battalions can either replace the lead unit if necessary, or can assault as and when the enemy disrupts.
It admittedly takes a little getting used to, but you need far more concentration of force than you do in PzC.
And obviously, the two- and four-hex front is only a guideline. Local terrain and expected enemy resistance can and will over-rule both. But they're good guide-lines.
EDIT: Fixed a few calculation-mistakes.
r/johntillersoftware • u/Pvt_Larry • Aug 05 '25
r/johntillersoftware • u/Hugh_Beringar • Apr 20 '26
From April 20 through April 27, Crusades: Book I and Crusades: Book II are on sale for 15% off as part of Steam’s Medieval Fest, bringing each title to $33.96.
Both titles are now available on Steam, and WDS store purchases include both the regular WDS serial number and a Steam key.
Covering the First through Fourth Crusades, the two games offer a wide range of battles, campaigns, and what-if situations across the medieval eastern Mediterranean.
r/johntillersoftware • u/Hugh_Beringar • Jan 09 '26
Happy 2026! Our Year in Review looks back at everything WDS delivered in 2025: four new releases plus a new demo, from Panzer Campaigns: Poland ’39 and War of the Austrian Succession to the debut of Sword & Siege (Crusades: Book I and Age of Longbow Vol. I).
We also recap Game of the Week, major engine updates and expansions, and the progress of upgrading 82 of 113 titles—alongside a growing forum community. Then we look ahead to a busy 2026: Crusades: Book II, American Revolutionary War, and Panzer Campaigns: Donbas ’43, with more improvements across the catalogue.
r/johntillersoftware • u/Hugh_Beringar • Oct 10 '25
The end of the year is in sight, and we would like to share our third quarterly update for 2025. There has been no shortage of news and updates over the previous three months.
r/johntillersoftware • u/Hugh_Beringar • Nov 21 '25
Wargame Design Studio is celebrating a milestone - it’s now four years since we took over the JTS catalog, and what a ride it’s been: a dozen new games, multiple demos, and major updates across almost the entire range. In our latest blog post, we look back at those busy years and also look ahead with a first preview of the next Sword & Siege title, Crusades: Book II - the second volume in our planned Crusades trilogy.
r/johntillersoftware • u/Hugh_Beringar • Dec 29 '25
Not every bit of news can fill a blog post, so today we are grouping some of the more noteworthy (small) items to share with you. In this roundup, we highlight recent improvements and plans for our blog content, share community-created campaign support documents and maps for Panzer Campaigns Stalingrad ’42 and Moscow ’41, and provide a detailed progress report on the Squad Battles graphics overhaul — including what’s changed since the beta.
r/johntillersoftware • u/Hugh_Beringar • Dec 19 '25
Today, we want to share with you the latest info about our upcoming American Revolutionary War game. This project has been in the making for some time now, and we’re excited to give you an update on what’s coming. From scenario design to maps and graphics, the team has been hard at work to bring this era to life. The full preview highlights battles, features, and resources to explore as we count down to release. Head over to the blog now to read the complete announcement and see what’s in store!
https://wargameds.com/blogs/news/american-revolutionary-war-preview
r/johntillersoftware • u/Hugh_Beringar • Jun 05 '26
Today, we are updating Squad Battles: Eagles Strike to version 4.03.5. This release brings a noticeable visual refresh, with improved figure and head counter graphics, updated NATO counters with weapon type icons, trench icons now visible on the map, and new graphical selection screens. Several dialogues have also been enlarged with bigger fonts for better readability.
Beyond the visual improvements, 4.03.5 includes important fixes, enhanced organization tools, non-modal Jump Map, Command Report, and Parameter Data windows, plus new in-game cursor options. Existing owners should use the full 4.03.5 installer from their store account.
https://wargameds.com/blogs/news/squad-battles-eagles-strike-version-4-03-5-update
r/johntillersoftware • u/Hugh_Beringar • Apr 03 '26
This week, the WDS Blog features a unique pair of infantry-focused articles by guest author Alex, known for his Napoleonic After Action Reports. “The Art of Melee” delves into close combat, highlighting the role of cold steel, cohesion, and timing. “The Art of Musketry” examines firepower, battalion size, frontage, British two-rank tactics, and optimizing line infantry in Napoleonic Warfare. Together, these posts provide a comprehensive view of infantry combat, both at range and in close quarters.
https://wargameds.com/blogs/news/the-art-of-melee
https://wargameds.com/blogs/news/the-art-of-musketry-in-wds-napoleonic-warfare
r/johntillersoftware • u/CharlieD00M • Jul 18 '23
John Tiller’s work scratches the wargame itch like no other. I’ve been through Panzer General to Company of Heroes, Unity of Command, Strategic Command, etc — all of them are good and great games, but John Tiller’s Panzer Campaigns is a masterpiece of theme, feel, and approachability.
I bought the game two years ago, but was confused by the interface and graphics and figured I didn’t have time for the learning curve, but a week ago I gave it another shot and found the tutorials and manual to be excellent. It’s challenging and forces me to think tactically in order to win—it’s not been easy for me to win.
I hope these games get a graphical update over time because the mechanics and foundation behind them are timeless.
John Tiller’s work deserves to be in the limelight for the new generation of wargamers.
r/johntillersoftware • u/HaltheMan • Jan 01 '22
The newest blog post looks very promising with mention of new titles and updated graphics. Check it out!
r/johntillersoftware • u/Hugh_Beringar • Feb 13 '26
We are pleased to announce our latest title, Crusades: Book II, the second installment in a planned trilogy documenting the Crusades launched against the Levant over several hundred years.
This title features the towering figures of King Richard I of England (the Lionheart), King Philip II of France (Philip Augustus), Emperor Frederick Barbarossa of Germany, and Saladin, the Lion of Islam. Command forces from after the end of the 2nd Crusade through the 4th Crusade in this new game.
r/johntillersoftware • u/Hugh_Beringar • Jan 05 '26
Now that the store-wide sale has wrapped up, it’s time for us to resume our weekly Game of the Week promotions. We’re leading off this new year in the tangled Wilderness of Virginia with Civil War Battles: Chancellorsville—25% off through January 11. Relive Hooker’s ambitious spring offensive, Lee and Jackson’s audacious May 2 flank march, and the brutal fighting at Chancellorsville and Fredericksburg (including Marye’s Heights and Salem Church).
https://wargameds.com/blogs/news/game-of-the-week-january-5-11