So tickets from me:
- add admin password to config
- add possibility to run from LFS Master (not directly from server)
Other things are made very good and if someone knows basic of programming - they can do everything.
My next question is: will this work with nginx (is live stream of packets, so I'm asking), how many resources does this need to run on Linux (Windows eats too much and I wonna prepare PRISM and node.js hosting for applications like this one).
Oh, there. Sorry, I was looking in clientmanager.js.
The TV plugins looks nice. I didn't tried the livemap yet, but it can be best thing for 16h race this year. I'm going to host it if organizers will approve it!
EDIT:
TV plugin doesn't know what VIEW_CAM and VIEW_DRIVER is. I don't know why, but it don't read exports.VIEW_ variables.
You know what kind of service I am hosting - good quality and very cheap but ppl are still buying extra expensive service in another place and they have a lot problems with service availablity.
Everyone who made and will make layout: if you made sprint layout, send me it. I will choose best 15-20 layouts and will run server for each of them. Then (I don't have time), maybe someone will use it to make championship
Make global variable rip (race in progress).
Set it to 0.
If someone moves and it is in racers array and rip = 0 - kick.
When countdown reaches green light or pre-green set rip=1.
I can explain it you with algoritm if you don't understand (my english is bad)
What I mean is to avoid 8 apps limit connected to InSim at once. Propably we will need here additional packet to be created or to write plugin working like LFSW master server and connect to it like to LFSW InSim Relay.
I don't have time to do it now, but if someone will start it I can help him with problems.
Saving time for each node will take a lot of memory in big events and it's not possible, because InSim don't report same nodes for each car. If you drive fast InSim report e.g. 104, 107,112,116 and for another car 104,108,111,115.