Selia Posted April 22, 2020 Report Share Posted April 22, 2020 Greetings, I am experiencing a problem with Trinitycore 7.3.5. When starting the worldserver for the very first time, everything starts up fine and it works. But once the server is closed and opened up again, the following error shows up every time. I have also tried recompiling and erasing the database and once again it worked the first time, but then the same error over and over. No core or database madifications have been made, this is a raw TC 7.3.5 pull. Any advise on what I can do? Ps. I do not wish to upgrade to TC 8.xx because I have tried it and it is simply too unstable right now to use it, so I really want to get this Legion core to work. unknown_worldserver.exe_[22-4_21-47-17].txtServer.log Link to comment Share on other sites More sharing options...
Demolol Posted April 26, 2020 Report Share Posted April 26, 2020 It's literally telling you the exact problem. You have an error in your SQL syntax at InstanceSaveManager::LoadResetTimes. Compare that function in your core to trinitycore 8.x and see if it's different. If it's not, then your db might be out of date. Link to comment Share on other sites More sharing options...
Selia Posted April 26, 2020 Author Report Share Posted April 26, 2020 22 minutes ago, Demolol said: It's literally telling you the exact problem. You have an error in your SQL syntax at InstanceSaveManager::LoadResetTimes. Compare that function in your core to trinitycore 8.x and see if it's different. If it's not, then your db might be out of date. The core is 7.3.5 and it's unmodified, so there's nothing for me to compare it to... Link to comment Share on other sites More sharing options...
Aokromes Posted April 26, 2020 Report Share Posted April 26, 2020 7.x branch is no longer supported, when it was released it worked, be sure you have the correct files and deps. Link to comment Share on other sites More sharing options...
Shauren Posted April 27, 2020 Report Share Posted April 27, 2020 No, it was broken back then too Link to comment Share on other sites More sharing options...
Selia Posted April 27, 2020 Author Report Share Posted April 27, 2020 Oh I see, well that is unfortunate. Thanks for the replies. Link to comment Share on other sites More sharing options...
Daniel25 Posted May 2, 2020 Report Share Posted May 2, 2020 You can try to add this patch manually if you want try it: UPDATE `access_requirement` SET `difficulty`=4 WHERE `mapid`=564; Link to comment Share on other sites More sharing options...
Selia Posted May 2, 2020 Author Report Share Posted May 2, 2020 Well I'm attaching the function void InstanceSaveManager::LoadResetTimes() below if anyone has any idea where the problem might be: LoadResetTimes.txt Link to comment Share on other sites More sharing options...
Recommended Posts