Anyone else ever had the game crash this way?

[umbro]

okay - technically:
This crash happens in JTCS with extreme assault ON or OFF. It does NOT happen in Talonsoft CS. Thus, one has to deduce that it was introduced when the extreme assault option was implemented. The most likely explanation is that when the assault is executed the target units list is empty and the code that considers the target simply falls off the end of the list.

gamey?:
My philosophy on questions of gameyness is whether or not there is a decent justification from a battlefield view. Regarding this example, the game is attempting to model simultaneous events in a linear fashion. Thus, there is some justification for assaulting a hex that becomes empty in the same manner as assaulting one that has enemy units in it. The problem then becomes what is the justification for assault not provoking opfire. This is harder to justify as the standard reason (there are friendlies about) simply does not hold water when the scale is considered and soldiers natures. It appears to me that the justification was based on the game engine rather than battlefield realities.

umbro

P.S. IMHO opfire should be triggered before the assault calculation is made and the results applied before the assault calculation. If this were the case then the gameyness question becomes moot.

P.P.S. The same should be true of assaulting into minefields (IMHO)...