Armageddon - River Crossing bug

Shadi · 15-04-2007, 09:54

I just noticed that during combat the attacker had a river crossing penalty of 0.0
No engineer general and no engineer attachment.
Anyone else notice this?

Deltoidius · 05-05-2007, 01:11

yes i noticed this river bug as well.

Also I'm having trouble with setting attack times on land. It won't let me roll them back, I can only move the attack time forward. This isn't a problem for naval/air missions.

Raniel · 08-06-2007, 20:57

Maybe Im confusing something, but wasn there a River Crossing Penalty Value in misc.txt? Cause now there isnt one anymore in Armageddon.
Was there one in Doomsday?
If yes, then one could think that Paradox deleted it intentionally. Because as it is hard-coded, it just can't be "forgotten".
Would appreciate if someone took a look over to the Doomsday misc.txt and see if theres a River Cr. Pen. value.
Or if Paradox maybe just tells us if it's a bug and will therefore be resolved by the patch, or if it is WAD...

15-04-2007, 09:54	#1
Shadi Private Join Date: Jan 2005 Posts: 21	Armageddon - River Crossing bug I just noticed that during combat the attacker had a river crossing penalty of 0.0 No engineer general and no engineer attachment. Anyone else notice this?

05-05-2007, 01:11	#2
Deltoidius Private Join Date: Apr 2007 Posts: 14	yes i noticed this river bug as well. Also I'm having trouble with setting attack times on land. It won't let me roll them back, I can only move the attack time forward. This isn't a problem for naval/air missions.

08-06-2007, 20:57	#3
Raniel Corporal Join Date: Dec 2004 Posts: 47	Maybe Im confusing something, but wasn there a River Crossing Penalty Value in misc.txt? Cause now there isnt one anymore in Armageddon. Was there one in Doomsday? If yes, then one could think that Paradox deleted it intentionally. Because as it is hard-coded, it just can't be "forgotten". Would appreciate if someone took a look over to the Doomsday misc.txt and see if theres a River Cr. Pen. value. Or if Paradox maybe just tells us if it's a bug and will therefore be resolved by the patch, or if it is WAD...