Warzone 2100 Forums

...I remember this bug very specifically from almost a decade ago b/c it was just so frustrating...

Well I experienced it again last night on the campaign (Beta phase still... mission to destroy all AA sites). And I'm still unclear on what causes it. To elaborate, I'd select a target for my tank killer squadron (Mantis/Tracked) and they'd just stand there doing nothing. I hadn't changed their range, AFAIK it was still all "factory settings". Randomly switching their ranged settings would sometimes make them start attacking and assigning them to a Commander would also work sometimes... but not every time. Nor do I know which range is the best to make them effective without turning them all into a bunch of Leeeeroy Jenkins (close range seems too dangerous). Advice plz? ...And why hasn't this been fixed yet if the code is open source now? Wouldn't it just be a single number to change in some XLS file for this weapon? Plz pardon my Naivet'e in case it's not

Ilr wrote:...I remember this bug very specifically from almost a decade ago b/c it was just so frustrating...

Well I experienced it again last night on the campaign (Beta phase still... mission to destroy all AA sites). And I'm still unclear on what causes it. To elaborate, I'd select a target for my tank killer squadron (Mantis/Tracked) and they'd just stand there doing nothing. I hadn't changed their range, AFAIK it was still all "factory settings". Randomly switching their ranged settings would sometimes make them start attacking and assigning them to a Commander would also work sometimes... but not every time. Nor do I know which range is the best to make them effective without turning them all into a bunch of Leeeeroy Jenkins (close range seems too dangerous). Advice plz? ...And why hasn't this been fixed yet if the code is open source now? Wouldn't it just be a single number to change in some XLS file for this weapon? Plz pardon my Naivet'e in case it's not

I guess it isn't fixed*, since nobody reported it here: http://developer.wz2100.net/newticket

*that is assuming it is broken. It sounds broken though.

I remember it being reported at some point.

Aha, found the ticket: http://developer.wz2100.net/ticket/663

Probably isn't even the only ticket. The bug tracker's S:N ratio is steadily decreasing.

Like I said, possibly a reoccurring bug from the very first version(or possibly 1.10) and it was something I only faintly remember from a very long time ago. It could just be local to a certain mission or missions in the campaign since I haven't had time to test skirmishes yet. I'm not even certain how to reproduce it yet... but I'll look back into it before filing anything to be sure