jr-k
[FEATURE] Optionally append hostname to studio_url for player identification and auto-registration
Is your feature request related to a problem? Please describe. Currently, it's not possible to easily identify individual players or clients in the Studio interface. This makes it difficult to distinguish between multiple instances, especially in environments with many devices.
Describe the solution you'd like Add support for optionally appending the hostname of the player to the studio_url (e.g., STUDIO_URL=http://localhost:5000?hostname=$(hostname)).
This hostname should be visible in the Studio under both the "Players" and "Clients" overviews.
When a new player connects for the first time, it should automatically be added to the "Players" list, potentially in an inactive state, to allow for configuration completion.
Describe alternatives you've considered Manually tagging or renaming each player in the UI, or modifying the player config manually, which doesn't scale well for large deployments.
Additional context Shell snippet for appending the hostname:
STUDIO_URL="http://localhost:5000" HOSTNAME=$(hostname)
if [[ "$STUDIO_URL" == ? ]]; then FINAL_URL="${STUDIO_URL}&hostname=${HOSTNAME}" else FINAL_URL="${STUDIO_URL}?hostname=${HOSTNAME}" fi
This would greatly improve clarity and management in multi-device setups.
Is your feature request related to a problem? Please describe. Currently, it's not possible to easily identify individual players or clients in the Studio interface. This makes it difficult to distinguish between multiple instances, especially in environments with many devices.
Describe the solution you'd like Add support for optionally appending the hostname of the player to the studio_url (e.g., STUDIO_URL=http://localhost:5000?hostname=$(hostname)?hostname=$(hostname)).
This hostname should be visible in the Studio under both the "Players" and "Clients" overviews.
When a new player connects for the first time, it should automatically be added to the "Players" list, potentially in an inactive state, to allow for configuration completion.
Describe alternatives you've considered Manually tagging or renaming each player in the UI, or modifying the player config manually, which doesn't scale well for large deployments.
Additional context Shell snippet for appending the hostname:
STUDIO_URL="http://localhost:5000" HOSTNAME=$(hostname)
if [[ "$STUDIO_URL" == ? ]]; then FINAL_URL="${STUDIO_URL}&hostname=${HOSTNAME}" else FINAL_URL="${STUDIO_URL}?hostname=${HOSTNAME}" fi
This would greatly improve clarity and management in multi-device setups.
Hey 👋 thanks for the detailed request!
Good news, the tagging part is now live on v2025.5.4. You can now tag players with things like hostname, geo location, etc., which should make it way easier to keep track of who's who in the Studio.
Auto-creating players on first connect isn’t there yet, but this is already a big step forward for managing lots of devices.
