Butt (DayZ)

One of the most WTF leg-breaking moments I've recently had was when scavenging the back room of a Supermarket when a zombie jumps through the wall beside me and the collision instantly broke my legs. This was before 1.7.7 but that's something I've never seen in my one year of playing DayZ.

ArmaA2 doesn't use blood, so how can one say that an A2 unit has 4500 blood? If there is a Captain Obvious amongst us, please lend me a hand.

Oh boy, I really am stumped then. I've tided up the initialization script a bit so it compiles its functions more like DayZ but I can't really see where it would cause connection problems. For the past 2 hours or so I've done nothing but connect and disconnect from my laptop DayZ server. I've found no connection problems so far, just crashes when I try to enter the server before my username appears in yellow in the join game screen. If you'd like to give it another go, here is the tided-up mission pbo. If it doesn't work this time, I'll try to continue looking but at the moment I'm out of ideas. Link to the pbo is below. http://www.mediafire.com/?j2g4fgkw9a78884

These two lines in your arma2oa.RPT seem suspicious: "DEBUG: loadscreen guard ended with timeout." NAT Negotiation failed (NNThink - result 2) A quick Google search about the second line seems to hint that the problem is network-related. I think you said that you can login just fine with a normal mission file, can you see if those two lines show up without any addons included? From the logs I don't see anything that says the addons are responsible, but I'm no expert. Also, the lines that start with Unrecognized... seem to be a normal part of DayZ. I see them in my logs all the time in normal situations.

Sorry to hear that you're still having troubles. Have you tried simply restarting the client and connecting again, or does it not connect no matter what you do? If the issue is server-sided scripting, it would be in your arma2oaserver.RPT in your server config files. If it's client-sided, it would be in your C:\Users\(Username)\AppData\Local\ArmA 2 OA\arma2oa.RPT (Windows 7, not sure about other OSes).

I don't know if this will help any, but here is a pre-packaged mission file containing the latest version of the AI addon (link at bottom of this post). It's the one that's used on my "test server" (it's basically just an old laptop) and I know it works. However, I noticed in your original post that problems started happening when other people tried to join in on your server. I simulated other people logging in by logging into my test server, exiting the client once I logged in, then opening a new client and repeating. From about 10 cycles of opening a new client and logging in, about 40% of them ended up in a crash-to-desktop. I'm not sure if this is an issue due to my laptop server's extremely crappy hardware, but you did not mention any crashing so I don't know if the problems are related. PBO link: http://www.mediafire...omcmc52zncovbzv Also, I tested out your own mission file and I don't know what was edited, because I had some really, really strange issues coming up. Like spawning in as a bird, or stuck immobilized in debug zone and unable to log out normally. The script I use to load the AI addon is pretty ancient, haven't changed it for probably 6 months now, so I may have to see what I can do to solve these issues.

Hello, I'm the creator of this AI script and I registered a new account on the forums to help out the OP. To the OP, I see that you've edited a few settings, have you tried to see if the same problem happens without changing any settings? I'm not sure if anything went wrong during your edits. Also, perhaps it is a good thing that something went wrong, because your "DZAI_randAddAI = 125;" line in the variables file will cause a huge amount of problems. I guess I didn't describe the variable enough, but this setting would cause a maximum of 5+125 individual AI units to spawn from a single trigger, and you have 25 total triggers. If you want a minimum of 2 AI + a maximum of 3 additional AI, you would set DZAI_randMinAI=2 and DZAI_randAddAI=3. I don't know if you'll find my reply since it's been 5 days since your last reply, but I will test out your mission file and see what's happening. I'm not sure what could possibly be wrong because I've dumped the DZAI folder into random mission files, done the init.sqf edit, and had no problems whatsoever running the addon within 5 seconds of moving stuff around.