04-24-2015, 01:13 PM
Yes, it appeared to be his bleeding that played a part in this last one. Since no further information has come to pinpoint the problem, I've dropped all my other projects and I am almost completely re-writing all the death and dying scripts. They are from the Henchmen (or "Hemophiliacs" who remember the days before they went politically correct) Always Bleed to Death package. They are massive. They are overly complex due to the high number of configurability options (which I no longer need/use). And they have been the staple of all my PW modules since 2004. So they are old. But I still don't understand why they appear to be at least part of the cause of this issue that just started last week.
This massive revision is going to take at least a full day or two. The main file for this system has 3893 lines right now. After an initial attempt to clean it up and simplify things, I'm down to 1593. But regardless, this will most like introduce bugs on its own. Just hopefully not as severe as a server lockup.
And if this revision does not resolve this problem, then the next step will be to enable script profiling on the server which will slow everything down. That, at least, can end though once someone causes the problem again and I have a log of the last scripts that fired before the server froze.
This massive revision is going to take at least a full day or two. The main file for this system has 3893 lines right now. After an initial attempt to clean it up and simplify things, I'm down to 1593. But regardless, this will most like introduce bugs on its own. Just hopefully not as severe as a server lockup.
And if this revision does not resolve this problem, then the next step will be to enable script profiling on the server which will slow everything down. That, at least, can end though once someone causes the problem again and I have a log of the last scripts that fired before the server froze.