When on a servers lobby, the player count displays the current players x3.
Description
Details
- Severity
- Minor
- Resolution
- Fixed
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- Server
- Join a multiplayer server
- Check the amount of players on
- See the "Listed Players" - It displays 3x the real number
Correct Player count as per steam: http://i.imgur.com/ZV5DgzT.png
ArmA 3 Server lobby: http://i.imgur.com/iUHNJCM.png
Related Objects
- Mentioned In
- T120372: Listed Players in lobby incorrect
Event Timeline
This seems to be an unintended side effect of making the player list a child of RscListNBox, instead of the old RscListbox. when calling lbsize on a RscListNBox the actual output is rows * columns. This can most easily be fixed by updating the display script to take the columns into account.
a3\ui_f\scripts\gui\rscdisplaymultiplayersetup.sqf (lines 23-30)
_display displayaddeventhandler [ "mousemoving", " _display = _this select 0; (_display displayctrl 1015) ctrlsettext str (lbsize (_display displayctrl 114)); " ];
Should look more like (3 is hardcoded here, but we can probably find a better way to pull the column count):
_display displayaddeventhandler [ "mousemoving", " _display = _this select 0; (_display displayctrl 1015) ctrlsettext (str ((lbSize (_display displayctrl 114)) / 3)); " ];
This can be fixed (while waiting for this to be patched) on the client's mod side example:
https://github.com/BourbonWarfare/POTATO/tree/master/addons/fixPlayerCount
The provided example has CBA/ACE dependencies due to using some of their macros, but if you want to put together a simpler fix you can just use a config tweak to have the RscDisplayMultiplayerSetup display load your own custom script that has the correct values.
Hello,
thanks for the feedback. Issue should be fixed in the next Dev branch update and of course later in Stable/Main branch.
Thanks
Can confirm, player count displaying properly on dev build 1.65.138842 . It looks like it was fixed by using lnbSize (good solution, for some reason I couldn't get that to work when I tried).