Saiboogu

That was the problem, I was working with a file provided by the DayZ team. http://imgur.com/ihdvS Just wasn't the right one, evidently. My co-admin found the real up-to-date file somewhere last night, I'll find out where when I talk to him this morning. Can you answer my question from the other day please? Having trouble reconciling the restriction codes with the lines in the file - they don't usually add up when I try to compare them to what gets logged, so I imagine I'm counting lines wrong somehow.

I had to reinstall the beta, DayZ, and Hive with my host and it finally started rejecting the scripts.txt file, so I can agree that that file doesn't work. Problem is, it also rejects the old 08-08 update I was using previously, as well. Seems something else has changed with the syntax, or there's a bug.

You're right there. That's what I get for trusting a file provided to me from a DayZ dev would be any more trustworthy than the dozen other random scripts.txt pastebins. Thanks, I'll make that change and see what happens.

Battleye didn't reject it on my side, though I don't have any logging yet. It's only been up briefly, I'm still assuming for the moment that no-one tripped any detections so far. I wasn't provided with the full cfgdayzdefault.zip file - I had put a ticket in with the devs asking if I, as a managed host admin, could get access to the files for the latest scripts.txt. They said sorry, no - but here's the scripts.txt file at least.

I just got this a few minutes ago from a dev when I requested the latest. http://pastebin.com/0M0dNWPf

Is this a firm line-by-line match of the file or does it skip commented out lines? Does //new count as line zero, for instance, or is it ignored?