Been a while.
I just fixed the .DAT issue regarding semi colons... More work to come.
Okay time to beef up the link between HQ and OYS.
Eric and I have been working on an authentication system for YSFHQ. Eric did the YSFHQ serverside of things, and I did the C# application side of things. OpenYS now has a dedicated API Key for use with linking with the YSFHQ service! This API Key will be embedded in the binaries (compiled, unreadable, would take quite the hacker to uncover it!) and will NOT be included in the source code releases! If you would like to extend OpenYS and use your own YSFHQ Auth Service, please speak with the developers here at HQ. Now, in the tragic even that my API Key is stolen, only the local database on your PC could be compromised with this information. In the past, I'd just store the password plain text but now this is no longer necessary - but even if my encryption is broken, no real damage is done as the only password stored on your pc is your own.
My idea is to create a new YSF Launcher that runs in the system tray. The program will launch your chosen YSF install, plus prop itself up as a proxy server on 127.0.0.1:7915. YSF will be launched to auto-join the proxy server object, and from there, it will prompt you which server you wish to join from the list of frequent servers (taken DIRECT from your YSF settings!). Just like the ysflight console server, you just type in the number of which server you wish to join (or the name of the server) and voila, the tray application will connect you.
But wait, there's more!
Using the extended protocal, I'll be implementing a handshake system where clients connecting with the tray application will connect to OpenYS Servers via UDP (stock YSF Server will maintain TCP). So the lag should increase a tiny amount with the proxy, but decrease a LOT with the UDP!
Whats that? Even more
I've got back onto the OYS Webserver (openys.ysfhq.com) and I'll be using PhpMyAdmin to start setting up a MySQL user database, having learned a bit of SQL at the end of last year. The UserDB will be very simple: Primary key is the users HeadQuarters UserID number - which will be taken direct from the authentication process - no impersonating others! And everything else stored will be OpenYS stats: I will be adding TotalFlightTime as the first and only variable, but I'll be expanding this to cover much more stats over time. My plan is to have a central database service for OpenYS and YSFlight. You want to earn flight hours while playing on a STOCK YSF Server? With the OYS Tray you'll be able to do just that!
The final step in the great database linking of 2016 will be to integrate with YSFHQ a bit more - show off your stats in your signatures with a PHP generated image.
2016 will be a big year for OYS with some major, game changing additions:
- OpenYS Database Service - track your stats and the stats of your friends!
- Player vs Ground - Ground Objects will be improved, and they will attack you!
- Player vs Player - Playing against other pilots will increase your kill/death ratios!
- OpenYS Tray Notifications - You can chose to be notified when certain players join certain servers.
Now that the server is relatively stable, it's time to start pressing forwards with some major additions!
I am an accountant working full-time (and some). I'm not here as often as I would like to be. Send a message if you need me. There are a few people in the community who can get in contact with me urgently if you need - don't be afraid to ask. I just don't check here as frequently as I used to. Sorry!