troops unloading with "do not unload"

[n01487477]

Had a TTaskforce, set to go to Ramtree Is. with "DO NOT UNLOAD", they unloaded on the Island, I was using this as a waypoint ... guess I've learnt the hard way to not use land as a waypoint... (I made the SShot at the end of my turn, so I've changed the destination and now I'm picking up the troops)...

P.S OMG ... just realised they're still "DO NOT UNLOAD" ... they'll get to AKyab and not unload ... redo the turn !!!

[tsimmonds]

This is a painful undocumented feature. All troops unload when the DH is reached. They don't care where you would like for them to be, all they know is that they have reached the end of the line.

I suppose this is to eliminate the possibility that they could reach the actual DH, and then just sit there on the ships like dumb sh1ts.

[rtrapasso]

ORIGINAL: irrelevant

This is a painful undocumented feature. All troops unload when the DH is reached. They don't care where you would like for them to be, all they know is that they have reached the end of the line.

I suppose this is to eliminate the possibility that they could reach the actual DH, and then just sit there on the ships like dumb sh1ts.

Actually worse than that... sometimes, they will unload just passing land that is NOT the designated destination even with DO NOT UNLOAD being on... fortunately, this is very unusual, but alas, not unheard of - but maybe this is fixed now (haven't heard of it in later patches).

It is much more common for troops to unload on passing a piece of land (not the designated hex) when the UNLOAD is active.

The reverse problem is also true - sub transports won't unload when the UNLOAD button (at the top) is active when they get to their designated hex. You have to hit the UNLOAD button to the far right to get them to unload (at least in friendly hexes).

[Nomad]

As far as I remember, this only happens when the hex in question is controlled by the enemy. If it is contolled by you, your troops will not unload.

[rtrapasso]

ORIGINAL: Nomad

As far as I remember, this only happens when the hex in question is controlled by the enemy. If it is contolled by you, your troops will not unload.

Good to know... [8D]

[Charbroiled]

The way I read it previously here on the forum, is that the program figures that since an enemy controled base was set as a destination, then you ment to invade but forgot to change the "Do not unload". However, IIRC, they will only unload on the first turn that the ships arrive. If the base is friendly, the computer figures you know what you are doing with the "Do not unload".

I would suggest:

1. Do not use an enemy base as an assembly point.

2. If you want to delay unloading, set the destination one hex away from the target (in water, not land) with "Patrol" set.

[tsimmonds]

Course the big problem is a coastal hex with no base. They will unload there too. You must be extra careful. And don't rely on the map art to help you decide whether the hex has land in it or not. The only way to be sure is to use the hotkey (what is it? "a"? "1"?)

[rtrapasso]

ORIGINAL: irrelevant

Course the big problem is a coastal hex with no base. They will unload there too. You must be extra careful. And don't rely on the map art to help you decide whether the hex has land in it or not. The only way to be sure is to use the hotkey (what is it? "a"? "1"?)

1

[castor troy]

had just recently in my PBEM against Swift a regiment unloading at Palmyra while the TF was set to do not unload. After the first "what the f*** is going on" I checked the TF and it was set to do not unload. Though I forgot to set it on unload and voilà, the TF didn´t unload more men... [8|] Things like that can really ruin an invasion...

[Nomad]

ORIGINAL: irrelevant

Course the big problem is a coastal hex with no base. They will unload there too. You must be extra careful. And don't rely on the map art to help you decide whether the hex has land in it or not. The only way to be sure is to use the hotkey (what is it? "a"? "1"?)

this is also very ture. It seems that the game engine treats a hex with no control ( no A, J, or AJ ) in it as enemy held. I wanted to march a unit from a city in my control to a contested hex two hexes away. The middle hex was uncontrolled. I got the message that a unit could not move from one enemy zone of control to another. I then marched it one hex to the uncontrolled hex, which I then controlled, and then marched to the next, contested, hex. So, when your TF, with "Do Not Unload" set stops at an uncontrolled hex, it will attempt to unload, because it thinks it has stopped at an enemy hex and surely it is smarter than you - you dummy - you forgot to set me to unload. [&:] Another case of 2x3 trying to protect us stupid players and causing a severe problem doing it. How many times do you really get to a hex with "Do Not Unload" orders set and you really did want to unload?

/edited for poor typing - I can spell fine - I can not type for beans. [X(]