The Monthly Metrics : December 2015

As many of you know I have been asking Barbarossa players to switch on the metrics switch so we can have a better idea how hard the game is for the average player.

In this first Monthly Metrics post I’d like to share a comparison of the German player Victory Points in v1.00 and v1.01.

On the y-axis the number of VP, on the x-axis the number of rounds played. Click to mega-enlarge:
metric15dec_small

In my personal opinion the Germans should try to really have around 55 VP at round 10-ish. And than add around 10-15 VP’s per 10 round untill the grand finale arrives. The grand finale is at around a 100 VP’s. At that point the Germans are on the verge of victory.

Taking into account the quite large number of German players with relatively low VP progress abandoning the current game, or restarting it, I have to say it seems like the difficulty level for the average player is just about right.

I am happy to see that judging from the current data the AI in v1.01 seems to better hold itself against some extremely aggressive German players (note the 4 early victories before or around round 30 in the red lines)

Of course I ran more analytics on the data. And I can also say it is quite astonishing to me that almost everybody is playing at the lowest difficulty setting. Me and Cameron put quite a lot of thought and balancing work in getting the ‘challenging’ and ‘hard’ levels right without overloading the AI with combat bonuses, but so far play of ‘challenging’ seems to be absolutely minimal. Guess We’ll probably have to take it as a compliment.

Also I can share that the ratio of German players versus Soviet players seems in the order of at least 5 to 1.

Next month I’ll highlight something different in the Monthly Metric! Hope you enjoyed that we shared a bit of insights here.

Best wishes,
Vic

Posted in DC:Barbarossa | 1 Comment

Decisive Campaigns : Community Project now available!

Community ProjectIf you own DC:Barbarossa you can now participate in the semi-open BETA of DC:Community Project. The Community Project is a separate game that uses the same engine but is configured to make scenario construction as easy as possible.

Why a separate game?

First of all because we want to be able to eventually share the Community Project with owners of different (and future) versions of our DC games.

One big problem we noticed with series and editors is that the scenarios created have a tendency to become obsolete after the newest game in the series is released. By giving the Community Project a decent subset of features from all new releases and keeping it available to old and new players we should be able to provide a long life-time for any scenario design efforts by the community.

Secondly it helps psychologically for players to understand that the Community Project (default rules) are different from DC:Barbarossa. The default rules of the Community Project are more similar to DC2 and are relatively void of any chrome. In many ways the default setup is for a straight-forward counter-pusher.

That being said the Community Project does come with official libraries that allow you to set for example the weather, victory conditions, political point income, reinforcement and replacement cards and more.

What can I make with it?

The Ardennes offensive, Kursk, the Korean war, Africa, Sicily, world war 1 scenarios… In many ways your imagination is the limitation.

The default rules give you a big amount of landscape types (ranging from jungle to desert) and the rules will work well with any unit scale chosen between divisional and regimental. Though you might get a way with battalion or corps level units as well. Length of turns can be anywhere between 1 turn/day to 1 turn/week or more. My recommendation is to stick to 5km per hex/1 day a turn or 10km per hex/2 day a turn.

You can create trooptype libraries and historical unit libraries (TOEs) for any nation you want. As well as making officer libraries and drawing maps from scratch.

The modular setup ensures that when at a future moment we’ll provide additional chrome-by-event you can easily add it in to your scenario. And your scenario will be available to players of newer games as well.

For the hardcore “modder” it is even possible to create your own event libraries that can directly tap in to over 500 execute- and check- functions that the engine’s scripting system supports.

Where to get it?

To download the Community Project you’ll need to register and login to the scenario bank. To consult the documentation visit the community project wiki pages.

Posted in Uncategorized | 1 Comment

Barbarossa Developer Notes #10: The Low Down

Information

How information is presented is a big, topical, subject. A game can live and die by it’s ability to provide adequate feedback to the Player. Game mechanics that chug away in an information vacuum are no fun for anybody. If there is something going on you want to know why and how.

Being presented solely with the outcome is like finding yourself married to a woman whose personality changes every day. She’s still you wife, you’re still married, but why she keeps morphing into a different woman is a mystery. One day she fawns over your dog, the next she informs you that Chuckles the Chihuahua has left, in dubious company, to start a career in the restaurant trade.

blog_30

The amount of information that needs to be presented to the Player is proportional to the complexity of the game. For Pacman a score and a timer readout constitute adequate feedback. For DC3: Barbarossa, with it’s multitude of game mechanics, there is a dump truck’s worth of information that needs to be thrown at the Player each turn in order to convey what is going on.

Straight up there is a problem. Information overload. Drowning under an excess of data is a feeling that we all familiar with, one way or another. Nobody wishes to replicate the experience in a game. The information needs to be presented in an easily digestible format.

The primary way the game tackles this is by making the information optional. There are, if you’re playing the German side, dozens of reports available in the report tab each turn. Do you need to read each and everyone of them in order to play the game? No. You can, in fact, ignore them all.

Delegate all decisions and fill your virtual wastebasket up to the brim. Of course there will be a train wreck at some point. You’ll lose the game. Probably get slaughtered. But not immediately. Importantly the game will keep ticking over without any input from the Player. If all you want to do is shuffle counters across the map then you can do this. For a while. Until your fast Divisions run out of fuel and a number of other, cascading, disasters catch up with you.

The game is about Operational Command and it assumes that you are going to at least make an effort to stay on top of what is going on. It also assumes that you’ll make a few decisions and read a few reports. But only a few. The rest are there to be dipped into at your leisure. The degree at which you choose to do that is up to you.

Which fits in nicely with the Operational vibe of the game. You’ve got a pile of reports on your desk. You can read the ‘need to know’ stuff and wing all the rest. Or you can be the one of those Commanders who are regarded as ‘on top of their brief’. Up to you.

Which of the two archetypes would you consider to be the better Operational Commander? Probably the second. I say ‘probably’ because Mr ‘I-don’t-fight-the-war-from-behind-a-desk’ might have other, equally valid, ways that enable him to keep his finger on the pulse. Which he would need to because there is no way to dodge around the fact that he would have to be on top of what is going on before he could make informed decisions. Does this mean that you’ve got to brew up a cup of stiff coffee and wade through endless reports each and every turn? No.

Information is presented in multiple ways and in multiple formats. You can access it textually or visually, or both. The game goes out of its way to provide you with different information channels and allows you to pick the one the suits. It also layers the information. Get the big picture and then peel away, Shrek-like, for further details.

Is it perfect? Nope. But the design has made a big effort to provide ample feedback, in a streamlined manner. Here’s how it is done.

Lets start with reports. There are a heap of them. Most of them are contextual. You would reference them only if you wanted specific information, the headquarters equivalent of asking your staff to provide a detailed breakdown on such and such.

The core, important, reports are the Daily Logs. They contain all the goings on in one place. If something has happened in the game, at a level that you need to be aware of, then it’ll show up in the appropriate Daily Log. They are divided into topics but, once the campaign gets underway, there can be a lot of stuff in there.

To provide a quick reference filter for the really important, need to know information there is the Aide de Camp which is essentially a distillation of all the major Daily Logs into a single, heavily condensed, report showing only the vital stuff. It’ll serve to give you a gentle prod if you’ve forgotten to tell the Luftwaffe what to do, for example, or have Theatre Artillery assets sitting around, twiddling their thumbs.

Tool tips. They are like rabbits in a breeding frenzy. Everywhere you look there is a tool tip. Pregnant and about to drop another litter of little tool tips. A lot of them are static. They provide the same information every time you read them. They are the dull neighbours or the boring in-laws type of rabbits.

But lots of others are dynamic. They are hopping around faster than a rabbit has a right too. They are the exciting, razzle dazzle, rabbits. The Matrix versions. Their little bunny brains neurally shunted directly into the virtual construct, constantly updating.

Report Status! Originally this was an Action Card but it received pride of place as a special button. It’s not happy if you aren’t pressing it. Everything you need to know about a Division or an Army is right there. With tool tips.

If you’re playing the Soviets you may find that the cogs of Command grind to halt at unexpected times. But that’s life in the Red Army. The rabbits and buttons are all on tranquillisers. As are the channels of communications that feed STAVKA with reports from the front lines. If your playing Stalin you might want to give your entire Command Structure a decent shake. Wake everybody up. Unclog the blockages. Have all the dopey ones who haven’t snapped to attention taken out back and shot.

Where ever applicable, Action Cards have dynamic text that updates after being played. If you want F.M Von Leeb, up North, to change his focus you’ll be able to see who currently has it before issuing new orders.

Status icons adorn the Unit displays to indicate various conditions. Logistical icons march across the map enabling you to accurately ascertain the state of your logistics purely from their colours, without the need to read a single report.

A comprehensive mouse-over is available for every hex with dynamic information on movement costs and combat. Small icons adorn the map letting you know of any additional, non-standard movement costs as a result of recent combat, or ZOC’s, for example.

Then there are the Special tabs down the bottom. Three for each regime. All of them aimed at a particular aspect of the game. All of them with extensive dynamic tool tips that serve to condense most of the information contained within the numerous related reports. One stop information shops.

Cheers,
Cameron

 

Posted in DC:Barbarossa, Game Design | Leave a comment

Decisive Campaigns : Barbarossa is released!

DC:Barbarossa is now for sale over at Matrix Games.

Click here for more information.

Posted in DC:Barbarossa | 2 Comments