Matrix Games Forums

In the attached file, I have a British garrison of 15i at Le Havre, which is besieged. If I understand the rules correctly, I should be able to supply them either by invasion supply from a depot in the Channel (which I have), or by putting a depot in the city. (The rules say this is the one time a depot can go in a city.)

First problem is that if I create a depot, it gets put out in the area, and is immediately destroyed.

Invasion supply seems to work, inasmuch as the game doesn't ask me to forage the garrison. But then, after the land phase (or actually, I think, after the land combat phase, when I say I don't want to attack the besiegers), I get two pop-up boxes. One says "Le Havre cannot support VI Corps", which doesn't make any sense. I dunno whether that was the corps that originally created the garrison (a long time ago), but in any case it's back in London now.

The next box says "Le Havre cannot support Le Havre", and then my garrison is reduced to zero. It shouldn't have to forage since it has supply, and it didn't ask me to forage, and even if it did forage, a loss of 15 makes no sense. Is this a bug, or is something else going on?

Nathan Rose

Sea supply should work if the port is not blockaded by an enemy fleet.

When I had a siege going on at Gibraltar I was able to place a depot in the city.  In that game everything worked fine.  So this must be some kind of intermittant problem?
 
Just thought you might find this helpful.

Thanks, Nalamin. I think I've seen it work correctly before, too. I suspect this has something to do with having the garrison in a city which is in an unceded province. I've noticed that garrisons in that situation, if you look at the area information box, are categorized as if they were the besiegers, since they are "enemy" units, while the besieging forces of the country that owns the province are listed as if they were inside the city. So I'm thinking that the game gets confused and dumps them outside the walls?

I've noticed a similar ambiguity (maybe this should be a different thread, but....) when it comes to sorties. It's not clear what the term "defender" means in a sortie, but I *think* (I'm just going on recollection, haven't tested it) that the garrison always loses the factor in sorties no matter the die roll (which shouldn't be the case).

To follow up on my previous post, if you examine the information box for a selected area and look at a garrison in an unceded province of a hostile power, you'll see that it is shown as a "besieging rural unit", and any forces of the power that owns the province that come along to besiege the town are shown as "in the city". I imagine that has something to do with the bug I reported above, and could be causing other problems, I would think.

Does this always happen? If a hostile power puts troops in garrison in one of your provincial capitals, say, do you have only to besiege it to make them all disappear instantly?

As an experiment, I just started a game with me playing both Prussia and Austria, and declared war between them. I moved some Prussians into Prague as a garrison and let the Austrians besiege it.

It did categorize the Prussian garrison as "besieging rural unit" and the Austrian corps as "in city", which I still think is odd, but the garrison foraged normally, and I didn't get any message like "Prague cannot support Prague". So whatever was happening in the Le Havre situation above is evidently not a general problem. Can anyone tell me what *is* causing it?

The besiged invasion supply was frankly was not working right when an enemy unit was in the rural location. When the port was besiged and you had a corps in the rural location, it would flip your depot to the rural spot. Also, when you were not using the besieged port supply BUT could use invasion supply the game was thinking that since you did not have a depot in the port to provide besieged port supply then it dismissed possible use of invasion supply and forced a forage.
 
This was a goody for sure! Richard and I have been working this one for the past 72 hours!
It looks like (as of this morning) that we have this fixed in 1.01.