Closed yagizher closed 4 years ago
same error, and the mysql-async isn´t the problem
Mysql async is written on js xD
Yeah I don't see how this is related to my resource
Apparently it only happens when they add essentialmode to ExM.
I was using ExM without ES for a week or two and there were no errors, I soon as I added ES it throws me that error. Still don't understand how can it be not related to ES..
IT IS related to es. But maybe cuz its maybe not compatible with ExM (even tho they say/said IT IS.)
Nothing changed between today and a week ago in either resource and they've been working fine since it's release.
Again: without a reproducible case, this is not something to fix.
I am not saying something changed. Kane I respect your work and not blaming you or anything for this issue. What I meant that I was using es_extended and ExM for 2-3 months developing my server and never had this issue. It started to happen after I installed ES to my system. If I disable the resource now I'm not getting those errors anymore on connects. So like the other one said, it might be an ExM issue when using with ES, or the opposite.
It still stays the same, I can't reproduce this behavior so I'm not sure how to handle it.
https://media.discordapp.net/attachments/701966810958004224/723581152031670566/dasdasdas.JPG?width=1442&height=234
It seems to be experienced when someone joins. Like tons of people are getting this message in their console when someone joins.