Examine Item via hover fails

[greeneyes137]

I recieved a rather complex script and it does what I want, but if it is running, examine items by hovering them fails. If i right click examine an item then the hover examine works. If i do this for say a wrist item and then examine via right click examine both worn wrists, i can then hover the wrist item in bags and the pop-up examine compare all 3 will occur. Until i right click examine, the hover examine does not.

This issue does not occur in ogre running, so I presume there is a fix, work around, or something in my code is preventing this. What should I look for? Has anyone experienced this?

 

[macker0407]

EQ2 rate limits the number of actions you can make that involve the client doing something. The most common example of this is server side calls(which item examining includes, until the item data is cached by the client). The fix is to avoid making these calls but without knowing the script or what it does, there's no way to know what the culprit in this instance might be.

 

[Kannkor]

EQ2 rate limits the number of actions you can make that involve the client doing something. The most common example of this is server side calls(which item examining includes, until the item data is cached by the client). The fix is to avoid making these calls but without knowing the script or what it does, there's no way to know what the culprit in this instance might be.

Massive server calls are a very, very, very bad thing.

Every time you do a server call, it logs it (which normally is fine, it's just logging everything that is happening).

Lets use a completely fake, made up number, and say an average (non-botter) uses 10 server calls per frame.
When running a script, you can easily exceed 1000 server calls per frame.

So you start bogging down the server to shit. If the server starts having issues, and someone needs to look into it, and they see someone is hitting the server 100 times the average, guess who they look at first?

The reason Ogrebot doesn't effect hover examining, is I've went through every single line of code, and there isn't a single server call in Ogre's normal routines. Not a single one. (I say in normal routines, because if you need to repair, you need to do 1 server call, which again is acceptable, but you don't have to check it 50 times per frame).