striat wrote:Ydiss wrote:Sounds like it's broken more than it's fixed and the risk/reward of the change has lost scope, to me.
This definitely is not true. It has fixed exactly what it was intended to. All we did was revert to eqemu stock code for this aspect. This would be a great place if we could change people's mindset to not cheat and look for loopholes. However, that just is not going to happen. Right now, it's serving its purpose and it will be reviewed further as mentioned above.
A code reversal is still a change and I didn't actually claim it hasn't fixed what it was intending to fix (it's clearly done that

). I'm expressing my opinion and providing a suggestion on how it could perhaps have been fixed more elegantly, with a lower impact on the players (particularly those who don't even use the exploit).
Reverting code, in my opinion, should be done only when the reason is critical (game breaking, in this case). The custom change that has now been reverted was originally implemented for a reason, wasn't it? Effectively, by reverting it, that reason has now been forgotten, or it has been considered not worth the risk of the exploit that it allowed. This is assuming that the custom code was
not introduced to allow pulling mobs through the whole zone out of line of sight, of course. I'm assuming it was introduced for some benefit and if this is the case the removal of that code has negated that benefit, which is probably why you're seeing these complaints and posts of feedback about the bot behaviour.
You're reviewing the code in response to the complaints, which is fine. I'm only questioning whether the issues created by reverting should be the things now being reviewed when it could, perhaps, have simply been the actions required to exploit that should be reviewed instead.
As I know nothing of the code, I can't comment further than that, of course. I only felt that it would have been a more elegant solution, one that has the lowest impact on the general population, to attempt to restrict LOS only on specific actions that exploited it, rather than reverting the entire custom code nugget.
Just my thoughts and suggestions. If what I'm suggesting is impossible or impractical and you're sure the benefit of avoiding the exploit is greater than the risk of altering the requirements of players who use bots (exploits or not), then that's that.
Thanks for your response, it's appreciated.