-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fall back to parsing the log for the player count #14
Comments
Hey, thanks for the request. I could try to adopt it with my bash scripts. But I don't know how robust the logic is. It reads the service logs to count every join and exit of a user. I hoped we get some kind of rcon, so I could get the information strait from that and also do server messaging, to alert users of an upcoming restart. But I will try fiddling around with that and report back. |
Thanks for the image, it's been working quite well for me. Using python-a2s and a simple |
Thanks for the suggestion. I added the python-a2s script to check for connected players locally. I removed the I'll test it a bit further and merge it afterwards. |
@opello If you want you can check this feature with the latest |
Thanks! I updated and will do a better test later, but it seems to work: # PYTHONPATH=/home/enshrouded/.local/lib/python3.10/site-packages python3 -c 'import a2s; print(len(a2s.players(("127.0.0.1",15637))));'
0 |
Released with version 0.4.0 |
Is there an existing issue for this?
Feature description
A rust implementation of a tool created to track currently connected users was posted in the Enshrouded Discord:
https://github.com/jcjolley/enshrouded-player-count
It seems like either using this directly (if sufficient) or adopting the parsing logic put into it to track the player count locally instead of querying the Steam API might be nicer to avoid updating while players are connected.
As I was writing this up it occurred to me that it might be simpler to query the server directly (using the query port) but I haven't looked for an implementation of that yet.
The text was updated successfully, but these errors were encountered: