Night Rules Bug

[berto]

It's a legitimate bug, present since February's 2.00 release (and, in development, before).

And nobody -- not the Dev Team, no players even, noticed or reported this until now.

We on the Dev Team will huddle to figure out how to resolve this problem. Maybe posting a hot fix, with corrected night .scn files (only), maybe a 2.02 Update with EXE fixes (much earlier than planned).

Sorry for the trouble!

Gents:

I've been developing a RS night scenario... and noted that units had a 3-hex visibility.

Not being familiar with night time rules / conditions, I thought it was operating correctly!

Thanks for posting... and I look forward to receiving the fix.

For new scenarios, visibility will be as you specify it using the new dynamic #-#[v] system. Should be fine. What will not be fine, not until the next bug-fix update, will be gun flash (etc.) visibility. Until the fix, gun flashes (etc.) will confer no extra effect (no extended visibility beyond normal night visibility).

So you can continue to develop your scenario, but gun flashes (etc.) will not be working quite right.

The underlying problem here is that, in the .scn files, the new #-#[v] visibility specifications pre-empt the old, simple, one number spec -- the number indicating gun flash (etc.) visibility. (Pre 2.0*, ordinary non-flash night visibility was always set to 1, no ifs ands or buts about it.)

The fix for this bug involves changes to the EXEs. Changes to any legacy .scn files will not be needed.

Until we release the next bug-fix update, we advise players not to play night scenarios. (If you can't wait, as a kludgey workaround, you could edit the last number in line 4 of the .scn file, ensuring that the figure is 1. But this would not solve the no-extended-visibility gun flash problem. Gun flashes (etc.) would still be broken.)

Sorry for the goof. Sh*t happens!