Possible Bug: Recombining LCU gives it a move order?

[Lokasenna]

Recently when I'm cycling divisions in/out of besieged bases, I notice something strange. So far I've always managed to cancel the phantom move order so I don't know if it would actually make the unit move or not. But what happens is this.

Unit is besieging a base, let's say Palembang. In an attack, it takes a lot of losses/disablements, so I turn off 'upgrade allowed', set Op Mode to Move and the destination to the NW, then split the unit into 3 parts (this seems to make recovery demonstrably faster).

Once the units arrive in the hex to the NW, I will recombine and resplit the unit to evenly redistribute disabled squads and newly arrived devices every day or every few days.

When I recombine the unit, it frequently gives the recombined ID a new move order in the same direction it was just moving - i.e., to the NW. I will post up screenshots in a little while. Working now and wanted to get this out of my brain while I was thinking about it.

I've noticed this on many occasions, not just with one unit or one area of the map.

[Lokasenna]

Hell, it just happened while I was looking at an ID that's been sitting in a hex outside of a base for several weeks, recovering. I combined the parts and the unit gained a destination. The destination remained once I split the LCUs again.

[michaelm75au]

If one of the split units has a destination, it does carry it over to the parent unit.
IIRC, this is (or was changed in early patches) how it was designed.
I'll look up the code shortly to refresh my memory as several attributes carry over from split to parent unit

[erstad]

This happens (sometimes) even if none of the sub-units has a movement order. I see it a lot, I just cancel the movement order for the combined unit.

[Lokasenna]

ORIGINAL: erstad

This happens (sometimes) even if none of the sub-units has a movement order. I see it a lot, I just cancel the movement order for the combined unit.

Well the thing is... I'll order a unit to move east one hex, to say 110,50. Then when it gets there, I'll either split or recombine depending on how I moved the unit out. And the next time I recombine, it will be like it "remembers" the unit was moving east and give it a move order to 111,50. Which is just weird.

It's pretty easy to notice the sudden appearance of a move order, but it's funky.

[michaelm75au]

I looked into clearing destination data before it merges the subunits.
See if this helps