The problem with all of those third party solutions is that they don't allow you to write the server-side code with construct 3
Also most use websockets which is slower than the webRTC implementation construct 3 uses (construct 3 uses websockets to establish it's webRTC Connections but webRTC does all the work)
I find it baffling you people suggest worse 3rd party solutions over our wonderful built-in officially supported multiplayer, enlighten me on this if you may
But now with Construct 3, people mostly gave up on the multiplayer plugin and went for the alternatives like customized plugin, customized back-end, WebSocket System or 3rd party plugins like Colyseus or Photon Cloud / Server.
People didn't give up on anything, you just told people to give up on it and and the people trust you