Quote:
Originally Posted by Konstantinos
Server log will print nothing for a server crash or run time error as long as crashdetect plugin is not loaded. Nobody would want to waste time and effort trying to find the cause without a clue, it's like looking for a needle in a haystack.
|
That's incorrect.
Fact is that the errors that come up are easy to find due to backtracking to what you changed, and actually debugging your code.
Also, with people stating their server has crashed, how are you so sure that the server is indeed crashing, and that there are no errors in the compiler? (The immortal "it's only an warning, it'll still run" understatement.) Or even nothing else in the rest of the server log that he's neglected to post. One line isn't what the server.log put out... Surely...
Again, this plugin was never intended to be a first line of checking the reasons why this sort of thing happens, yet right now, everyone seems to recommend it constantly... Another one is that people still run it on production servers, don't even use it properly, and make out, that it is a wonderful "fix all", when it's an advanced debugging tool.
As I requested, the complete server.log, and any warnings/errors from the compiler would be the first gotos in this case... Much like the requirements for a thread of this nature which is the guidelines for posting in this section.
You all miss major steps that can be taken for sake of this fix all, then people will forget how to even fix their scripts in the first place.
Much the same as those who post up endless "Help" with compiler errors that are self explanatory.
Your "wasting time" is actually an excuse for being lazy...