Closed FlorianSW closed 1 year ago
Ah yeah, that is something I did not account for indeed. The real issue is that the game server does not tell us beforehand the amount of bytes the response will be in size. I suppose in this case we could tell whether the response is complete or not since we know the size of the array, but that's not something I ever really thought I needed in the first place.
To resolve the same issue with the showlog
command, I simply wait a second for more packets to accumulate. The same could in theory be done here, by passing multipart=True
to HLLRconProtocol.execute
. But since we don't use the VIP information it might as well be skipped entirely.
If we later need this information for something, it would be easy to re-add it, too 👍
This might not be the case for most event servers, however, when looking at the general use cases this tool might to offer, I still want to raise the issue. Our server benefits from a VIP share program of big german clans, hence our VIP list for the server is massive (over 800 entries). This seems to make the log utilities to raise an error when trying to read the response:
I think this is very much the same as #1, so not really much we can do about this issue (please correct me, if my analysis is wrong). However, what I wonder in the first place is: Why do we need to fetch the VIP status in the first place? The field (
is_vip
) is not really used anywhere, not even in the output logs (as far as I can see).For the sake of simplicity and to make this working with our first server as well, I would simply remove this call to get the full vip list? Opinions?