Jump to content
Omaran

BattlEye: CreateVehicle Restriction #1

Recommended Posts

Seeing a lot of kicks for this tonight, anybody else seeing this?

  • Like 1

Share this post


Link to post
Share on other sites

Yeah I just started joining and it's been kicking me from a server I joined about 20 minutes ago now its constant kicking can't even join the server and it's the same BattlEye #1 restriction

Share this post


Link to post
Share on other sites

Im assuming its not player related, restarted my server and it let me join back after continuously getting this error. Possibly a bug in the latest dayz.

Share this post


Link to post
Share on other sites

Server updated today, The problem has been eradicated... Just like the zombies :D

Share this post


Link to post
Share on other sites

Look at createvehicle.log

You will see it is "seagul" realated.

Comment out "seagul" line in createvehicle.txt and profit.

Share this post


Link to post
Share on other sites

Ok so i have spent about an hour trying to do this "comment out seagul" line in createvehicle.txt" but for the life of me i cant find where i actually do this. Im not good with these sort of things. I cant even find a createvehicle.txt thing on my pc, i cant play dayz atm because i keep getting kicked for the battleye createvehcle restriction #1. any help would be appreciated.

Share this post


Link to post
Share on other sites

Ok so i have spent about an hour trying to do this "comment out seagul" line in createvehicle.txt" but for the life of me i cant find where i actually do this. Im not good with these sort of things. I cant even find a createvehicle.txt thing on my pc, i cant play dayz atm because i keep getting kicked for the battleye createvehcle restriction #1. any help would be appreciated.

It's a server file

Share this post


Link to post
Share on other sites

The fix for this is... for server admins..

Find your battleeye folder on the server and edit the createvehicle.txt, find where it says

5 "SeaGull" 

and edit it to where it looks like this instead

//5 "SeaGull"

the // remove the action (5 which is log and kick)

You also may need to go into your battleeye config.cfg file and scroll to the bottom to where it says


createvehicleURL=http://dayz-community-banlist.googlecode.com/git/filters/createvehicle.txt
createvehicleUpdate=true
createvehicleScan=true

and make it


//createvehicleURL=http://dayz-community-banlist.googlecode.com/git/filters/createvehicle.txt
//createvehicleUpdate=false
createvehicleScan=true

This will disable BE from pulling a new createvehicle.txt and overwriting ur changes.

Edited by shibdib

Share this post


Link to post
Share on other sites

The fix for this is... for server admins..

Find your battleeye folder on the server and edit the createvehicle.txt, find where it says

5 "SeaGull" 

and edit it to where it looks like this instead

//5 "SeaGull"

the // remove the action (5 which is log and kick)

You also may need to go into your battleeye config.cfg file and scroll to the bottom to where it says


createvehicleURL=http://dayz-community-banlist.googlecode.com/git/filters/createvehicle.txt
createvehicleUpdate=true
createvehicleScan=true

and make it


//createvehicleURL=http://dayz-community-banlist.googlecode.com/git/filters/createvehicle.txt
//createvehicleUpdate=false
createvehicleScan=true

This will disable BE from pulling a new createvehicle.txt and overwriting ur changes.

Wouldn't that allow hackers to create vehicles?

Share this post


Link to post
Share on other sites

been seeing a rash of this today along with corrupted data #3. Sounds like Battleye trying to narrow something down. Restarting server seemed to help it a bit when people started seagulling.

Share this post


Link to post
Share on other sites

Been getting both errors all day long. The only fix is a restart and temporary at that.

Share this post


Link to post
Share on other sites

Can you try one thing for me. Empty the "MpMissionCache" folder at your appdata folder and try join your favorite server.

Edited by mokum

Share this post


Link to post
Share on other sites

did anyone ever find out why this is happened ? My server was running stable, now everyone gets

CreateVehicle restriction #0

 

when joining....

 

why is this? Does commenting out the 5 "SeaGull" stop this?

 

will this allow hackers to spawn cars?

 

please reply

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×