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  
KField86

Server still kicking for script restriction (#98)

Recommended Posts

So, after the whole thing happened yesterday with battleye and the scripts.txt file being renamed to scripts_old.txt -- I finally got around to replacing that file with the one Dwarden told us to use. All is good. Scripts.log is recording data and A LOT of it. Great. Problem is, now all of a sudden we're being kicked for script restriction #98 again.

Is this issue still ongoing? Are other servers still experiencing this? It doesn't have anything to do with me using the working scripts.txt file again does it?

Share this post


Link to post
Share on other sites

It's kicking everyone from the server for the same thing. It's a Vilayer server so I can't upload it to the cfgdayz\battleye folder myself since I don't have permission to move files around. I can upload but not move it into the proper folder. Is anyone else with a vilayer server experiencing the same thing. I'm using the one Dwarden posted yesterday. I didn't update the remoteexec folder or anything like that.

Share this post


Link to post
Share on other sites

Actually. since I can edit those files, being scripts.txt createvehicle.txt and remoteexec.txt ... can I just copy & paste the new information in, while deleting the old stuff and it should work fine? I'm using the ones posted this morning for all 3 files. Will this stop the script restriction kicks? I wouldn't care if it's just doing it to one person, but it kicks the entire server at the same time.

I'll start my server up and see what happens.

Edited by KField86

Share this post


Link to post
Share on other sites

Did that. Not getting anymore #98 kicks or other false alarms, but man... lots of people getting kicked for remoteexec violations and even two guys for createvehicle restrictions. I take it it's doing it's job? :P They didn't come back lmao.

Share this post


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

×