I’m looking to make the Socket-Mucklet interface for those who love screen+tf (or tmux)
I’ve done a Telegram conversion bot for FurryMuck before, and would like to do something similar. I hear that some furs might be looking to do TF as well, so I found some motivation to get started on this.
Read up on resgate, been looking at the wss comms, looked at the dev resources, and I seem to be stuck somewhere basic. Auth. How can I get a bot token to get me started?
Thanks!
Oo! Neat! (And welcome to the forum! 
)
What language are you using?
Kotlin. I’ll probably be doing a lot of things from scratch.
I have very little Kotlin knowledge, to the point where I am not sure if the C# or the Javascript library of ResClient is best to look into when trying to write something similar to Kotlin.
The issue with the API is that the protocol is not trivial in itself. Yes, if you have a ResClient library that implements the RES Client protocol used by Resgate, then it is quite simple to do things with the API, using the library. But without such a library (I haven’t written one for Kotlin), you first need to implement that one that speaks the protocol.
But, if you give it an attempt, I am happy to help as much as I can! 
I saw from a screenshot that your protocol version handshake looks good.
Next step would be authentication.
After that, fetching the resources (the bot-model).
And then handling incoming events.
Just tell me where you want help!
Feel free to poke me as well, I did two implementations of res from scratch now and I know a couple things that you might want to be on a lookout for.
Although kotlin has a GC, so you will mostly dodge those by the virtue of not caring about allocations.
@Accipiter I have the full oauth going on and passing the cookies over to wss, persistence of cookies to avoid doing a full handshake every time. Protocol and auth method call all work! My next step will be to actually implement a full ResClient, and the C# library seems like a good place to get the logic and DTOs. Once I have that, I’ll probably start implementing the game logic.
@farcaller Yes! I’d love to hear what pitfalls I should avoid for!