arthuro555
From what I can see on the Construct3 documentation[2], they seem to be roughly matched in terms of features:
Both are authoritative with a host-client architecture, both allow using WebRTC DataChannels for UDP connections, sending messages, synchronizing objects & instance variables automatically, and using a relay with rooms.
THNK has some features that Construct's multiplayer also does not seem to have. For example:
- THNK is fully network agnostic[3] through a network adapter system (you can easily implement an adapter for another networking method in a few lines). Using the geckos.io adapter, you can connect to a player on the LAN via an IP address, even if offline, instead of requiring the presence of the signaling server for a connection to happen.
- Games made with THNK work in single-player normally by default. It only becomes multiplayer once you connect to/start a server via an adapter.
But Construct also seems to have features THNK doesn't (yet) have. For example:
- Listing rooms (when using the THNK Rooms adapter)
- Expressions for stats
- Local input prediction
Hence, I think of them as roughly evenly matched.
Disclaimer: My claims here are based from the information I read on [1]. I have not used Construct multiplayer before and might very well be wrong with this comparison. I would be happy to be proven wrong.
[1]: THNK Documentation - https://thnk.cloud/ [2]: Construct Multiplayer Documentation - https://www.construct.net/en/make-games/manuals/construct-3/... [3] THNK Adapters Documentation - https://thnk.cloud/docs/misc/picking-an-adapter/