Safes inaccessible after unlock

[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.

[nedfox]

I had bits of old industrictable base code in server-functions.sqf.. As he also used code that is obsolete I thought it might be related.. Seems not then.

Guess you'll have to do same as all others : Start plain vanilla, then add mod per mod and check when it starts failing.

[koolaidman04]

Same story here.   Updated my custom compiles.sqf and fn_selfActions.sqf both, and still having the same issue. I have disabled antihacks, updated BE files, added the PVDZE lines to the exceptions, and still the same problem.  Everything is fine until you try to unlock a safe, then can no longer interact with anything that requires dynamic mousewheel menus.   I am out of steam for tonight and will continue to plug away at it tomorrow evening.  If anyone finds the fix please post it ASAP!  

 

koolaid

[havok]

Bumping due to having the same issue

[nedfox]

Since I went back plain vanilla, and worked from there, it would be great to hear what you actually altered.

I was able to do infistar, DZMS, and some autorefuel things, without problems.

So if you have troubles, WHAT did you change server side ?

[Tobias Solem]

Bumping due to having the same issue

 

Check HOW you repacked your server and client PBO:s

 

You need the exact paths to be specified in eg. the Prefix (z/addons/dayz_epoch) 

[Karg]

How I solved this issue for me and the cause of it.

 

Long version short:

Arma2 used the wrong pbo. Clean up your pbo folders and remove all 'xxx - copy.pbo' files and such.

 

Long version long:

Arma2 can use the wrong files, why is out of this infos scope.

If you make "backup" copies of your pbo's (which incidentally quite a few admins do when making changes) you may end up with several pbo's, for example:

dayz_server.pbo

dayz_server - Copy.pbo

dayz_code.pbo

dayz_code - Copy.pbo

dayz_code - Copy (2).pbo

and so on...

 

For some very funny reason (hey, hmm,. how come this crappy engine keeps doing stuff like this?, oh wait, it's because it's crappy...) or not so funny reason,.. Arma2 loads the wrong file, so instead of loading 'dayz_server.pbo' it loads 'dayz_server - Copy.pbo'.

 

You can confirm this by attempting to move for example the 'dayz_server - Copy.pbo' to another folder while the server is running, the system should state it's open by Arma2, and you have the issue confirmed.

 

So basically, make sure only pbo's that are actually supposed to be used are where they should be, and move everything else, elsewhere.

 

Hope this solves your issues.

[DarkRanger]

Having this issue too/still..

 

Do not have any additional pbo copies lying around. The way the additions are added and where they are added is no different than before, so does anyone have any other ideas?

[Jkrohn1]

Looks like I will need to test this started my server as my community couldn't wait so it's still a WIP. Hope we don't have an issue as the Tow and Lift has my head in a twist.

[Tobias Solem]

Again, I think it's about how you packed your PBO:s, consult the logs.

[IceCold]

Ok, I of course ran into all these issues - safes, cars, traders. Fixed the traders, but still having issues with safes and vehicles unlocking. Can get the 'unlock safe', put in code, then...nothing.

 

Checked fn_selfActions, and compared it to my customs one...ok, problems. Made a 'merged' file of both. did same with compiles.sqf.

 

Now, before I go putting them back...where do these 2 files go back to. Do they have to be in the custom folder, or an they go back to their original locations?

 

Right now I have the custom fn_selfActions.sqf in my custom folder, and the compiles.sqf back in the dayz_code.pbo

 

Thanks

[IceCold]

Anyone?

[PetuniaEpoch]

All sorted :D

 

Was a server-side pbo bug, re-did some files and it fixed itself :P