There’s a pretty good tutorial for getting starter
https://ktor.io/docs/creating-web-socket-chat.html#what-s-next
It definitely doesn’t demonstrate best practices, but does teach you all the fundamentals. Namely, that there’s no inherent connection between multiple clients, and you’ll need to build that out yourself.
For a best practice when running websockets in production, you’ll just want to keep in mind that multiple clients might be connected to multiple server processes, so you won’t be able to store the game state in-memory as described in the ktor tutorial. You would need to store the game state in another observable system like Redis, so that all clients across all server processes will still see the same data and get updated in realtime. Redis has an example project showing how you might do this with Java/Spring Boot, which you should be able to translate to Ktor without too many changes
https://github.com/redis-developer/basic-redis-chat-app-demo-java