Alex Martin

The log-core library will have logging rotation based on date and size in the near future, so there might be some conflict there when two programs attempt to rotate logs...

log-core never writes to stdout (it writes to stderr on a detected server crash though), and I don't really plan on adding that feature, so no conflict there 👍

No, it doesn't have access to that function. I was planning on adding `logprintf` redirection into my normal log plugin though, so that every `logprintf` call gets logged through log-core....

This is just an information log-core is giving you. It says, that it *detected* a crash (log-core didn't necessarily cause it). You'll have to use crashdetect to find out what...

All getter functions (`DCC_GetSomething`) work with variable references: ```pawn new id[DCC_ID_SIZE]; DCC_GetChannelId(my_channel, id); ``` Additionally, those getters return `true` or `false` based on whether the value was successfully retreived or...

The logs don't really tell a lot about your crash. Use crashdetect, reproduce that crash and share the crashdetect output here.

I made some network related changes; could you please [try this development build](https://ci.appveyor.com/project/maddinat0r/samp-discord-connector/build/job/a573k1k0j91150md/artifacts) out and report back if the crashes stopped?

I'm not quite sure that this is fully fixed. I did some changes on the WebSocket netcode, but I suspect that there's still a possibility for a crash, especially on...

Are there any errors or warnings in the plugin log? Does your bot have enough permissions to receive message delete events in the channel you expect it to?

I'll investigate further as soon as I get some free time.