Jackson Snow

Don't know if it's been mentioned, but you can't search for terms shorter than four characters. In a game where the "map" is a big deal, you can't search for anything on how to for example "disable map" in your missions.

We've been playing and enjoying the inbuilt Sabotage mission, however we have a couple of questions, mostly relating to the safehouses. It seems like every time we set up a safehouse, immediately the message comes saying that it has been detected by the enemy and they will attack within 30 minutes. Are we doing something wrong, or misunderstanding something? The description makes it sound like setting up safehouses is a core part of the mission; is it intended that they are always immediately detected? And then, about five minutes after the safehouse is set up, enemies will come along and blow it up - this happens every time so far. So the safehouse gets ruined. Is this because we are choosing poor locations for the safehouses, or doing something else wrong? Essentially, it seems like the safehouses are not very safe for us; they are always detected and attacked within minutes. And to make matters worse - if we have set the safehouse as our respawn point, and we die, then it will always be surrounded by enemies, and often we will be unable to leave as we just keep dying. And if we don't set up safehouses then it quickly gets very annoying having to drive / walk from the initial spawn point to wherever we have to sabotage... Some suggestions would be good! Thanks.

There are some templates in the demo subfolder of @Alive - it says single player and multiplayer, but I think the multiplayer one I've played with would definitely work for single player (maybe toned down in numbers slightly, perhaps).

Yes, I preferred the older one too. There's something that I disliked about the newer one that I can't put my finger on. The rest of the sounds in the newer video are great, though.

Just checked mine and same problem here. I tried to report it through the application, but no idea if it was successful.

Have a look at Alive, or RHS (just a couple of examples - there are tons more!).

I think if you read the first post you might have your answer... You could try using the Virtual Arsenal - it allows you to create custom loadouts which you can save, and so on. It's quite nice.

You have to modify your files manually. Then tick the box which says "Launch as is" and it won't overwrite your files. But yeah, the tool is pretty broken now unfortunately.

If you edit the config you can tick the box "Launch as is" and it will not overwrite the config before launch. This if the only way to get TADST to work with headless client now, that I know of.

Same problem here. A similar thing happened with VAS, but we stopped using it and went over the the Arsenal instead. No idea how to fix it - perhaps it is looking for the wrong icons or something?

I think the link is http://www.rhsmods.org/updater - it's working for me now.

It doesn't help much if you're too lazy to bring a list of which mods you're using... Try running the game without your other mods, and see if ASR AI causes them to kill you in one hit; then, add your other mods, one by one, and see which one in combination with ASR AI might cause this effect...

Try without any of your other mods, and then add them one by one until the error returns, and report back which one causes the error to return... It'll greatly help the author if you do this :)

I think that has to go in description.ext rather than init.sqf (someone correct me if I'm mistaken).

Download speed is good here (~8.8 MB/s). Thanks for all your efforts getting these quick releases to us rather than delaying it over longer periods.