For what it's worth, my server uses @dayz_lingor (@dayz_lingor;@dayz_lingor_island;@blisslingor) and it still doesn't work. It also shows the dayz version as 0.3 instead of 0.34 and launches normal dayz instead of lingor.
IP/PORT: 199.195.198.140:2332
Here's what I've seen - this is a vilayer mod string from a query:
Arma 2: Operation Arrowhead;Arma 2: British Armed Forces (Lite);Arma 2: Private Military Company (Lite);@dayz_lingor;@dayz_lingor_island;@BlissLingor;Expansion;beta
This is a normal server's:
Arma 2: British Armed Forces (Lite);Arma 2: Private Military Company (Lite);beta;Expansion;Arma 2: Operation Arrowhead;Arma 2;DayZ Lingor 1.7.2.5/034;DayZ Lingor Island v034;@blisslingor
I'm not sure where vilayer got their files from but as far as I know they aren't the official lingor files, the official files show that mod string. I think Vilayer and possibly dayz commander are they are the ones doing it wrong (if you got your files from vilayer, which I think is the case) not the other way around.
Can you please fix this? I constantly get complaints from people who can't connect to the server.
It looks like it's an issue with your server, it's not even in a "PLAYING" state.
... I assure you it isn't an issue with my server, it's not in the playing state because nobody has joined it since it has restarted - and even if it wasn't in the playing state it shouldn't matter to your program.
I have joined the server and started the map so that it is in the 'playing' state and as you can see the problem persists and the names of the loaded mods are the same.
Try downloading the official lingor files from http://dayzlingor.tk/ and you will see that it works the same on that server and many others that aren't hosted with Vilayer.
I bumped 4 threads on this forum that I found on the first page - they all have the same problem that would be fixed by what I explained:
https://groups.google.com/forum/#!topic/dayzcommander/Cr7eUJ2b4MQ
https://groups.google.com/forum/#!topic/dayzcommander/LmLi139cois
https://groups.google.com/forum/#!topic/dayzcommander/8Efvhlbdlq8
https://groups.google.com/forum/#!topic/dayzcommander/xPagM19k1FA
I'm encountering the same issue, I can connect just fine to my Vilayer Lingor server but am unable to connect to my bliss Lingor server using DayZ Commander. It constantly tells me I don't have the mod installed.
If I first launch into my Vilayer server though, then disconnect and connect to my bliss server it works fine and doesn't complain about the mod being missing.
Any help you can provide would be greatly appreciated.
Edit: initially I posted that my server was not displaying the "Playing" state in the in-game browser. That is incorrect, it is showing that state properly.
You are absolutely right - the files that dayz commander downloads are the same as the dayzlingor.tk official files - sorry about that. Whatever Vilayer is using to host their servers doesn't seem to be though.
This is what process explorer says were the launch parameters when you join one of the lingor servers that isn't working:
"C:\program files (x86)\steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta\arma2oa.exe" -skipIntro -noSplash -noFilePatching -world=empty -connect=199.195.198.140 -port=2332 "-mod=C:\Program Files (x86)\Steam\SteamApps\Common\ArmA 2;expansion;expansion\beta;expansion\beta\expansion;c:\program files (x86)\steam\steamapps\common\arma 2 operation arrowhead\@DayZ"
As you can see it's just trying to run it with normal DayZ and not lingor. The issue is not with a bad client side install of lingor, it's with a bad server side install.
Some servers say this:
Arma 2: Operation Arrowhead;Arma 2: British Armed Forces (Lite);Arma 2: Private Military Company (Lite);@dayz_lingor;@dayz_lingor_island;@BlissLingor;Expansion;beta
Some servers say this:
Arma 2: British Armed Forces (Lite);Arma 2: Private Military Company (Lite);beta;Expansion;Arma 2: Operation Arrowhead;Arma 2;DayZ Lingor 1.7.2.5/034;DayZ Lingor Island v034;@blisslingor
I don't know why, and I can't explain it, but if you could just update dayz commander to handle both of them this problem would go away.
Awesome, fix seems to have worked!