Breaking Lock Bug or just Bad luck????

[Argos]

None of my lock breaking chars have managed to succesfully break a lock in a long long time.
Could this perhaps be a bug? Or are they all just totally unlucky?

[computaertist]

I've never managed to break a lock with any character. I've tried more times than I'd ever want to count.

[Hedgedhogst]

I've had one character try to pick a lock recently, and it took at least 9 attempts. Someone else I know was trying to pick a lock in a bit of a hurry, and it took them about 13-14 attempts. I know I've heard a much higher set of numbers in the past too... A real record breaker it was.

I'd quickly put my potatoes on bad luck.

[Doug R.]

My character's luck has been crap lately also, but I also had one break a lock on the first try in that last two weeks.

[wadko]

I see that not only I have a concern about the lock breaking script being broken...

[freiana]

If it broke, it broke very recently. Has anyone been able to break a lock in the last week?

[Hedgedhogst]

If it broke, it broke very recently. Has anyone been able to break a lock in the last week?

Yeah, I have. Twice. Once in about 7 attempts, and once in 3 attempts.

[SekoETC]

I doubt anyone has touched that code in a long time. According to statistics, lock picking has been successful 57 times this week, unsuccessful 206 times. So chance of success has been 21.7% this week.

[Greek]

Seko: Data based on number of events or time stats is unreliable, because num of successful tries contains locks destroyed with a screwdriver (it has 100% success chance).

And this code wasn't changed for years. Server configuration wasn't changed for a few weeks, so nobody knows the cause.

After some investigations I can confirm it as a bug.
We've run piece of code which is responsible for lock picking many times so it's practically impossible to have such results.
The same code run on different servers worked as it should (both on the same and different php version).
Something's wrong with php inbuilt random function in this particular case.
I'll fix it as fast as possible, but you probably see I have very little time for Cantr since april

[wadko]

Seko: Data based on number of events or time stats is unreliable, because num of successful tries contains locks destroyed with a screwdriver (it has 100% success chance).

And this code wasn't changed for years. Server configuration wasn't changed for a few weeks, so nobody knows the cause.

After some investigations I can confirm it as a bug.
We've run piece of code which is responsible for lock picking many times so it's practically impossible to have such results.
The same code run on different servers worked as it should (both on the same and different php version).
Something's wrong with php inbuilt random function in this particular case.
I'll fix it as fast as possible, but you probably see I have very little time for Cantr since april

Well... this sucks... and to think that my char wasted so much time on a bug...

[Doug R.]

Well, may I be so bold as to suggest that lockpicking is integral and essential to Cantr, and that the game should be shut down until it can be fixed? This is not something players should lose their characters over, and now that it's known, some might take advantage of it.

[freiana]

I very much agree with Doug. This is potentially very dangerous for some chars.

[Greek]

Ok, why not. I'll lock it before projects tick.

[Vega]

Now thing is... When will it be back?

[catwill]

Now thing is... When will it be back?

The timing of the lock was just awful for one of my chars, so hopefully soon.