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

kaspermnielsen

Kick for Public Variable Restriction #0

Recommended Posts

On EVERY server i get kicked for this. Can't play the game. Very annoying. Does anybody have a clue or solution?!??

Share this post


Link to post
Share on other sites

It's an issue with the login process that's throwing this error. I'm sure Faco will have a fix for it very soon, if not already. I'll check with him now to see if the filters have been updated--or if he knows a fix.

It looks like this on the server-side:

13.06.2013 00:10:03: PlayerName (IP) GUID- #0 "dayzLogin" = ["PID",<NULL-object>]

Share this post


Link to post
Share on other sites

It's not really an issue. dayzLogin does not exist anymore.

You get kicked from a 1.7.7 if you are using 1.7.6.1 client files.

All players need to update to 1.7.7.

  • Like 1

Share this post


Link to post
Share on other sites

It's not really an issue. dayzLogin does not exist anymore.

You get kicked from a 1.7.7 if you are using 1.7.6.1 client files.

All players need to update to 1.7.7.

THIS^^^^^^

most of the kicks have been people not updating dayz, commander should now clearly indicate you need to update dayz now.

EDIT : also remember to download the stable arma OA beta patch in commander settings menu too

Edited by Ninja_Meh

Share this post


Link to post
Share on other sites

×