Rupture

ok that makes sense to me. I was attempting to save disk space by using the mod folder within my arma 3 folder also as the repo. I see that wont work, as if i were to select the whole arma 3 folder (in order for arma sync to get the @unitmods folder) it seems it would pickup ALL of my mods... A bit of a pain to have to double how much space is taken up on my hard disk to have the mods in arma, and also in a separate repo folder. Not really complaining, just hurtful on a small capacity SSD drive. Anyway, I understand the instructions, matching folder names of repo on local and remote, and whatnot. Thank you for the clarification.

I can do that. I've selected a folder on my computer as a repository, built the repo, and uploaded it. The autoconfig URL doesn't point to the right place on the server that it was uploaded to, through arma sync. Aside from that, it didn't keep the name of the folder of the repo folder, it just grabbed the addons folder. so on my computer I selected a folder named @unitmods within that is the folder named addons, and in there all the pbos like it should be. in my server i placed a folder called modpack and pointed the arma sync at it. when i go look inside the modpack folder, i only see a folder named addons, not the @unitmods folder with the addons folder inside it. edit: additionally, when i create my own autoconfig URL that points the the correct place, i can connect to it initially. As in if i were to give you the URL, you would get the server info, and have the server info, name, etc. However when you hit the connect to repository button, and hit check for addons, i get a 404 error, and i can see that the url it is attempting to connect to is again, the wrong URL.

Would it be possible to get a detailed walkthrough on how to get a repository working for those of us that have to build the repository on our own computer, and then upload it to the server. Its quite confusing and frustrating trying to figure this out.

Love the sounds so far, looking forward to the release of this mod. Dont worry if not everybody is happy with it, cant please em all!

Having a similar issue to Dark Spectre, PM sent.

Any chance to see a 100 round Beta C mag included with this in the future?

I'm having an issue getting my headless client to connect to my server. I have an arma 3 server hosted through Jest servers, and its up and running fine. I have followed the horrible bread crumbs of documentation on how to setup my main server, and missions to accept a headless client. I have edited the pbo to include the following in a civillian slot for the HC: I've also added this command into the server.cfg: localClient[]={127.0.0.1}; So as far as I've been able to determine, everything server/mission side should be setup to accept the headless client. my command line in the TC admin for the HC is as follows: -client -name=HC -nosound -profiles=HC -connect=XX.X.115.132 -port=2302 where my server is at the same IP and is on port 2302, the HC is on port 2402. This is how things are at the time of posting this _________________________________________________________ I have Edited the server.cfg to change the following from: localClient[]={127.0.0.1}; to: localClient[]={XX.X.115.132:2302, XX.X.115.132:2402}; with no HC attempting to connect and have since reset the localclient information back to what it was before. Since the server and HC are on the same ip, just different ports, should I be using the 127.0.0.1 is in the -connect= area? I would try this, but the TC admin is a POS and i pretty much have to send in a support ticket to get a proper command line made.