While the idea is nice, my vote is no: 1) Many clients will eventually show up. They may be incompatible to each other. Do we really want the core to be doing complicated guessing of which assist is there? We already have enough problems trying to support the client APIs 2) There is an easy solution...

The main question is whether the client would go back to the char selection screen. You could try to send the 0xA9 packet via script and see what the client does with it. Here is the doc: https://docs.polserver.com/packets/index.php?Packet=0xA9 I doubt the client will respond to it. Maybe it crashes...

I like the idea of having a board for alternative distros, but there are not that many posts to warrant a board per distro. I can see it working if topics are tagged according to the distro they refer to.

And... don't we already have a "complete world" forum in some category?

Set "RunawayScriptThreshold" to some smaller value, like 1000 or 5000 and see if anything shows up in the debug.log. 100000 is too large. Yukiko: the option you mentioned is useful only when the core reports "No clock movement in 30 seconds. Dumping thread status.". If I understand correctly, he mos...

The core ignores that parameter and assumes it's always true. Unfortunately I can't find when it changed, but it was more than 8 years ago (that's the limit of our history). Must have been right after this speed increase.

We discussed about it some time ago, and the next one will indeed be POL 1.00. ;) For the silver/gold amounts, do you know which client version starts accepting those? Do you know how the packet looks like? We could have a look into it. About the other features, have you seen those implemented somew...

I'm also at a loss with this bug, that's why I'm looking for any information on it. Skinny has reported it to me many times for a few years now. Apparently it went away after he fixed some critical scripts. My hypothesis is a problem in the scheduler. It seems that within some special condition, the...