Bug #1992
Added by bjcasey over 6 years ago.
Updated over 6 years ago.
Description
Needs an overhaul to be redone similar to how mining is now cached.
Should not be spamming:
Target #2 [NULL / NULL] entity does not exist. Calling cleanup routine. -- Skipping target.
- Status changed from New to Resolved
This should be resolved in Version 1.021.
- Combat targeting has been rewritten to be behave more like the mining targeting. This should fix a bug where it would spam that it couldn't assign a NULL target to a specific target. It should also allow it to recognize that if there are multiple attackers it is in combat until all attackers have been destroyed (previously, it would think it wasn't in combat for a brief amount of time between attacker destructions).
- Status changed from Resolved to In Progress
[5] Target #1 cannot be assigned to [NULL / NULL] because it has already been assigned to Target #1. -- Skipping target...
- Status changed from In Progress to Resolved
This should be resolved in Version 1.022.
- AstroBot should no longer get itself into a loop of being unable to assign a NULL target because it is already assigned to another target.
Also available in: Atom
PDF
Updated by