-sc-

For anyone having the issues regarding your server NOT showing using the in-game serverlist while having verifysignatures=2 or verifysignatures=1 Other issues regarding this problem: While the above problem is happening, The server will show up if added using remote button, When a player connects he will hang at "Wait for host" indefinetly. Possible other undocumented issues caused by this. The server will show this error in the RPT: NetServer::finishDestroyPlayer(605910197): DESTROY immediately after CREATE, both cancelled Possible Causes: 1. Windows file permissions! 2. Corrupted/Bad .bikey files Possible Issues: 1. The key files do not have proper permissions for the Windows Account that the server exe is being run under. This causes the server exe to start normally with the problems I stated above ^^ 2. The key files are corrupted or for some reason they are not compatible with 1.63 Solution 1: Delete all user-added .bikey files from the keys directory/folder leaving only bi.bikey and bi2.bikey, Run the server, see if it works. If this works, you will need to add keys 1 by 1 or in small batches to determine the trouble maker. Personally, a combination of the 2 solutions worked for me, I ended up finding 1 user-added .bikey file that was causing these issues to occur. Trouble Makers (Filenames): ibr_panthera29.bikey Solution 2: Right click keys folder, click properties, click Security tab, Click Advanced button, Click Change Permissions button, Click the Owner tab, Click the Edit button, Select the account your server exe is run under, Tick the "Replace owner on subcontainer and objects" check box at the bottom, Click apply, Click yes on any prompts. Attempt to run the server again, it should have the proper permissions to access the key files and the server should operate correctly. (If needed, You may want to repeat the above solution for the root Arma folder, this way all files inside the folder should have the proper permissions) Additional Notes: This problem did not appear to occur before the 1.63 major push to stable, only after updating from 1.62->1.63~ This has not been confirmed on Linux Dedicated. Solution 2 is mainly for people whom have direct access to their server box or are hosting on their home machines etc.. If Solution 1 does not work for you and If you host from a server provider/GSP contact them with solution 1 and I'm sure they can fix your issues, otherwise poke around your control panel for some form of repair file permission/repair account options. System: Windows Server 2012 R2 Arma 2 OA Version 1.63.125548 Cheers -sc

Did you by chance pull this from the SOTG Edit of Ahoy Worlds Invade & Annex? If so, I take credit for this modification :) the code is eerily similar to my modified pilotcheck.sqf with slight differences. Edit: If interested, I have another vehicle restriction script I wrote that uses a trigger to check when a player enters a vehicle, if that vehicle matches a defined list of classnames & UID array, it then boots them out with a hint. If they passed the check, they are greeted with a welcome hint. Also: The current modified version running on our SOTG Edit works for co-pilot seats as well (I had an issue where people could take control as co-pilot without the pilot unlocking controls, aka everyone flying stuff they should not be.) We use this in order to restrict Attack Helicopters to Members/Friends only, as every Joe schmoe jumps into them if they can.