Thanks —, I tried it a couple of days ago, connected the computer to the TV with apple-tv and gave my sons a smart phone each as a controller and it worked well. They are only 2 and 5 years old and I manage to keep them playing for a good two minutes, which is something like 2 hours in grown-up time
I've done everything from scratch so I'm not using anything from superhappyfuntimes, mostly because I felt C2 had all the needed parts all ready.
Anyway, this is how I've set it up so far. There are three components:
- Main game: made with construct 2
- Controller: made with construct 2
- Nodejs server, to connect the main game and the controllers
A user downloading the "package" should not have to care about the nodejs server (unless they want to). But they will have to start the nodejs server on their local computer.
The controllers will send simple input instructions to the websocket server which the server will send to the main game. The main game has "functions" like "Joined", "Dropped" and so on. A user could add new actions to send from the controller and add support for interpreting those in the main game without having to modify the nodejs websockets server. So all modifications will be done in construct 2.
The controller and the main game would be pretty simple to change. All the coding will be done in the main game (unless you want to add new actions from the controller). But if you would like a user to loose hp when another user bounces of their head that would be normal event based coding in c2 in the main game.
I'm currently working on another construct 2 project and just did this for fun, but it there are more people interested I will of course try to make a beta release of "this", codename CrowdGaming
KFC yes but adding the need for a nodejs websockets server. The reason I looked into this from the start was because I was disappointed to find out that ios did not support webRTC which means there is no C2 multiplayer support on iOS, so I started investigating alternatives ended up with websockets did a multiplayer game with a nodejs server hosted on a amazon AWS micro instance had too much lag and figured it would be better on LAN which it was.