ID:268803
 
Alright as many know of this .configure bug, I don't have a clue on the way to fix it. I can't set any variables in the time before the bug kicks in. I have people leveling up 5 levels in 10 seconds.... thats HUGE problem for an RPG based game.

If you know of a way to fix this, please tell me as soon as possiable.
What .configure bug? If you believe there is a bug in BYOND, you should be reporting it in the BYOND Bugs forum.
In response to Shadowdarke
I don't believe it is a BYOND bug, or I'd done that... I blieve I need a fix, a newbie's fix even.

I hate to post the bug, it'll probably work in 90% games on BYOND.

.configure delay 99999

It'll make it so that you can .dblclick things a hundred times and the del() proc will never kick into play.
In response to Ryne Rekab
Ryne Rekab wrote:
I don't believe it is a BYOND bug, or I'd done that... I blieve I need a fix, a newbie's fix even.

I hate to post the bug, it'll probably work in 90% games on BYOND.

.configure delay 99999

It'll make it so that you can .dblclick things a hundred times and the del() proc will never kick into play.


This was fixed in v340.

~>Jiskuha
In response to Jiskuha
Your real smart. If it's fixed, then why is it broken?
In response to Ryne Rekab
Ryne Rekab wrote:
Your real smart. If it's fixed, then why is it broken?

Don't get an attitude with me. You obviously have not upgraded your byond version or who ever hosting has not.
[link]

~>Jiskuha
In response to Jiskuha
Jiskuha wrote:
Ryne Rekab wrote:
Your real smart. If it's fixed, then why is it broken?

Don't get an attitude with me. You obviously have not upgraded your byond version or who ever hosting has not.
[link]

~>Jiskuha

There was another bug relating to configuring the delay. Perhaps Lummox was talking about that? It had to do with freezing the server.
In response to Jon88
Ya, playuers used to be able (before 340) to crash servers by typing, into the command line, .configure delay=65535, or something like that. Although it doesn't effect the server, I'm pretty sure, although not positive, that it can effect a singular player.
In response to Wizkidd0123
Wizkidd0123 wrote:
Ya, playuers used to be able (before 340) to crash servers by typing, into the command line, .configure delay=65535, or something like that. Although it doesn't effect the server, I'm pretty sure, although not positive, that it can effect a singular player.

.configure delay -1
In response to Ryne Rekab
What version of BYOND are you using? (In Dream Seeker, click the Help menu and select about BYOND. The version number is in the lower left corner.)

Ryne Rekab wrote:
It'll make it so that you can .dblclick things a hundred times and the del() proc will never kick into play.

The effects of .dblclick are applied but the object is not being deleted. Could you supply the DblClick() proc. in question?

I've seen numerous instances where a laggy player (what they are simulating with the .configure delay setting) can select items that are no longer available to them. However, if the item was deleted in the mean time it usually just gives me an error. BYOND shouldn't initiate multiple simultaneous threads no matter how much input it has. It is a single thread language and will finish one thing before going to the next. If you have a spawn() or sleep() delaying the deletion, that may be the problem.

In the beginning of the proc make sure to check that the usr has valid access to it. You really can't trust the atom to be in the usr's view for clicking or the src settings of verbs to always be accurate. A quick check can prevent the proc/verb from executing when it shouldn't.
In response to Hell Ramen
Oh, didn't realize.