[Fixed] MMS HUD displaying incorrect exp/hour rate

[Cisco]

after dieing its normal, i had simmilar situation but it happend cuz bot counted time 2x longer then hunt itself

30 minutes later

[Mateuszp]

hmm my bad i putted it in sentence. After diening its normal it geting buggy happend all the time, same after save server.

I was answering @topic that he had 2 times less cuz bot in my situation was turned on for 3 h and i was hunting 1,5h that makes it showing corectly even compared to tibias eph - witch showed hunt eph

[Lucas Terra]

this?



After he dies and go back to hunting

The value showed in $exphour is the session average, meaning it's the total exp you made since you logged in your char divided by the time you've been playing.
I'm adding a $clientexphour, which will do the last 15 min average, like the game client does.

[Cisco]

Very good, congratulations for the great work and attention. /// Muito bom, parabens pelo otimo trabalho e atenção.

[Raphael]

The value showed in $exphour is the session average, meaning it's the total exp you made since you logged in your char divided by the time you've been playing.
I'm adding a $clientexphour, which will do the last 15 min average, like the game client does.

That's a breaking change then and should at least be documented. Because on Tibia 10, WindBot reports the client's exp/h rate on $exphour.

[Lucas Terra]

That's a breaking change then and should at least be documented. Because on Tibia 10, WindBot reports the client's exp/h rate on $exphour.

Uh, yea... you're right.

[Raphael]

Uh, yea... you're right.

I believe the appropriate course of action here would be to leave $exphour reporting the client's exp/h rate and add another variable for a "real" exp/h rate. I know $clientexphour sounds better, but I believe keeping backwards compatibility is more important.

This might (and most likely will) even cause problems such as complaints like "my script makes more exp/hour on Wind for Tibia 10 than on Wind for Tibia 11".

What do you think?

[Raphael]

This should be fixed as of beta 31.