Let's Play Batman Arkham Origins Walkthrough Part-2- Penguin's Dealer [1...

Visit By Head Of Games Design At TT-Games - Arthur Parsons

We are very lucky to welcome Arthur Parsons to our Games Design studio at UCLan this week.
Arthur is Head of Games Design at TT_Games and as such, it's so amazing that he takes time to visit our course and speak directly and openly with our students.
Arthur gave a great presentation about the criteria involved in designing and making a Lego game and offering a broad insight into the workings of the industry in terms of producing and marketing a game.
It's great to have the chance to speak with experienced industry experts such as Arthur.
His warmth and enthusiasm always motivate our students so much and encourage them to work hard and develop their passion for games design.

 

Slowly Getting Back To 'Normal'

A bit of painting, a quick solo game, aced the Beef and Broccoli for supper, Hornblower: The Duchess and the Devil with my closest canine friends.......that's  retirement!

GTA 4 ULTRA HIGHLY COMPRESSED

GTA 4 ULTRA HIGHLY COMPRESSED

===============================================

How To Install GTA 4 ULTRA HIGHLY COMPRESSED without Errors and Problems

===============================================

Grand Theft Auto IV Recommended Requirements

CPU: Intel Core 2 Quad 2.4GHz, AMD Phenom X3 2.1GHz
RAM: 2 GB (Windows XP) 2.5 GB (Windows Vista)
OS: Windows Vista - Service Pack 1 / XP - Service Pack 3 / Windows 7
VIDEO CARD: 512MB NVIDIA 8600+ / 512MB ATI 3870+
HARDWARE T&L: Yes
PIXEL SHADER: 3.0
VERTEX SHADER: 3.0
SOUND CARD: Yes
FREE DISK SPACE: 18 GB

DEDICATED VIDEO RAM: 512 MB

Screenshots

GTA 4 ULTRA HIGHLY COMPRESSED :- 

CLICK HERE

----------------------------------------------------------------------

THANK YOU SOO MUCH FOR VISITING OUR SITE.

Buds, Blooms, And Thorns Review Of Triassic Terror By Eagle-Gryphon Games

Buds, Blooms, and Thorns Review of Triassic Terror by Eagle-Gryphon Games
DisclaimerSupport me on Patreon!

Vitals:
Title: Triassic Terror
Designed by: Peter Hawes
Publisher: Eagle-Gryphon Games
Year Published: 2013
MSRP: $75
2-6p | 90-120 min | 14+

Introduction:

Triassic Terror is an exciting tactical game for 2 to 6 players. Starting with just one herd in the steamy Triassic Swamp, players must make wise choices to grow new herds and guide their migration across the four pre-historic landscapes.

This Primeval world is full of danger, with the mighty T-Rex, marauding Velociraptors and swooping Pterodactyls looking to reduce the size of your herds. Jurassic and Cretaceous Volcanoes fill this violent world with ash and dust and devastate the terrain.

The player best managing his herds and dominating not only local habitats, but entire environments, will win this challenging game.

~Triassic Terror is the winner of GAMES Magazine's Best New Strategy Game Award~

- Description from publisher.

Blooms:
Blooms are the game's highlights and features.  Elements that are exceptional.

• Very interesting area control mechanics.  The methods of distributing your dinos across the board and controlling areas based on the size of your herd present unique strategic situations.
• Amazing components!  You get to play with plastic dinosaur miniatures!  Like the toys you probably had as a kid (or maybe like the ones your kids currently have)!

Buds:
Buds are interesting parts of the game I would like to explore more. 

• This is a brutal game, with a ton of destructive player interaction.  You really have to be in the mood for a game with a lot of carnage, but that destruction drives some tight strategy and is pretty evenly dished out.
• The game has a very different feel at different player counts - fewer players is less brutal and offers more opportunities for strategic growth, while more players really has you running a tight ship with very little wiggle room strategically.

Thorns:
Thorns are a game's shortcomings and any issues I feel are noteworthy.

• Not a game for everyone.  There is a TON of take-that in this game, although it's so widespread that no one ever feels singled out.  The carnage is everywhere!
• The sweet spot is 3-4 players.  There are 6 possible actions each turn, including four of which mess with other players' herds, and three that cause predators to remove opponents' dinosaurs from the board.  With 6 players every destructive action is taken every turn; with 3-4 players there are periods of calm between the predator attacks so you can build up herd sizes.

Final Thoughts:

As you may have come to expect from Eagle-Gryphon Games, the component quality is absolutely stellar.  Everything from the box to the insert (with its plastic cover to keep everything nice and neat) to the wooden dinosaur tokens, to the amazing plastic dinosaur models, and everything else is top notch quality.  This game is amazing just for the table presence alone.  My only complaint is that the graphic design on the reference tiles is very busy and can be confusing.  But once you know the possible actions, the reference becomes just a reference and is easy enough to use.

The actual gameplay is a little more subjective though.  My game group is mostly gamers who like deeper strategy games.  Some come from a more Amerithrash background (especially wargames like Axis & Allies, Risk, and some of the classic Avalon Hill titles) and some are really into more Euro-style games with less chaotic strategy.  Triassic Terror appealed to both groups, but didn't seem to be an instant hit.  Everyone enjoyed playing, and felt the brutality of the t-rex, raptors, and pterodactyl were amazingly thematic, however, this brutality was also a major source of frustration among both camps.  Everyone felt it was very difficult to create any long-term strategy because dinosaurs were removed from the board almost as fast as you could add them.

This was especially prevalent in the six-player game where raptors and the t-rex actions were used every single round.  You start the game with 4 dinosaurs and in our six-player game, after six rounds of play, our herds numbered 7-12 dinosaurs.  Our herds fared better in the four-player game, ending with 12-25 dinosaurs in our herds, but the predators were still brutal and often derailed any attempt at strategic planning.  Triassic Terror is mostly a tactical game.  You can only plan slightly and instead have to react to the situation you find your herds in each turn.

Triassic Terror falls just short of a Bloom rating, leaving it as a Bud, mostly because the game wasn't quite right for my group.  We liked the area control aspects of the game, felt it was very thematic (maybe too much so), but didn't like the frustration of the destructive mechanics.  For a dudes-on-a-map (or rather dinos-on-a-map) game, this has amazing table presence.  People will definitely stop to check it out and it's a ton of fun to play with dinosaurs.  YOU GET TO PLAY WITH DINOS!!!  But in a world where games like Kemet exist, Triassic Terror falls just a little bit short.  Kemet also has amazing table presence, great area control mechanics, and interesting combat elements (plus, you can ride a dung beetle!), but lacks the brutality and outright devastation that Triassic Terror brings to the table.

If you like area control games and/or dinosaurs though, I definitely recommend giving Triassic Terror a try if you have the chance.  It just barely missed the cut for me, but you may love it.  I'm definitely keeping my copy around for a while because I have a friend that I think will love it, and I'm sure my sons will enjoy it, too.  So while I'd rather play Kemet, there's definitely a time and place for Triassic Terror.

Buds, Blooms, and Thorns Rating:

Bud!  This game definitely has some
great moments.  It's good for several plays
and should appeal to most gamers, especially
if you enjoy other games like this.

Pictures:

Did you like this review?  Show your support: Support me on Patreon!Also, click the heart at Board Game Links , like GJJ Games on Facebook , or follow on Twitter .  And be sure to check out my games on  Tabletop Generation.

GJJ Games Reviews are independent, unpaid reviews of games I, George Jaros, have played with my family and friends.  Some of these games I own, some are owned by friends, some are borrowed, and some were provided by a publisher or designer for my honest feedback and evaluation.  I make every attempt to be both honest and constructively critical in my reviews, and they are all my opinions.  There are four types of reviews on GJJ Games: Full Reviews feature critical reviews based on a rubric and games receive a rating from 0 to 100.  Quick Reviews and Kickstarter Previews are either shorter reviews of published games or detailed preview reviews of crowdfunding games that will receive a rating from 0 to 10 based on my impressions of the game.  Buds, Blooms,and Thorns reviews are shorter reviews of either published or upcoming games that highlight three aspects of a game: Buds are parts of a game I look forward to exploring more, Blooms are outstanding features of a game, and Thorns are shortcomings of a game.  Each BBT review game will receive an overall rating of Thorn, Bud, or Bloom.

Article: The Strategic Use Of Smartphone Features To Create A Gaming Experience Of Mystery: The Mind Alone Case

As I said in the last post, in July I attended the Human Computer Interface Conference at Orlando (Florida). Today I want to share my article (click here) and invite everybody to buy the conference's book with all the articles related to the subject "games" (click here).



#GoGamers

Tech Book Face Off: Effective Python Vs. Data Science From Scratch

I must confess, I've used Python for quite some time without really learning most of the language. It's my go-to language for modeling embedded systems problems and doing data analysis, but I've picked up the language mostly through googling what I need and reading the abbreviated introductions of Python data science books. It was time to remedy that situation with the first book in this face-off: Effective Python: 59 Specific Ways to Write Better Python by Brett Slatkin. I didn't want a straight learn-a-programming-language book for this exercise because I already knew the basics and just wanted more depth. For the second book, I wanted to explore how machine learning libraries are actually implemented, so I picked up Data Science from Scratch: First Principles with Python by Joel Grus. These books don't seem directly related other than that they both use Python, but they are both books that look into how to use Python to write programs in an idiomatic way. Effective Python focuses more on the idiomatic part, and Data Science from Scratch focuses more on the writing programs part.

VS.

Effective Python

I thought I had learned a decent amount of Python already, but this book shows that Python is much more than list comprehensions and remembering self everywhere inside classes. My prior knowledge on the subjects in the first couple chapters was fifty-fifty at best, and it went down from there. Slatkin packed this book with useful information and advice on how to use Python to its fullest potential, and it is worthwhile for anyone with only basic knowledge of the language to read through it.

The book is split into eight chapters with the title's 59 Python tips grouped into logical topics. The first chapter covers the basic syntax and library functions that anyone who has used the language for more than a few weeks will know, but the advice on how to best use these building blocks is where the book is most helpful. Things like avoiding using start, end, and stride all at once in slices or using enumerate instead of range are good recommendations that will make your Python code much cleaner and more understandable.

Sometimes the advice gets a bit far-fetched, though. For example when recommending to spell out the process of setting default function arguments, Slatkin proposed this method:

def get_first_int(values, key, default=0):
    found = values.get(key, [''])
    if found[0]:
        found = int(found[0])
    else:
        found = default
    return found

Over this possibility using the or operator short-circuit behavior:

def get_first_int(values, key, default=0):
    found = values.get(key, [''])[0]
    return int(found or default)

He claimed that the first was more understandable, but I just found it more verbose. I actually prefer the second version. This example was the exception, though. I agreed and was impressed with nearly all of the rest of his advice.

The second chapter covered all things functions, including how to write generators and enforce keyword-only arguments. The next chapter, logically, moved into classes and inheritance, followed by metaclasses and attributes in the fourth chapter. What I liked about the items in these chapters was that Slatkin assumes the reader already knows the basic syntax so he spends his time describing how to use the more advanced features of Python most effectively. His advice is clear and direct so it's easy to follow and put to use.

Next up is chapter 5 on concurrency and parallelism. This chapter was great for understanding when to use threads, processes, and the other concurrency features of Python. It turns out that threads and processes have unique behavior (beyond processes just being heavier weight threads) because of the global interpreter lock (GIL):

The GIL has an important negative side effect. With programs written in languages like C++ or Java, having multiple threads of execution means your program could utilize multiple CPU cores at the same time. Although Python supports multiple threads of execution, the GIL causes only one of them to make forward progress at a time. This means that when you reach for threads to do parallel computation and speed up your Python programs, you will be sorely disappointed.

If you want to get true parallelism out of Python, you have to use processes or futures. Good to know. Even though this chapter was fairly short, it was full of useful advice like this, and it was possibly the most interesting part of the book.

The next chapter covered built-in modules, and specifically how to use some of the more complex parts of the standard library, like how to define decorators with functools.wraps, how to make some sense of datetime and time zones, and how to get precision right with decimal. Maybe these aren't the most interesting of topics, but they're necessary to get right.

Chapter 7 covers how to structure and document Python modules properly when you're collaborating with the rest of the community. These things probably aren't useful to everyone, but for those programmers working on open source libraries it's helpful to adhere to common conventions. The last chapter wraps up with advice for developing, debugging, and testing production level code. Since Python is a dynamic language with no static type checking, it's imperative to test any code you write. Slatkin relates a story about how one programmer he knew swore off ever using Python again because of a SyntaxError exception that was raised in a running production program, and he had this to say about it:

But I have to wonder, why wasn't the code tested before the program was deployed to production? Type safety isn't everything. You should always test your code, regardless of what language it's written in. However, I'll admit that the big difference between Python and many other languages is that the only way to have any confidence in a Python program is by writing tests. There is no veil of static type checking to make you feel safe.

I would have to agree. Every program needs to be tested because syntax errors should definitely be caught before releasing to production, and type errors are a small subset of all runtime errors that can occur in a program. If I was depending on the compiler to catch all of the bugs in my programs, I would have a heckuva lot more bugs causing problems in production. Not having a compiler to catch certain classes of errors shouldn't be a reason to give up the big productivity benefits of working in a dynamic language like Python.

I thoroughly enjoyed learning how to write better Python programs through the collection of pro tips in this book. Each tip was focused, relevant, and clear, and they all add up to a great advanced level book on Python. Even better, the next time I need to remember how to do concurrency or parallelism or how to write a proper function with keyword arguments, I'll know exactly where to look. If you want to learn how to write Python code the Pythonic way, I'd highly recommend reading through this book.

Data Science from Scratch

I didn't expect to enjoy this book quite as much as I did. I went into it expecting to learn about how to implement the fundamental tools of the trade for data science, and that was indeed what I got out of the book. But I also got a lighthearted, entertaining, and surprisingly easy-to-read tour of the basics of machine learning using Python. Joel Grus has a matter-of-fact writing style and a dry wit that I immediately took to and thoroughly enjoyed. These qualities made a potentially complex and confusing topic much easier to understand, and humorous to boot, like having an excellent tour guide in a museum that can explain medieval culture in detail while cracking jokes about how toilet paper wasn't invented until the 1850s.

Of course, like so many programming books, this book starts off with a primer on the Python language. I skipped this chapter and the next on drawing graphs, since I've had just about enough of language primers by now, especially for languages that I kind of already know. The real "from scratch" parts of the book start with chapter 4 on linear algebra, where Grus establishes the basic functions necessary for doing computations on vectors and matrices. The functions and classes shown throughout the book are well worth typing out in your own Python notebook or project folder and running through an interpreter, since they are constantly being used to build up tooling in later chapters from the more fundamental tools developed in earlier chapters. The progression of development from this chapter on linear algebra all the way to the end was excellent, and it flowed smoothly and logically over the course of the book.

The next few chapters were on statistics, probability, and their use with hypothesis testing and inference. Sometimes Grus glossed over important points here, like when explaining standard deviations he failed to mention that this metric only applies to (or at least applies best to) normal distributions. Distributions that deviate too much from the normal curve will not have meaningful standard deviations. I'm willing to cut him some slack, though, because he is covering things quickly and makes it clear that his goal is to show roughly what all of this stuff looks like in simple Python code, not to make everything rigorous and perfect. For instance, here's his gentle reminder on method in the probability chapter:

One could, were one so inclined, get really deep into the philosophy of what probability theory means. (This is best done over beers.) We won't be doing that.

He finishes up the introductory groundwork with a chapter on gradient descent, which is used extensively in the later machine learning algorithms. Then there are a couple chapters on gathering, cleaning, and munging data. He has some opinions about some API authors choice of data format:

Sometimes an API provider hates you and only provides responses in XML.

And he has some good expectation setting for the beginner data scientist:

After you've identified the questions you're trying to answer and have gotten your hands on some data, you might be tempted to dive in and immediately start building models and getting answers. But you should resist this urge. Your first step should be to explore your data.

Data is never exactly in the form that you need to do what you want to do with it, so while the gathering and the munging is tedious, it's a necessary skill that separates the great data scientist from the merely mediocre. Once we're done learning how to whip our data into shape, it's off to the races, which is great because we're now halfway through this book.

The chapters on machine learning models, starting with chapter 12, are excellent. While Grus does not go into intricate detail on how to make the fastest, most efficient MLMs (machine learning models, not multi-level marketing), that is not the point. His objective is to show as clearly as possible what each of these algorithms looks like and that it is possible to understand how they work when shown in their essence. The models include k-nearest neighbors, naive bayes, linear regression, multiple regression, logistic regression, decision trees, neural networks, and clustering. Each of these models is actually conceptually simple, and the models can be described in dozens of lines of code or less. These implementations may be doggedly slow for large data sets, but they're great for understanding the underlying ideas of each algorithm.

Threaded through each of these chapters are examples of how to use each of the statistical and machine learning tools that is being developed. These examples are presented within the context of the tasks given to a new data scientist who is an employee of a budding social media startup for…well…data scientists. I just have to say that it is truly amazing how many VPs a young startup can support, and I feel awfully sorry for this stalwart data scientist fulfilling all of their requests. This silliness definitely keeps the book moving along.

The next few chapters delve a bit deeper into some interesting problems in data science: natural language processing, network analysis (or graph algorithms), and recommender systems. These chapters were just as great as the others, and by now we've built up our data science tooling pretty well from the original basics of linear algebra and statistics. The one thing we haven't really talked about, yet, is databases. That's the topic of the 23rd chapter, where we implement some of the basic operations of SQL in Python in the most naive way possible. Once again it's surprising to see how little code is needed to implement things like SELECT or INNER JOIN as long as we don't give a flying hoot about performance.

Grus wraps things up with an explanation of the great and all-powerfull MapReduce, and shows the basics of how it would be implemented with mapper and reducer functions and the plumbing to string it together. He does not get into how to distribute this implementation to a compute cluster, but that's the topic of other more complicated books. This one's done from scratch so like everything else, it's just the basics. That was all fine with me because the basics are really important, and knowing the basics well can lead you to a much deeper understanding of the more complex concepts much faster than if you were to try to dive into the deep end without knowing the basic strokes. This book provides that foundation, and it does it with flair. I highly recommend giving it a read.


Both Effective Python and Data Science from Scratch were excellent books, and together they could give a programmer a solid foundation in Python and data science as long as they already have some experience in the language. With that being said, Data Science from Scratch will not provide the knowledge on how to use the powerful data analysis and machine learning libraries like numpy, pandas, scikit-learn, and tensorflow. For that, you'll have to look elsewhere, but the advanced, idiomatic Python and fundamental data science principles are well covered between these two books.

A Little Touch Of Leipzig (In The Night)

Apologies for the obscure 70s music reference ! Some of you may recall that we started to delve back into the wonderful world of 15mm Napoleonic gaming recently after I finally put together my Quarrie / GdeB mash up rules. A rerun of Albuera ensued recently and that went quite well so it was time for a second go with the "new" rules. We decided to move away from the Peninsula and try some Central European action to see how those armies performed. I will put a link to the rule amendments at the end of the post.

Italian Light Infantry masquerading as Young Guard

I picked the 1813 Dolitz & Probstheyda Scenario from the Napoleonic Scenarios 2 book from Partizan Press, avaliable below,

https://www.caliverbooks.com/Partizan Press/partizan_NS.shtml

An excellent set of scenario books perfect for any rule set. Even with over 6,000 15mm figures for the period I had to make some compromises as I have no Austrians and no French Guard, so my Italian Guard and Russians had a run out instead.

Historical Background 

We will all be familiar with the background of the Battle of Nations and this game represents a small section of that battle, the centre of Napoleons positions in the South of the battlefield to be precise. The game represents the Allied attack of the 18th October and is a simple attack and defend scenario.

Russian Cuirass

Set Up 

12 x 6 table with the Allies marching on the table on move 1 from the left, as viewed in the photos below,

Allies March On

From the French Lines

A fairly straightforward battlefield, there is a line of two villages and a farm along the centre of the table, Dolitz, furthest from the camera, Dosen in the centre and then the Meusdorf Farm. The Farm and Dolitz each had a small wood adjacent to their left flank. On the far side of the table there is another wood and the edge of a steam.

The rear of the French Line is dominated by a ridge line on which the village of Probstheyda is located (green copper spire church) with a fifth and final village, Lossing, which is level with Probstheyda and behind Dolitz.

French Infantry in Dosen

French Orbat

For general stats see the Quarrie / GdeB mash up rules post below, any variations on the standard charts to reflect the lower standard of some of the French units is noted below.

C in C - Murat

Augereau - IX Corps
Brigade Sierawski - 3 x Polish Line Battalions (2 x 36 figs and 1 x 32 figs) and 1 6pdr Polish Foot Battery. Set up between Dolitz and the stream.
Brigade Lagarde - 2 x Legere Battalions (36 , 30) and 2 x Ligne Battalions, both 36, both -1 on standard French Morale. 1 x 8pdr Foot Artillery. Set up in and around Dolitz.
Brigade Semele - 1 x 36 Fig Legere Battalion, 2 x Ligne Battalions 1 x 36 and 1 x 30, the 30 man unit is a- 2 on Morale. 1 x 8pdr Foot Artillery.
Brigade Sulkowski - 1 x 18 man Polish Uhlan Regt and 1 x 6pdr Polish Horse Art.

Probstheyda

Victor - II Corps
Brigade Dubreton - 1 x 36 Legere Battalion, 3 x Ligne Battalions 2 x 36 and 1 x 30 (also -1 morale). 1 x 6pdr Foot Artillery. Set up in and around Dosen.
Brigade Dufour - 1 x 36 Ligne, 1 x 30 Ligne, 1 x 30 Legere and 1 x 24 Ligne (-1 Morale). Set up around the Farm.
Brigade Corbineau - 1 x 18 Hussars, 1 x 6pdr Horse Art. Set up between Dosen and the Farm.

French Cuirass

Oudinot  - Guard Corps (all in Reserve behind ridge, activated the turn after one of the front villages is either assaulted or fired on by musketry.
Brigade Pacthod - 4 x 32 Young Guard, 8pdr Foot Artillery
Brigade Curial - Italian Guard Grenadiers, Italian Guard Fusiliers both 30 figs, Italian Guard Velites 32 Figs, Italian Guard Foot Artillery 12pdr.
Brigade Bouresoulle - 3 x 24 Fig Cuirassier, 1 x 24 Dragoon (inferior mounts)

On a roll of 12 on initiative - Napoleon arrives anywhere on the French baseline escorted by 1 x 24 Guard Lancer and 1 x 24 Guard Chasseur.

Italian Guard on the ridge

Allied Army

C in C Schwarzenberg (remember Russian troops have been substituted in for Austrians)

Hesse Homburg - move on table opposite Dolitz
Brigade Roth - 3 x 48 Fig Russian Infantry Battalions one with -1 morale. 3 x 36 Fig Russian Infantry Battalions one with -1 morale. 1 x 6pdr Prussian Foot Artillery.
Brigade Mezentzov- 1 x 48 Fig Russian Infantry Battalion, 2 x 36 Fig Russian Infantry Battalions both with -1 morale. 1 x 30 figure Prussian Landwher, 1 x 6pdr Prussian Foot Artillery.
Brigade Vassov - 1 x 36 Fig Russian Grenadier Battalion, -1 morale. 2 x 16 Fig Prussian Hussar one with + 1 morale and 1 x 6pdr Prussian Horse Art.

Cossacks in a wood, what a surprise 

Gorchakov - move on table opposite Dosen
Brigade Grenadier - 4 x 32 Grenadier Battalions, 2 Prussian, 2 Russian. 1 x 6pdr Prussian Foot Artillery
Brigade Laelin - 1 x 24 Russian Guard Cuirass, 1 x 24 Russian Cuirass
Brigade Larkov - 2 x 24 Russian Cuirass

Russian Infantry Battalions attack

Barclay move on table opposite the Farm
Brigade Pirch  - 1 x 32 Prussian Fusilier (+1 morale), 1 x 32 Prussian Musketeer, 2 x 24 Reserve Prussian Infantry, 2 x 24 Prussian Landwher.
Brigade Von Kluse - 1 x 32 Prussian Fusilier (+1 morale), 1 x 32 Prussian Musketeer, 2 x 24 Prussian Reserve Infantry, 2 x 24 Prussian Landwher, 1 x Prussian Foot Artillery, 1 x 16 Landwher Cavalry.
Brigade Oldenkop - 5 x 32 Fig Russian Infantry Battalions (2 are -1 morale) and 1 Russian Position Battery
Brigade Zilowski  - 1 x 24 Russian Uhlan, 1 x 18 Russian Hussar, 1 x Russian Horse Artillery.

Prussian Reserve Infantry on the move

How did we get on 

We actually played through the scenario twice and it was quite an interesting experience having a go at a Central European battle after the Albuera Peninsula game. National Characteristics definitely give each army a personality and once you become aware of its strengths you start to alter your tactics to those of that nation, something I have been after in a game for a long time.

1st shot 6 gun battery, low ammo !

Normally I let the photos follow the story of the game but on this occasion they are a bit random, one because we played through twice and secondly because I was too busy taking notes about the rules rather than what was happening in the games.

Prussian Infantry attacking the Farm

In game 1 the match was over pretty quickly, the attack on Dolitz was a bloody affair with the Russians failing to gain any headway against the village and the Polish Infantry who had formed a line behind the stream. It wasn't long before the attacking Russians were streaming back to the baseline.

Another view of the Prussian attack on the Farm

In the centre the Allies sat there and got shot ! The Russian Guard Cuirass ended up retiring off the table without moving forward at all. That woke the rest of the troops up and there was a glorious charge against a gun line (see top photo) at the end of that game.

Waiting to go again in game 2

The Farm side of the table ground to a stalemate fairly quickly, the attack started on the Farm but all the French Heavy Cavalry came out to play, putting the Prussian Infantry in square ending any movement. With all the Russians running away at the end of our first session we decided just to reset and go again. I made a couple of changes to the orbat (the French started with the Guard Cavalry in game 1). Overall an easy Victory for the French in our first run through.

French Infantry in Dosen

Another aspect of game 1 was the atrocious dice rolling of the Allies (including myself) the double one for the Russian Artillery in the photo above was just the start, we have all had it, those days where you can't roll over 5 on 2 d6 until you need to roll low when you roll a double 6 !

French in the Farm

Game 2 went on for a lot longer (3 sessions) and was a much closer affair. We realised that we had been allowing too many people to shoot out of built up areas which made the approach to the villages a bit easier and the removal of the Guard Cavalry made the French player a little bit more cautious.

Attack on Dolitz in Game 2

The Russian attack on Dolitz was more sustained and they had a good deal of success against the French in the wood near the village, however the downfall this time was the Polish on the flank who pushed home their own attack in support of the village, there were some further shocking die rolls by the Russians but all in all a much closer battle.

French Cavalry mass behind the lines

In the centre the Allies wisely stayed out of range of the French Artillery, this time the French Cavalry massed behind the lines in the centre of the table but it all ended up with a lot of posturing. The Allies never got a clear run at a target whilst the French kept failing command rolls and remained on Hold orders behind the central village.

Cossacks skirmishing against Young Guard

The area around the Farm got a bit more fruity this time, this time the Russian Infantry led the attack, one thing we have quickly learnt is there is no point messing about firing Russian Infantry, get them stuck in as soon as you can. A battle raged over the woods adjacent to the Farm and the French sent two units of Young Guard to hold the line.

Prussian Infantry supporting the Russian attack

The Russians attacking the Farm failed to charge but those in the wood unceremoniously dumped the Young Guard out of the cover and into the path of a waiting Russian Hussar unit.

End of the Young Guard

The French committed the Italian Guard to hold the line in that area, the Allies had turned the flank but the new line at a right angle anchored on Probstheyda was pretty strong but was lacking Cavalry support.

We finished the game at this point entering a period of stalemate, the Allies had made more progress than before but had failed to get into the villages, with a bit more luck on dice rolls we could have got into the front line of built up areas but I don't think there is enough to get into the rear towns, it also felt that the French had a lot of artillery and with the ridge line they could often get multiple batteries on one unit when needed.

Italian Guard coming to the rescue

Rules Development 

The original Quarrie / GdeB mash up rules post can be accessed below,

https://yarkshiregamer.blogspot.com/2018/10/quarrie-to-general-de-brigade.html

There is still some work to do to get them perfect but I am happy with the progress and it's given me a renewed interest in Napoleonic gaming (which was my first gaming period) after years of inactivity so that in itself is a huge positive.

General de Brigade makes it harder to get into contact than other rules but when you do melee is over quickly, usually in a single round and there is none of the enormous black holes pulling in multiple units into massive combats which last 3 plus turns like say Gilders which needs a change of mind set from players of those sets.

The magic floaty tree

We found getting into contact a real problem in this game which is interesting as that wasn't an issue in the Peninsula bash, maybe we were expecting the British to shoot units off ?

The main discussion point and change from the game was the +1 for infantry charging in column. Infantry now has a charging factor for melee and a confused factor when not. We found that a plus 1 on top of the Impact factor was too much but we needed to reflect the impetus of charging in column so the decision was to count the Impact factor as the charging column factor and add a -1 to the Impact when charging in any other formation. The exception being the British.

I hope to get at least one more Napoleonic Game in before Xmas, oh the joy of too many collections ! Next game, currently on table is Spanish Civil War.