Pages

Sunday, 18 August 2019

My terrain generator: A progress report

I've been doing a lot of work devising a terrain generator that will work with my simple campaign system and my PORTABLE WARGAME rules. The basic rules have been written, and now I have to test them. This is going to take some time, as any problems that arise during the testing may require tweaks here and there.

It is my intention to include lots of explanatory diagrams in the rules to show how they work, and this is also going to take time as I am going to have to create them using the meagre resources I have to hand ... mainly MS PAINT. As a result, I hope to be able to upload the rules as a blog entry by the middle of the week.

Saturday, 17 August 2019

A simple campaign system (Part 4): Initial play testing

I decided that the British Relief Force would comprise three separate formations:
  • The River Column (Four Infantry units, Artillery Unit, and a Machine Gun unit, all carried in steamboats) starting from Wadi Halfa and moving up the River Nile towards Khartoum.
  • The Desert Column (Three Cavalry units) starting from Wadi Halfa and crossing the desert towards Abu Hamed to meet up with the Suakin Column.
  • The Suakin Column (Three Infantry units and an Artillery unit) starting from Suakin, and crossing the desert towards Abu Hamed to meet up with the Desert Column.
Turn 1
The River Column threw a D6 die score of 5, which meant that it could move 6 grid areas (5 + 1) ... and landed on an Event grid area. It threw a second D6 and scored 3, which meant that supply problems stopped it from moving for two turns.

The Desert Column threw a D6 die score of 3, which meant that it could move 4 grid areas (3 + 1) ... and also landed on an Event grid area. It threw a second D6 and scored 5, which meant that it was aware that an enemy force was in an adjacent grid area. The Desert Column chose to withdraw one grid area to avoid fighting the enemy force. (I used a 50:50 chance to decide what to do in this instance ... and the dice favoured a withdrawal.)


The Suakin Column threw a D6 die score of 2, which meant that it could move 2 grid areas ... and also landed on an Event grid area. It threw a second D6 and scored 6, which meant that it was ambushed by an enemy force. It chose to fight ... and for the purposes of this play test I adjudicated the result to be a draw, with both sides being exhausted.


(I must admit that I had not expected all three of the elements of the British Relief Force to trigger Events during the first turn of the campaign, but it certainly made it an interesting experience!)

Turn 2
The River Column stayed where it was, and the Desert Column resumed its advance. It threw a D6 die score of 4, which meant that it could move 5 grid areas (4 + 1) ... and yet again landed on an Event grid area. It threw a second D6 and scored 2, which meant that supply problems stopped it from moving for a turn.


The Suakin Column did not move this turn in order to recover from the battle it had fought. (I used a 50:50 chance to decide what to do in this instance ... and the dice favoured a stop to recover.)

Turn 3
As both the River Column and Desert Column had supply problems and could not move, only the Suakin Column was able to make any progress. It threw a D6 die score of 4, which meant that it could move 4 grid areas ... which took it to the Location grid area where Abu Hamed was located. As a result, it had to stop in the adjacent grid area. It threw a second D6 and scored 2, which meant that the Location was devoid of enemy forces and it could occupy Abu Hamed next turn.


Turn 4
All the British columns could move this turn.

The River Column threw a D6 die score of 1, which meant that it could move 2 grid areas (1 + 1).

The Desert Column threw a D6 die score of 6, which meant that it could move 7 grid areas (6 + 1) ... which took it to the Location grid area where Abu Hamed was located. As the Suakin Column had already discovered that the Location was empty of enemy forces and was about to enter the Location themselves, I decided that the Desert Column could advance into Abu Hamed but no further this turn.


The Suakin Column threw a D6 die score of 3, which meant that they could move 3 grid areas. It advanced into Abu Hamed, and linked up with the Desert Column.


Turn 5
The River Column threw a D6 die score of 4, which meant that it could move 5 grid areas (4 + 1) ... which took it to the grid area where the Third Cataract was located. It was not allowed to pass through the cataract, and it threw a second D6 and scored 3. This meant that it could not move for two turns whilst it negotiated its way through the cataract.


The combined Desert/Suakin Columns were ordered to advance towards Berber, which they were to secure prior to the arrival of the River Column. A garrison of one Infantry unit was left behind to secure Abu Hamed. The combined Desert/Suakin Columns threw a D6 die score of 4, which meant that it could move 4 grid areas (The presence of Infantry and Artillery slowed down the Cavalry) ... and landed on an Event grid area. It threw a second D6 and scored 6, which meant that supply problems stopped it from moving for three turns.


At this point in the play test I had to stop, but I felt that there were some interesting areas for further development that had arisen as a result of what had happened. As a solo player it certainly felt as if the system was running itself reasonably well. The movement rules worked as well as I had hoped, and although the Event Table needs some work on it, the concept seems fairly sound. I suspect that the Location Table will need to be tweaked a bit, but again the concept seemed to work reasonably well for this campaign.

It would have been nice to set up the battle that did take place and fight it through on the tabletop, but the absence of any terrain generation rules that fit in with this campaign system is something that I need to work on before the next play test.

As we used to say in the teaching profession, I'm 'working towards' achieving a simple, workable campaign system. As yet, I have some way to go ... but the situation looks positive and it feels as if a solution is within my grasp.

Friday, 16 August 2019

A simple campaign system (Part 3): Some initial rules

Before I even began to draft some rules, I decided to enhance the colours I had used on my campaign grid as the original looked rather anaemic!


The draft (and incomplete) rules that I have written are intended for solo use, but should be easy to amend so that they can be used by several players operating in cooperation or in opposition.

Rules
  • Movement:
    • Infantry and Artillery move 1D6 grid areas per turn.
    • Cavalry move 1D6+1 grid areas per turn (but 1D6 grid areas per turn if accompanying Infantry and/or Artillery).
    • River Boats move at 1D6+2 grid areas per turn.
    • All movement is made through the face a grid area unless the grid areas only touch at a corner, in which case the movement is made through the corner of the grid area.
Two examples of Permitted Movement.
Two examples of Prohibited Movement.
    • Any unit that ends its move in an Event grid area must throw a D6 and read the result from the appropriate Event Table.
    • Any unit that passes through an Event grid area treats the grid area as if there was nothing in it.
    • No unit may enter or pass through a Location grid area as part of a normal move. It must stop an adjacent grid area, throw a D6, and read the result from the appropriate Location Table.
    • River Boats that enters a Cataract grid area must stop and throw a D6.
      • If the D6 die score is 1 or 2, it may not move next turn.
      • If the D6 die score is 3 or 4, it may not move for two turns.
      • If the D6 die score is 5 or 6, it may not move for three turns.
  • Event Table:
    • 1 = Grid area is empty. Proceed unhindered.
    • 2 = Supply problems. Do not move next turn.
    • 3 = Supply problems. Do not move for two turns.
    • 4 = Supply problems. Do not move for three turns.
    • 5 = Enemy forces are in an adjacent grid area. You may fight them next turn or try to avoid them.
    • 6 = Enemy forces have ambushed you. You must fight or retreat one grid area.
  • Location Table:
    • 1 or 2 = The location is empty. It may be occupied next turn.
    • 3 = A small enemy force occupies the location. You may fight them next turn or try to avoid them.
    • 4 = A large enemy force occupies the location. You may fight them next turn or try to avoid them.
    • 5 = A small enemy force occupies the location. You must fight or retreat one grid area.
    • 6 = A large enemy force occupies the location. You must fight or retreat one grid area.
As I was drafting these rules, I realised that I will also have to develop some terrain generation rules for when battles take place, but initially I wanted to see if the movement system will work, and if the Event and Location Tables concept is worth pursuing for solo games.

Thursday, 15 August 2019

A simple campaign system (Part 2): Creating a campaign grid

During our recent cruise, there were several sea days when I had time to sit and doodle in my notebook ... and eventually I can up with an initial design for a generic campaign grid that I could draw on my laptop.

(Please note that all the following illustrations can be enlarged by clicking on them.)


This design allowed linear movement in several directions, with the greyed squares representing important nodes (e.g. towns or cities) on the grid. For example, a unit/formation/army starting out from the central node on the top row of the grid and that was moving four grid areas could reach any of the grid squares shown below.


I then drafted a second generic campaign grid, this time including 'Event' squares.


On this grid the nodes were indicated by thick black edges, 'Event' squares had the word in them and slightly thinner edges, and the greyed areas represented grid squares that a unit/formation/army could not enter.

I felt that although I was making progress, I was unhappy with some aspects of the design of the generic campaign grid, and redrafted it for a third time.


This was much closer in design to my first generic campaign grid, and confirmed my thinking that this idea had potential. The next step was to try to create a definitive campaign grid ... and having only recently run CARRY ON UP THE NILE! at COW2019, I chose the Relief of Gordon in Khartoum as the campaign I would draw a specific campaign grid for.

I started by finding a map that would give me the main geographic features of the Sudan, including the main settlements and potential choke points where fighting might take place.


It was then a relatively simple task to convert this into a campaign grid.

Key to places: WH = Wadi Halfa; Do = Dongola; ED = Ed Debba; AH = Abu Hamed; Be = Berber; At = Atbara; Su = Suakin; Om = Omdurman; Kh = Khartoum
Key to cataracts: 3c = Third cataract; 4c = Fourth cataract; 5c = Fifth cataract; 6c = Sixth cataract

A close-up view of the central section of the campaign grid.
I am happy that I have devised a system for creating campaign grids that seems to work. All I have to do next is to write some rules and test it!

Wednesday, 14 August 2019

A simple campaign system (Part 1): Exploring ideas

I want to include a simple campaign system in my forthcoming PORTABLE COLONIAL WARGAME book, but experience tells me that campaigns usually flounder after a few moves if and when players begin to get bogged down in the minutiae of how the campaign works. They rapidly lose interest, and move onto something else. It therefore follows that any design I come up with MUST be simple and easy to use, and require the absolute minimum of record keeping.

I therefore set myself the following parameters:
  1. The system must be able to be used solo or for several players without access to an umpire.
  2. Campaign movement should be area-to-area or point-to-point rather than anywhere on the map.
  3. It should be possible to include unforeseen events into the system so that players have to contend with the unexpected.
On the face of it, these seem simple parameters to meet ... but when you begin to try to meet them, you soon discover that they are not!

The system must be able to be used solo or for several players without access to an umpire
As I do most of my wargaming solo, it would be relatively easy for me to devise a simple, solo campaign system ... but most wargamers are more sociable than me, and like to fight an opponent that they can see across the tabletop. Trying to devise a simple campaign system that is suitable for use by solo and face-to-face wargamers therefore has an added layer of complication for the designer, especially as you have to assume that players will not have access to an umpire who can 'run' the campaign for them.

Campaign movement should be area-to-area or point-to-point rather than anywhere on the map
I've taken part in campaigns where ordinary maps were used, and it very quickly became obvious where the 'good ground' was and therefore where the battles were most likely to take place. As a result, I have tended to favour simpler maps that use either area-to-area movement or point-to-point movement between the likely sites where fighting will take place, and I cited examples of these in DEVELOPING THE PORTABLE WARGAME.

A simple area movement map, as used in the game SAVE GORDON!
A simple point-to-point map of the area around between Brussels and Charleroi.
A simple area linear track map for a South or Central American revolution or civil war
It should be possible to include unforeseen events into the system so that players have to contend with the unexpected
A simple way to achieve this is the use of Event Cards or an Events Table, but unless one is very careful, it is possible to generate problems that don't seem to fit the campaign.

So where to start?
Having toyed with one or two ideas, I decided to go back to basics, and looked at some game designs that have been around for a long time ... in some cases, a very long time. I started with ludo.


Despite its Latin name (ludo = 'I play'), the game known as ludo probably originated in India, and is thought to have been brought to Europe in the sixth century. It is a simple, strategy board game for two to four players, where each player tries to chase and 'take' their opponent's pieces (i.e. return the piece to its starting point) and prevent them from reaching safety in the middle of the board.

The game has simplicity, but I thought that using it as a basis for a campaign system might not appeal to many wargamers. In addition, it did not seem possible to include any unforeseen events into the game without creating a completely new game.

I then looked at snakes and ladders as a possible model for my game design.


Like ludo, snakes and ladders originated in India, and the two games probably share a common ancestor. It is also a chase game, but with 'events' affecting movement (i.e. the snakes force players to move their piece backwards and ladders propel them forwards). In some ways this looked like a better starting point for a campaign design than ludo ... but as the players were all going in the same direction, the only potential for a conflict between players was when opposing pieces landed in the same square.

I also looked at Monopoly as a possible game design model.


The origins of the current game are generally accepted to have been a development of Lizzie Magie's 'The Landlord's Game', which she created in 1903. Charles Darrow took the design, developed it, and published it in 1932. It was subsequently bought from Darrow by Parker Brothers in 1934.

It is also a chase game, but with the added advantage of including Event Cards (i.e. 'Chance' and 'Community Chest') and a level of resource management (i.e. the purchase and development of property which generates additional income). Perhaps this type of resource management might not be applicable to a wargame, but the inclusion of something that requires players to manage what is available to them does appeal.

Ideas were beginning to form in my head as to how I could meld the various game designs into a simple campaign system, and my recent cruise gave me the opportunity to play around with them.

Please note that the photograph of the Monopoly board is © Hasbro.

Tuesday, 13 August 2019

Memoir '44 New Flight Plan expansion set

I like Richard Borg's wargames, and own quite a few of them, including both the early and later versions of BATTLE CRY and COMMANDS & COLORS: NAPOLEONICS. My largest collection of his games consists of MEMOIR '44 and most of the expansion sets ... and I have just added the latest of the latter to my collection.


The MEMOIR '44 NEW FLIGHT PLAN expansion set is a more streamlined and simplified version of the earlier AIRPACK (which I have used but never owned) and includes
  • 16 unpainted aircraft models that look approximately 1:300th-scale
    • US North American P-51 Mustang fighter
    • US Chance Vought F4U Corsair fighter
    • US Republic P-47 Thunderbolt fighter-bomber
    • US Boeing B-17 Flying Fortress heavy bomber
    • UK Submarine Spitfire fighter
    • UK Hawker Typhoon fighter-bomber
    • UK Avro Lancaster heavy bomber
    • German Messerschmidt Bf 109 fight
    • German Junkers Ju 87 Stuka dive bomber
    • Heinkel He 111 medium bomber
    • Japanese Mitsubishi A6M Zero fighter
    • Japanese Aichi D3A Val dive bomber
    • Japanese Mitsubishi G4M Betty medium bomber
    • Soviet Yakovlev Yak-9 fighter
    • Soviet Ilyushin IL-2 Sturmovik ground attack aircraft
    • Soviet Ilyushin DB-3/IL-4 medium bomber
  • 3 aircraft stands for the models to use when 'flying' over the terrain boards from the original MEMOIR '44 games
  • 30 Air Combat Cards
  • 8 Summary Cards
  • 15 Nation Markers
  • 18 Machine Gun and 12 Bomb Markers
  • A Rules Booklet
  • A Scenario Booklet with scenarios for 21 new battles most of which that can be used with or without the MEMOIR '44 NEW FLIGHT PLAN expansion set
    • Western Front
      • Isneauville Junction
      • Battle of Pico
      • Battle of La Heunière
      • Groesbeek Heights
      • North of Oosterbeek
      • Reinforce Arnhem
      • Elst
      • Koevering Corridor Raid
    • Mediterranean Theatre
      • Kalamata Waterfront
      • Fort Capuzzo
      • Attack of the Sabratha Division
      • Gambut
    • Eastern Front
      • Luftwaffe Air Attack
      • Soviet KV-2 tanks at Lutsk
      • The Grain Elevator
      • Battle of Maciejow
      • Cherkasskoye
    • Pacific Theatre
      • Battle of Wau
      • Main line of resistance
      • Hill 107
      • Capture of Meiktila

Although I have yet to use the rules, I have read through them, and they are not unlike my own air combat rules as featured in DEVELOPING THE PORTABLE WARGAME ... which isn't all that surprising considering they both use individual aircraft models on a hexed board!

For more information about this expansion set (including links to downloads of the rules in four languages and ten of the scenarios), go to the relevant page on the DAYS OF WONDER website.

Please note that the photographs featured above are © DAYS OF WONDER.

Monday, 12 August 2019

Miniature Wargames 437

After my somewhat damning review of last month's issue, I hoped that this month's would be better ... and I am pleased to say that in some ways it was, and in other ways it wasn't.


The articles included in this issue are:
  • Welcome (i.e. the editorial) by John Treadaway
  • Forward observer
  • Send three and fourpence: A Spot of Hapsburg Policing: A Solo Scenario for Rebels & Patriots set in Hungary circa 1848 with text and illustrations by Conrad Kinch
  • The Great Game: Waterloo Replayed: The biggest 28mm recreation of the battle ever attempted! with text by Noel Williams and photographs by Noel and Carrol Williams
  • Alternate Waterloos: At Waterloo Napoleon Did Surrender ... by Arthur Harman, with photographs by John Treadaway
  • The Battle of Karnal: Persian Mughals: February 1739 by Jon Sutherland, with photographs by Diane Sutherland
  • Show Report: Sex It Up: A quick visit to the Joy of Six show with text and photographs by Alex Webster
  • Darker Horizons
    • Fantasy Facts
  • Creating the Forgotten War: Getting the lowdown on Bold Action: Korea an interview conducted by James Winspear
  • Recce
  • Wargame-Mancer: Do game writers dream of electric D10s? Plug in as we talk to designer Joseph McGuire about cyberpunk skirminshing in Reality's Edge an interview conducted by James Winspear
  • Quick and Dirty: Brush through your lead pile with the art of the tabletop standard with text and photographs by James Winspear
  • How To … build a shell crater: Incoming! Grab some cover and get ready for some heavy calibre scenery with text and photographs by James Winspear
  • Fire in the Fens: Hereward the Wake and the Anglo-Saxon Revolt by Chris Swan, with photographs by John Treadaway
  • Stone Me: The continuing tales of a wargames widow with text and photographs by Diane Sutherland
  • Club Directory
So, what did I think of this issue?

Well it was better than number 436 ... but in my opinion it isn't as good a magazine as it used to be. So what did I enjoy?

Well Conrad Kinch was back on track, and although I've never wargamed the Hungarian Revolution of 1848, his Send three and fourpence column made me wonder if I have been missing something. I enjoyed reading The Great Game: Waterloo Replayed (a project that I wish I could have been involved in, had it been possible), and Arthur Harman's Alternate Waterloos, coming as it did so soon after I had read Peter G Tsouras' book NAPOLEON VICTORIOUS: AN ALTERNATE HISTORY OF THE BATTLE OF WATERLOO, was serendipitous. I also enjoyed Chris Swan's Fire in the Fens, especially as I know parts of the Fenland quite well.

What didn't I like?

Why were they two more 'interviews' in this issue? They felt like they were bordering on exercises in 'product placement', although at least Creating the Forgotten War was about a real war and not a fantasy/SciFi one. (And in answer to the question in the title of James Winspear's piece entitled Wargame-Mancer, this game designer does not dream of electric D10s!) Yet again there were two different 'how to ...' articles ... and do I really want to know how to paint figures to 'the tabletop standard' ... whatever that means?

One thing that I did notice in a sidebar in the Darker Horizons section was that Fantasy Facts is being dropped for the time being. It was accompanied by a statement, part of which did give some cause for concern, namely:
'It's not the end of Non-Historical reviews in Miniature Wargames, of course; certainly not! But we are going to put into practice something I have espoused for many years: that there is essentially no difference between wargames set in Historical and Non-Historical 'periods'. On that basis, from this point forward, the plan is to amalgamate and combine reviews into a different format within the magazine'
Over the past few months I have felt that I have seen more and more 'Non-Historical' content creeping into this magazine, and I am worried that this statement is the precursor of changes that will drive me to cancel my subscription. I may well enjoy using imagi-nations in my wargames, but they are always firmly based on historical examples. I am not, and never have been, a Fantasy or SciFi gamer, and I do see differences 'between wargames set in Historical and Non-Historical 'periods''.

Sunday, 11 August 2019

My latest book sales figures

Due to my concentration on other matters, I almost missed looking at my latest book sales figures.

Last month they were as follows.


The sales figures for July are better than I expected ...


... and it was particularity gratifying to see that sales of THE MADASAHATTA CAMPAIGN have now reached one hundred. My two latest books have also made an appearance in my sales figures, and now that they are available in paperback form from Amazon, I hope to see further sales over the next month or so.

A WINTER-ISH WAR is available in hardback, paperback, and PDF from Lulu.com and in paperback from Amazon.


TROUBLE IN ZUBIA is available in hardback, paperback, and PDF from Lulu.com and in paperback from Amazon.

Saturday, 10 August 2019

Some ideas for developing the Portable Napoleonic Wargame

Whilst we were away, Archduke Piccolo wrote a couple of interesting blog entries that analysed the Close Combat system used in THE PORTABLE NAPOLEONIC WARGAME, and they make very interesting reading.

The relevant blog entries were:





Archduke Piccolo outlines some interesting changes to the Close Combat system that he is experimenting with, and I thoroughly recommend that anyone who uses my rules should read his analysis and suggestions.

Please note that the photographs featured above are © Archduke Piccolo.

Friday, 9 August 2019

Another book bites the dust ... almost!

I've been rather preoccupied since we got back from out latest cruise ... and not just with assembling flat-pack furniture!

I finally finished writing the second draft of the centenary history of Hertfordshire Masters' Lodge No.4090 last night, and I will be sending it off for proof reading and checking later today. Unlike all my previous books, I was actually commissioned to write this one, and it has required considerable research into the history of the Lodge and its members. The research actually spawned two other books (MASTERS AT WAR VOLUME 1: UP TO 1920 and MASTERS AT WAR VOLUME 2: 1920 TO 1970) and fills two large crates. Sue has helped by preparing biographical details of all the Worshipful Masters of the Lodge and some of its more notable members.

The crest of the Hertfordshire Masters' Lodge No.4090.
Usually a Lodge has a brief history written when it is fifty years old, and this gives whoever writes the centenary history somewhere to start. This was not the case with the Hertfordshire Masters' Lodge, and I have had to start from scratch. I have read every Minute Book from 1920 to the present day, constructed a spreadsheet that details every meeting of the Lodge, and a produced a database that contains the names of the Lodge's Founders and principal office holders.

With luck only a few errors will be found that require correction, and once that stage is complete, the book can be sent to the printer in time to be printed and bound for the centenary meeting in May 2020. During the meeting, which is likely to be attended by several hundred people, I will have to give a very brief account of the Lodge's history, after which I can finally put this project to bed.

So what next?

Well I seem to have a backlog of things that I want to do, including doing some further work on my PORTABLE COLONIAL WARGAME book. I also have several topics that I want to blog about, including the campaign system that I am trying to develop. I might take a break from blogging over forthcoming the weekend ... but if the muse comes upon me, I may well end up writing a blog entry or two that I hope will be of interest to my regular blog readers.