Finland bug?

[sillyflower]

I'm playing allies in standard '39 scenario PBEM v. 1.06. This is the first time I have had a game go beyond '40. This is due only to the fact that I've only been playing PBEM for a few days, not early surrender monkeying.

Finland duly joined the baddies in March '41 per the scenarion rules. They promptly 'invaded' the USSR occupying all hexes up to and including those adjacent to L'grad. USSR is not at war with Axis. L'gad was not attacked, nor can I attack the Finns.

This seems bugged or otherwise plain wrong given that the Finns refused to join in at the start of Barbarossa, but waited until the Germans had got most of the way to L'grad.

[PanzerMike]

I already reported this:
fb.asp?m=4779591

In early version of Warplan, Finland joined when the Germans took Kaunas. This was changed. Don't know why.

[sillyflower]

Kaunas is a bit early anyway. Taking Pskov or 1st turn in July seems to be the 'norm' for this issue

[sveint]

"The Finnish plans for the offensive in Ladoga Karelia were finalised on 28 June 1941".
But the Soviets bombed Finland as soon as Barbarossa started.

To keep it simple I'd suggest that Finland joins once Germany and Russia are at war.
(Much like Bulgaria joins vs Greece).

[PanzerMike]

I tend to agree, but as I said, I don't know why Alvaro changed the Kaunas entry to an event entry in March 1941.

[AlvaroSousa]

There was a gamey exploit if they activated earlier, that's why.

[sillyflower]

Swapped 1 gamey exploit for another.............
Must be solvable fairly easily -I've never seen a problem with appropriate Finnish activation in any other east front games and I've probably played most of them.
Easy to solve with house rule for now tho' to replicate the original rule

[PanzerMike]

Well, if the bug of premature access to the Soviet occupation zone is solved, all will be okay as far as I am concerned.

[AlvaroSousa]

It is solved in the new beta I put up. Well it was when I tested it.

[PanzerMike]

Excellent, though I see no mention of this bug having been fixed in the changelog. I will take your word for it [:)]