Tracer

> i agree with CrosRoad here. This would be a hassle to maintain Nah, it wouldnt. Its the same as with node or any other discord lib. Users would need...

> Updating the bot is easy, but updating this lib in mtasa-blue takes more time and as he said, there's not as big and active of a developer community like...

> https://github.com/botder/mtasa-discord-bot This is only a webhook and not a bot. Not the same solution. It has limitations and it obviously isnt implemented as native feature

> > > https://github.com/botder/mtasa-discord-bot > > > > > > This is only a webhook and not a bot. Not the same solution. It has limitations and it obviously isnt...

> Found 3 more issues: > 1. only one bot allowed? why not "createDiscordBot(token)"? > 2. discordOnEvent - why won't you use current event system? > 3. performance, even if...

> As the owner and developer of mtasa-discord-bot I have to disappoint you, because it always used discord.js for sending messages back and forth; and never webhooks. If you need...

> your pull request should be just regular resource, thats wy i mentioned to make better socket and http support. I don't want to turn off my server to update...

> Updates are not the worst, performance wise it can be bad especially big servers, and why 1 resource = 1 bot? maybe i want 2 bots in one resource?...

Im not interested in advancing this PR further anymore. If someone wants to refresh it, feel free to do so.

> Beautiful initiative. I see you want to implement getting players & max player count for starters. That's good! I want to implement every function + maybe more 😉