Jump to content

  •  

Bug Tracker Migration

June 3rd
Good news everyone! The staff has decided that it is time to slowly kill off this Bug Tracker. We will begin the process of slowly migrating from this Bug Tracker over to our Github Issues which can be found here: https://github.com/HerculesWS/Hercules/issues

Over the next couple of days, I will be closing off any opportunity to create new reports. However, I still will keep the opportunity to reply to existing Bug Reports. Doing this will allow us to slowly fix any bug reports we have listed here so that we can easily migrate over to our Issue Tracker.

Update - June 7th 2015: Creating new bug posts has been disabled. Please use our https://github.com/HerculesWS/Hercules/issues tracker to post bugs. Users are still able to reply to existing bug posts.

- Administration

Issue Information

Issue Confirmations

  • Yes (0)No (0)
Photo

User Count Display

Posted by Hercules Bot on 25 December 2007 - 06:35 PM

Originally posted by Ancyker
http://www.eathena.w...ker&showbug=688

I'm not 100% sure when this problem started, but the user count (server select, /who, etc) is wrong. It happens after the server has been up for a while for unknown reasons. All I can confirm for sure is that it is a bug, it's happing to more than one server (by my count, at least 4 separate servers have reported it, others may not know why it's happening or might think they are real users), 1 of which is my server.

This is severe since people getting hosting pay per user and eAthena has no idea how many people are actually online (BakaRO was reporting ~260 people online in /who when ~8 people were actually online). Actual online value is displayed with @who, indicating it's clearly a problem with the current system. This bug has existed for some time, at least a few weeks, probably longer.

It's very hard to reproduce this in a controlled environment, I can't reproduce using only 2 clients. I'm suspecting time outs or some type of improper disconnects to be the problem, but it's just a hunch and I have nothing to support that.

If it can't be fixed, revert it back to the old system.

Originally posted by Ind
this was fixed in a previous eA revision [rev=12090]