nightshift 10 Posted September 30, 2013 Sorry if this is the wrong area but i think its a sixupdater problem and not a (client problem with pws) i trying to host 3 servers in one repo with Sixupdater. my clients wanted to download it with pws (new 1 file version) i have set up sixupdater to work with arma3. my modpath is fine and the servers starting nice with this mods. But i am having issues with the repo manager. i have set it up tu us the current preset in repo manager. 1. SixUpdater (Repo Server) 2. Sixupdater Repo Manager 3. Sixupdater Repo Manager required Mods 4. Serverside Modfolder 5. Clientside PWS (current version) why does sixupdater only show 3 mods (and all other are arma2 mods) i wanted to add also 11 mods to the server not only this 3. whats "special" with this 3 mods? Share this post Link to post Share on other sites
sickboy 13 Posted October 1, 2013 Hi, Not all other are arma2 mods, I see arma2, arma3 and toh mods. The @gign folder and such should already be listed higher up, the mods in modset folder are not shown because they already exist officially on the network and higher up the list. The mods should also not be installed to a subfolder 'modset', that might cause some of the confusion, though normally when the mod path is set correctly in the arma 3 profile, it should not show up as modset/@.... If still issues, could best come and visit us at skype for support, details in the custom repo doc. Share this post Link to post Share on other sites
nightshift 10 Posted October 3, 2013 Hey sickboy, thank you for your help. It works now...only one problem left: pws doesnt process the bikeys. the bikey folder does only contain the a3.bikey so i cant join my (VerifiySignature2) protected servers. but in the downloaded modfolders [@modname] in a3 maindir are the bikey files. for some reason pws doesn't copy it to keys dir. Share this post Link to post Share on other sites
