Jump to content

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

Sign in to follow this  
switch296

Kicked from ANZ 2 for Battleye Script Restriction #68... why?

Recommended Posts

Hey guys,

I'm being consistently kicked from ANZ 2 upon joining for Battleye Script Restriction #68 and I have no idea why.. it worked fine for me last night and there hasn't been any beta/day z updates on it since then so I'm rather confused.

Every other server lets me in just fine, even other AUSARMA ones (Anz 1, 3, 4, 5) so I'm really at a loss for what could cause this.. I've contacted the owner of the server, cm. , but haven't received a reply yet.

Any ideas on how to fix this issue?

Edited by Switch

Share this post


Link to post
Share on other sites

Im getting the same :/

Well makes me feel better knowing I'm not the only one :)

Share this post


Link to post
Share on other sites

its annoying cos every time i log into those servers plays fine for a bit but if i died and try to respawn it kicks me. i kinda wanna know whats going on there? lol

Share this post


Link to post
Share on other sites

A few people have contacted me on ausarma's teamspeak saying they are all having the same issue so hopefully whatever it is, it will be sorted out by cm. soon..

Share this post


Link to post
Share on other sites

Took me a while but i finally found out what was causing this.

Should be all fixed now.

Tell what fixed it? I'm having this issue...

Share this post


Link to post
Share on other sites

I had this a while back. I did absolutely nothing different & it went away after ~2 hours.

Maybe a problem on Battleye's end?

Share this post


Link to post
Share on other sites
Sign in to follow this  

×