/who command limit

[Arheos]

Did you notice that after the server update the /who command displays only the first (?) 31 players?

[Karyuu]

Should be only 30, actually, but I haven\'t had the chance to see this myself :> Is there a way to view the next 30 with another command or somesuch?

[Nilrem]

it\'s 31, because:

 for (Client* curr = i.First(); curr && count<=30; curr = i.Next())

since the first one is 0, from 0 to 30 there\'s 31. You could just show 30 making count<30.

I was talking with Bodacher, the other day, and he also poked me about that fact, and perhaps the chance of recalling the function so it displays the next 30 players and so forth.

http://planeshift.oodlz.com/bugtracker/bug.php?op=show&bugid=1240

Here I tried to post about not fully closing the bug, since there wasn\'t all the players displayed, and the cause wasn\'t yet found, but seems that this workaround is the one that will be.

[Arheos]

Well sorry I didn\'t check the bug tracker. But before this thread is probably locked, what\'s the web interface?

Edit: Alright thanks. I never visited that exact link of the laanx site. Thought it was another just numbers stat page... alas...

[Karyuu]

Nah, threads don\'t get locked so easily :) Worry not.

The web interface is this page on the fragnetics website listing everyone currently online. There used to be a link to this on the main page (laanx.fragnetics.com, that is) but it was removed for whatever reason. Probably should be linked back up.

Regardless, limiting /who to 30 players only with no way to scroll for the rest is a rather funny thing. I\'d like a small addition to let you view the next batch of 30, and so on and so forth.

[Godfrey]

Whenever I do a /who, it shows an alphabetized list of 30 characters, then an alphabetized list of 30 different characters, and so on until it\'s shown them all.  Or at least it did a couple of weeks ago; I haven\'t tried it since then.

[VMann]

and now (since the update at weekend, i think) it shows only 31 players. that\'s what the whole thread is about

[white_slayer]

its got something t odo with the server update i think its intentional (pretty sure)

[neko kyouran]

Yes, it was intentional.  Please read your documentation about things that get updated and worked on in the future.  Thank you.

Taken from the file:

\"*** 2006-01-15 by Andrew Dai
- Fixed an issue with items being cloned by EquipIn() because they were dealt
  with twice consequently corrupting the PoolAllocator item allocation pool and
  allowing use of deleted items.
  It is essential that EquipIn() does not dispose of the object on failure.
  This is a TEMPORARY fix, unfortunately the code\'s poor design means this whole
  system must be rewritten sooner or later.
- Fixed the issue that psItem::transformationEvent is not initialised when a new
  psItem is created.
- Added a limit of 30 players shown through /who.
- Increased the performance warning threshold to 500.\"