TopTarget

3.1.3
- Added canaccessvalue (removed in 3.1.2) back into group unit validation, because rarely the group unit value cannot be accessed and then there would have been an error without canaccessvalue validation. Either way, this will cause that group unit's target to be ignored, so that part is not fixed. Seems to be the cause of the "zero targeting when greater than zero expected" issue that has been attempted to fix in recent TT updates. It doesn't have to be zero, it's just more noticeable in the heat of battle when zero count. Will look into this more, and fix, or if no fix, display an indication that the issue is currently happening.