1. Verdun
  2. News

Verdun News

Save System Update & More

We have a new patch for Verdun and Tannenberg for you today! This will improve the save system and additional connection improvements. You might have heard of the patch to the "opentesting" branch that we did earlier this month. This required all players who wanted to test our changes to the save system, as well as improvements for the connection issues, to opt-in by switching branches.

We really wanted to be sure that there would be no longer term issues, so we are very happy that many of you switched. We received positive feedback, so today we are rolling out the changes to the main versions of Verdun and Tannenberg.

[h3]The update affects two major systems:[/h3]

[h2]Save System[/h2]
If this update works as intended, you should not notice anything. This update is meant to stop the progression loss and progression inflation (suddenly having billions of XP/level/prestige) from happening again.

If you are currently suffering from this "Billions Bug", this might revert your stats to the correct ones, but we can’t guarantee anything. If you have suffered from progression loss (data getting set to an earlier state, or nothing at all), this update will sadly not bring back your stats. We made a rigorous reimplementation of our saving and loading structure so that we hopefully never have these issues again.

In the unlikely case that there are still issues with this, your old data will stay in place for now. This means that you would still have access to your old data if we need to revert anything, so you won't lose all your data by updating.

[h2]Connection issues[/h2]
This should mark an improvement across the board, please let us know if this is better after the update! We don't expect it to be fully solved yet, and again, we have improved our diagnostics, so if you send us your logs we will be able to track the issues more closely. Best case scenario it will make a big difference right off the bat, and otherwise it will give us more information to continue our efforts.

If any of you do experience any issues, please be sure to share your logs with us in the #techsupport channel in our Discord. These will help us address and fix the problems you might come across.

[hr][/hr]
For everyone on the opentesting branch, thank you again for helping us make sure these changes were safe. You can stay on the opentesting branch if you want, but you will have the same version as everyone. We don't plan on keeping it in active use, unless we have something experimental to test.

The Dual Spring Campaign has ended

Hello soldiers!

The Dual Spring Offensive has ended yesterday! The Entente were ahead with almost 40.000 casualties half way through the campaign and at the end these are the end results..
  • Central Powers casualties: 1,402,259
  • Entente casualties: 1,330,804

Once again, the Entente wins another campaign!
Will the Central Powers win the next campaign?



[h2]Isonzo Intel[/h2]

Did you read our latest Isonzo Intel? In our 11th dev blog, we discuss different mortars! We provide you with information of different versions and how they are in the game, combined with in-game footage. Be sure to read it if you havent already!

https://store.steampowered.com/news/app/1556790/view/3109179464630950184



[h3]Until the next campaign soldiers![/h3]

A campaign update, plus a new Isonzo Intel drops!

[h2]Dual Spring Offensive Update[/h2]
In our latest campaign, the Entente are ahead by almost 40,000! Could this be a record? The battle continues until March 27, so there's still time for things to change. Only time (and your actions) will tell...

Read the FAQ for more info!



[h2]New Isonzo Intel![/h2]
A new Isonzo Intel is out, and this time we're talking about mortars! Learn about how the mortars will work in our upcoming game, and take a closer look at the Italian Bettica and the Austro-Hungarian M14![h3]Read the dev blog here![/h3] The unusual Italian Bettica mortar.

Austro-Hungarian M14 mortar firing.

[h3]Wishlist Isonzo now![/h3]

Dual Spring Offensive Campaign begins!

[h2]Spring Offensive - Western Front[/h2]
Michael, Georgette, Gneisenau, Blücher-Yorck - No these are not the names of soldiers or generals, but the codenames of the German offensives during their spring offensive. Also known as the Kaiserschlacht (Emperor Battle) or the Ludendorff Offensive, it was a series of attacks along the Western Front during WW1 in France and Belgium.

Starting on March 21 1918, it was Germany's final attempt to achieve victory by defeating the Allies before the US would arrive as reinforcements. At this point, the German Army had a temporary advantage in numbers with around 50 divisions. These had been freed by the Russian withdrawal with the Treaty of Brest-Litovsk.

Operation Michael. German A7V tank in Roye.

[h2]Dual Spring Offensive in game[/h2]
Our latest campaign event will run until March 27.
All casualties in Frontlines and Maneuver game modes in Verdun and Tannenberg will be added to the total losses, and the winning side will be whoever suffers the least killed and wounded. Too many First World War battles essentially became meatgrinders (or were even conceived as such from the start) and so it is for our campaigns.

Read the FAQ for more info!

Progression Loss & Disconnect Issues Update

Hi everyone!

I'm Thomas, the producer of the WW1 Game Series team. We have a patch for you all that hopefully fixes the progression issues (removed/inflated XP) for Verdun and Tannenberg, as well as a high chance of helping with the disconnect issues. For further investigation we added more logging to provide us with more details on the issue going forward. These changes are experimental so please read the following instructions carefully!

[h2]UPDATING THE GAME[/h2]

To update your game to fix the previously named issues, we updated the opentesting branch for both games. This means that the games won't update automatically, you have to switch yourself. We want to be absolutely sure that our changes for data saving don’t influence your progression, so that's why we treat it like an experimental patch.

How to switch:

  • In Steam, right click the game in your list
  • Press Properties (the lowest option)
  • Navigate to the Betas tab
  • Select opentesting from the list.

This should trigger a small update.

[h2]RISKS[/h2]

When you switch to the opentesting branch, your current progression will not be at risk. However, if something turns out to be wrong with our fixes, you might lose the stats you gathered since switching. We did some internal testing, enough to deem it safe enough to deploy it here, but we never know for sure until we test at scale.

If you switch to the opentesting branch and encounter any disconnection and progression issues, please make sure to:

  • Notify us in our community Discord, find the #techsupport channel. You can share it here on Steam as well, but on Discord things go a lot faster!
  • Include your player.log and player-prev.log (how to find them)

By doing this. you will help us identify and fix the problem easier and quicker!

If all goes well, the fix will be applied as a standard update for the games.

Thank you all and good luck on the battlefield!