Tobias Solem Posted February 8, 2014 Report Share Posted February 8, 2014 * Upgraded to 1.0.4.1 * Changed to the new server/mission pbo Error: (Verified with several different users & safes), the safes aren't accessible after unlocking, and after relog they act as if you never unlocked them in the first place. Link to comment Share on other sites More sharing options...
0 vbawol Posted February 8, 2014 Report Share Posted February 8, 2014 Just checked on our dev server and we do not have any issues like this. Anyone else having issues with safes on 1.0.4.1 on their servers? Link to comment Share on other sites More sharing options...
0 cen Posted February 8, 2014 Report Share Posted February 8, 2014 Make sure you are using the most recent fn_selfActions.sqf as well as compiles.sqf Link to comment Share on other sites More sharing options...
0 Tobias Solem Posted February 8, 2014 Author Report Share Posted February 8, 2014 Make sure you are using the most recent fn_selfActions.sqf as well as compiles.sqf We have never modified those, since we run pretty much a clean vanilla Epoch. So doubt it's related to that. The only modifications we have done are done in the mission pbo (logo, zombie count, loot tables (removed M107) and added some UN drops in server pbo for events). Client files are unmodified. Link to comment Share on other sites More sharing options...
0 Tobias Solem Posted February 8, 2014 Author Report Share Posted February 8, 2014 I am troubleshooting by rolling back to 100% vanilla, will be back with results. Link to comment Share on other sites More sharing options...
0 Tobias Solem Posted February 8, 2014 Author Report Share Posted February 8, 2014 OK, for some reason when I rollbacked to 1.0.4.1 vanilla it gets stuck on Server Authentication o.0 Continuing... Link to comment Share on other sites More sharing options...
0 Tobias Solem Posted February 8, 2014 Author Report Share Posted February 8, 2014 After removing the ca-folder in the mission.pbo everything works. Link to comment Share on other sites More sharing options...
0 SN1P3R Posted February 8, 2014 Report Share Posted February 8, 2014 We updated to 1.0.4.1 and when you try to open a safe you get kicked Public variable rectriction #0 Link to comment Share on other sites More sharing options...
0 J.R. Posted February 8, 2014 Report Share Posted February 8, 2014 same here, I enter the code to the safe, after seeing the animation for unlocking the safe i get kicked for public variable restriction 0 Link to comment Share on other sites More sharing options...
0 Radiix Posted February 8, 2014 Report Share Posted February 8, 2014 Add this to your publicvariable.txt, it should fix the kick: !="PVDZE_obj_getlocalVars" !="PVDZE_obj_setlocalVars" Link to comment Share on other sites More sharing options...
0 vbawol Posted February 8, 2014 Report Share Posted February 8, 2014 Add this to your publicvariable.txt, it should fix the kick: Or just use !"PVDZE_" like our publicvariable.txt is setup. Link to comment Share on other sites More sharing options...
0 zogra Posted February 8, 2014 Report Share Posted February 8, 2014 * Upgraded to 1.0.4.1 * Changed to the new server/mission pbo Error: (Verified with several different users & safes), the safes aren't accessible after unlocking, and after relog they act as if you never unlocked them in the first place. Same here Link to comment Share on other sites More sharing options...
0 J.R. Posted February 8, 2014 Report Share Posted February 8, 2014 Or just use !"PVDZE_" like our publicvariable.txt is setup. did this and it stopped kicking us...but....now after entering the safe code we lose all options to interact with safe as mentioned above by others Link to comment Share on other sites More sharing options...
0 SN1P3R Posted February 9, 2014 Report Share Posted February 9, 2014 So does anyone have the actual fix for this so that it works properly? Link to comment Share on other sites More sharing options...
0 Clint_102 Posted February 9, 2014 Report Share Posted February 9, 2014 !"PVDZE_" Is work for me. Tested on two my servers. Link to comment Share on other sites More sharing options...
0 SN1P3R Posted February 9, 2014 Report Share Posted February 9, 2014 Same works on ours now too Link to comment Share on other sites More sharing options...
0 nedfox Posted February 9, 2014 Report Share Posted February 9, 2014 Very same here. After adding !="PVDZE_obj_getlocalVars" !="PVDZE_obj_setlocalVars" to the exceptions, the kicks are gone, but after unlocking you cannot interact with it, or any other safes.A friend tried the same safe and got the message "the safe is already being looted" or something simular. Link to comment Share on other sites More sharing options...
0 BetterDeadThanZed Posted February 9, 2014 Report Share Posted February 9, 2014 Or just use !"PVDZE_" like our publicvariable.txt is setup. Is this for people that haven't updated their BE configs? I'm assuming 1.0.4+ come with updated BE filters? Link to comment Share on other sites More sharing options...
0 Radiix Posted February 9, 2014 Report Share Posted February 9, 2014 Very same here. After adding !="PVDZE_obj_getlocalVars" !="PVDZE_obj_setlocalVars" to the exceptions, the kicks are gone, but after unlocking you cannot interact with it, or any other safes. A friend tried the same safe and got the message "the safe is already being looted" or something simular. Make sure you didn't screw up your fn_selfactions.sqf when adding additional scripts to your server. Add every script one-by-one to make sure everything else works. I didn't have any of the mentioned issues on this thread. The Battleye kicks were the only issue i had. Link to comment Share on other sites More sharing options...
0 nedfox Posted February 9, 2014 Report Share Posted February 9, 2014 I didn't change anything other then implementing Infistar.I never touch other scripts. Link to comment Share on other sites More sharing options...
0 nedfox Posted February 9, 2014 Report Share Posted February 9, 2014 Never mind.. I started fresh (plain vanilla + infistar) and it works.Might have done a typo somewhere.. Link to comment Share on other sites More sharing options...
0 edhunter Posted February 9, 2014 Report Share Posted February 9, 2014 Here the same Problem. No one is able to look in safes gear after they unlocked it. Second problem is, that after the unlock, we are not able to craft anything. a messages pops out, that i am still in "buildingaction". We have 1.0.4.1 and i updated the fn_selfaction and the player_build.sqf from the selfblood and takeclothesscript. We have installed the indestructibal base script with part 1 and 2. Could this be the problem in the dayz_server.pbo? Link to comment Share on other sites More sharing options...
0 WGC GeekGarage Posted February 10, 2014 Report Share Posted February 10, 2014 So i have the same issue on my server. Here is what i did to test it. Did a clean install to vanilla and began to add one mod at a time making sure I didn't do any typos. (this is not my first time setting up a server so i know where the do's and don't are) This is my normal procedure whan i upgrade our server and it have never been an issue. So after editing all the files i started the server and every thing looked good. No errors in RPT either Server or Client side. Next thing i did was testing some of the mods and they looked fine so i upgraded our community servers and opened up for players to join. and the all promptly complained about not being able to get into safes. so i reverted back to 1.0.4 and did some more testing on our test/upgrade server. First I tried to get into a safe myself, without any luck. I could enter the combo just fine but i didn't get any "Gear" option. neither did i get any option to unlock vehicles or any other scroll menu (except gears on cars that were locked or the full car menu if it was a car without key. So i tested if i could build anything, and funny enough i couldn't, just got the message "Build Already In Progress". Now i thought it might be due to the snapping addon i'm using, so i reverted back to the original player_build.sqf file in the compiles.sqf and tried again, without any luck. i thought then that i might be the communication with the SQL so I tested to enter the code wrongly and i told me that the code was wrong, this i could keep doing. So i tried to enter the correct code and now i was back in the "build Already in progress" and couldn't enter anything and most of my fn_selfaction options were gone. So i tried to build some stuff with and without snapping enabled and it works just fine. so i build a plot pole, then a lockbox and then a safe. without any problems. but as soon as i unlocked the lockbox (didn't need to type code for some reason right after i build it) I couldn't get into gear on it and i didn't get the option to unlock safe. this was tested with and without snapping So my conclusion is that everything works until you try and unlock a lockbox or safe, then you are screwed. haven't tested with a pure vanilla, this is the next thing i have to do. Link to comment Share on other sites More sharing options...
0 LoadingSA Posted February 10, 2014 Report Share Posted February 10, 2014 This is also an issue on my server we have tried everything, Can you guys please stop pushing an update every 48 hours to every server and clinet, make patch notes easy to find and fucking keep your wiki up to date. Monster 1 Link to comment Share on other sites More sharing options...
0 nedfox Posted February 10, 2014 Report Share Posted February 10, 2014 We have installed the indestructibal base script with part 1 and 2. Could this be the problem in the dayz_server.pbo?Not needed, read the patchnotes. It might actually be the cause. Link to comment Share on other sites More sharing options...
0 WGC GeekGarage Posted February 10, 2014 Report Share Posted February 10, 2014 Not needed, read the patchnotes. It might actually be the cause. the cause, how so? We don't have indestructible bases script and have the problem, so i don't see the logic in your statement? (might just be me not fully understanding what you mean?) Link to comment Share on other sites More sharing options...
Question
Tobias Solem
* Upgraded to 1.0.4.1
* Changed to the new server/mission pbo
Error:
(Verified with several different users & safes), the safes aren't accessible after unlocking, and after relog they act as if you never unlocked them in the first place.
Link to comment
Share on other sites
37 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now