Twix

Signature check timeout is not usually due to connection but to your own (client side) HDD performance. It's easy to check what bottlenecks too, simply open your performance meter, select the arma3.exe thread and see the read/write done when you connect to a verifysignature server. Your HDD will go literally NUTS over this, pumping max read capacity (and over, in my case) on the large files (usually sounds.pbo, a 2gb file...) and if unable to cope with the timeout reqs, you'll get kicked. I highly recommend disabling anything that could slow HDD access in anyway, shape or form (and exlucing arma3/addon folder from you antivirus/firewall/whatnot), setting arma3 on high priority and, above all else, NOT doing anything whatsoever for at least 30 seconds after joining the server. Personally my HDD isn't new (far from it) but I have a good connection. If I do ANYTHING when it's checking, I'll get kicked every time. If I don't, I'll get in every time. The WORST thing is when another high priority process requires HDD access at the same time....that'll get me the boot, no exception.

One answer for now: Verifysignature = 2; in your server.cfg file. Any server not using this and without an admin present 24/7 WILL be "hacked" (usually a script kiddie using someone else work) at some point or another.

1) create a text file somewhere. I'll use aparam.txt in the c:\armaparam directory for this example 2) put your -params in there, for example 3) edit your arma shortcut into this: (use your own path if different of course) "C:\Steam\steamapps\common\Arma 3\arma3.exe" "-par=C:\armaparam\aparam.txt" All done. From now on, you just need to change the text file and not mess up any other shortcut. I don't think there's a character limit either.

This is my =BTC=_revive_init.sqf: PARAMS_ReviveMedic is a map parameter I use to switch between "Anyone can revive" and "Only Medic can revive" depending on how many people are on the map. I use a custom Annex & Invade map for 20 people. I have 2 squads set up, Alpha and Bravo. Each has 2 B_medic_F slots. I also use this at the end of the =BTC=_revive_init.sqf file instead of the normal hint to check if the parameter is properly activated and this works perfectly.

First, great mod! Really 100% needed for most missions and helps keep immersion overall. Thanks for that. Now, I've been trying to use the Medic only settings to limit who can revive (and give medic something to do). I haven't tried yet with the latest release but it was working fine with just one medic per squad before. However, I have set up my map with 2 squads of 10 people and 2 medic slots in each. When I did this, nobody could revive whatsoever. I've been looking through code but just can't find what's wrong there. Since there's not "first aid" action whatsoever, I'm guessing it's somewhere in the BTC_is_class_can_revive function but the only potential problem there is the foreach (since there are multiple) but I don't get why it wouldn't work the way it is. I'll try again today with the newest version and post how it's going though if someone else figure this out, please post here :) Thanks

You need to add the PRC343 to the object backpack of the player (which is a cargo I believe), not to the player directly. Something like this might work, can't test it just now? myBackpack = unitBackpack player player addItem "ACRE_PRC148"; myBackpack addItemCargo ["ACRE_PRC343",1];