Sir R. M8gic1an
2010-09-17 13:36:01
A few points:
- FindObj… calls MSI_TrackObject, when adequate
- MSI_TrackObject increases its search area once, if it loses track of the object and *occasionally* grabs the wrong object because the other one disappeared.
- - There is an easy way to avoid this (distance check)
What I want to do is have MSI_FindObj returning false if it loses track of the object. Why?
Very simple:
- Track Object is unlikely to lose track of the object
- If it does lose track of the object and then someone steals it, we'll be waiting around like a suspicious bot.
The downside of this is that if it just simply loses the object because it lost it (which rarely happens now) we'll click it again.
So it's just a question of preference.
From many posts around the forum, most bans are fuelled from reports. I think that standing around is more likely to get us banned than clicking again
~RM
- FindObj… calls MSI_TrackObject, when adequate
- MSI_TrackObject increases its search area once, if it loses track of the object and *occasionally* grabs the wrong object because the other one disappeared.
- - There is an easy way to avoid this (distance check)
What I want to do is have MSI_FindObj returning false if it loses track of the object. Why?
Very simple:
- Track Object is unlikely to lose track of the object
- If it does lose track of the object and then someone steals it, we'll be waiting around like a suspicious bot.
The downside of this is that if it just simply loses the object because it lost it (which rarely happens now) we'll click it again.
So it's just a question of preference.
From many posts around the forum, most bans are fuelled from reports. I think that standing around is more likely to get us banned than clicking again
~RM