Bug This is a FXServer bug that makes discord.js@13.0.0+ not working properly. This can probably affect other node modules but I haven’t tested it. FXServer: Debian 10 with 4960 artifacts. Node.js version: 16.3.0 Discord.js version: discord.js@13.4.0-dev.1636675518.5e0a7d5 How to reproduce Creat…

The missing return this; breaking current releases of discordjs should be fixed: fix(scripting/v8): correctly return self in Timeout#ref/unref/refresh committed 08:36AM - 31 Dec 21 UTC (UTC) [blattersturm…

Seems to be an issue with fetch(). While waiting for this to get fixed, I found a workaround. By adding the presences intent all members will be cached. This allows us to use guild.members.cache. Just using .get() will however return undefined. If we use map like I’ve done in the example below, we …

Not related to the original bug report. The issue described in the report was fixed. Update your server artifacts. feat(scripting/v8): allow timers refresh committed 02:11PM - 08 Dec 21 UTC (UTC) [nihonium…

I am already running the newest server artifact. So far I’ve tested build 5134, 5123 and 5104. The error persists on all these builds with the exact same error message.

Again, your issue is not related to the original bug report. We won’t provide you any support since your messages are offtopic to this post.

[image] VikingTheDev: with the exact same error message. Can you post said actual error message?

Sure @nta . When testing OPs issue on the newest build (5134), I’m getting the same error: ‘refresh’ (NodeJS.Timeout.refresh()) is undefined in the FXServer Node.js “version” (Unsure what the correct term is). This leads to an error being thrown when i.e. using fetch() in discord.js version ^13.0.0. …

Right, this library is a bit weird and somehow tries to get setTimeout from require('node:timers') yet somehow expects it to be equal to globalThis.clearTimeout etc. which in our runtime very much is not the case. I guess you can ask the library’s maintainers to either consistently use globalThis.s…

Thank you for the quick fix! I Really appreciate all the work you and the rest of the team puts into this project :heart: Just tested OPs code example on build 5149 and everything works as intended now.

You cannot use stock discord.js in fivem. it may look like you can and work like you can on the surface but if you actually log the debug event from it you will see it’s very much not happy as the timeout doesn’t clear and so the bot will loop reconnecting indefinitely every 20 seconds till it’s use…

[image] zfbx: You cannot use stock discord.js in fivem. You can. If anything is making it not work, report it with a repro. [image] zfbx: as the timeout doesn’t clear and so the bot will loop reconnecting indefinitely This was fixed by the same commit discussed in this topic, wasn’t i…

Discord.js 13.0.0+

FiveM Discussion Bug Reports

nta March 16, 2022, 8:59am 19

As seen in another topic, they cut a release with half a fix and the issue is on their side now. Get their latest main from git.