22 - Slight inconsistence in new range checking
While the new range checking works great in general, I often find friendly targets successfully aquired while the border color still indicates that it couldn't be targeted. I suggest that after aquiring a target only the ability based in-range-check remains active or given priority.
| User | When | Change |
|---|---|---|
| Kenh | Wed, 11 Mar 2009 14:07:22 | Changed status from Waiting to Replied |
| rmet0815 | Wed, 11 Mar 2009 09:50:11 | Changed status from Replied to Waiting |
| rmet0815 | Wed, 11 Mar 2009 09:24:05 | Changed status from Waiting to Replied |
| rmet0815 | Wed, 11 Mar 2009 09:19:05 | Changed status from New to Waiting |
| Kenh | Wed, 11 Mar 2009 02:34:12 | Create |
- 4 comments
- 4 comments
- #4
rmet0815 Thu, 12 Mar 2009 09:08:44Screenshot with steps how to reproduce it would be perfect. Log of function calls is not needed, as WAR produces too much noise to make any real use of it. Also remember that I rewrote part of the range-scan code for v1.7.1, so you might want to wait until this version is released.
- #3
Kenh Wed, 11 Mar 2009 14:07:21I'll try to reproduce+ss it and make notes about the circumstances. Atm a debug log with function calls is out of reach, as my client reliably c2ds when I activate that check box in the debug options.
- #2
rmet0815 Wed, 11 Mar 2009 09:24:05in v1.7.0 units all show up as "our of reach" if you do not have a range-scan spell set. This is fixed in v1.7.1 (where they stay "unknown range") if you do not have a range-scan spell set.
- #1
rmet0815 Wed, 11 Mar 2009 09:18:43hmmm... this should be the case. If the unit is targeted, it always checks the "range" with the WAR-in-range-check. Meaning that your ACTIVE target is always either "green" or "purple", if you have a "friendly range scan spell" set.
Do you have more data for me to track this down?