Open MatheusAgL opened 3 years ago
Looks like that backtrace appears because the init of the YSI-Includes is taking up too much time. As far as I know, Y_Less recently made use of a feature available in crashdetect, so it won't report those code init callbacks anymore, as they always take too much to be executed (lots of things are done there, so that can't really be improved).
It is hard to tell why your server won't load without crashdetect, but there are two things to try:
OnGameModeInit
. You can try a basic debugging by placing lots of print
in your code. After every 15 lines or so in your callback, you could add some kind of OnGameModeInit 1/2/3/[and so on, each one being an increment of the last one]
. If the server goes into your OnGameModeInit
but it won't come out of it without crashing, then the problem is somewhere between the last print
that got its output written in the server_log.txt
file and the next print
, which didn't get written there. If you find an interval like that, try adding more print
functions between those lines, to find the exact line that is crashing.print
s mentioned in the previous step are displayed, including a print
placed on the first line of your OnGameModeInit
, it probably means that it is crashing in one of your libraries' OnGameModeInit
hook. Maybe you have a pretty old YSI-Includes library? Try updating it. Old libraries versions can be unstable, so it is worth a try. If it still doesn't work (after you manage to successfully upgrade the version), try updating more of your libraries. This one may take more time, if you are currently using ancient library versions. Converting from ancient versions to the latest versions may require plenty of code changes. You may also need to do the print
debugging in your libraries.
This error appears right on the call.
When I don't crashdetect plugins in server.cfg, GameMode won't load.