Discord webhooks don’t work ingame

Mine randomly stopped for a couple of hours then came back online? It’s used as an ingame command audit for whenever an admin uses an admin command or whenever a player gets vote kicked.

Edit: this isn’t supposed to be a reply, I misclicked my bad!

which address you’re using? discord.com or discordapp.com?

This is a little bit of a PSA

@marcin_pl500
The domain name you use shouldn’t matter, the discrepency on the block between https://discord.com and https://discordapp.com is very clearly unintentional, and abusing this will only make Discord less likely to reinstate webhook access.

And, for everyone reading this in the future and anyone this might be relevant to…

Discord has blocked Roblox’s access to https://discord.com, which very clearly means that continuing to make requests to Discord anyways isn’t going to be taken well by them, especially considering many people haven’t even attempted to implement proper rate limits or even just any kind of rate limiting at all, which is disrespectful to the service, and in the future, people should be properly rate limiting their code, or not issuing requests to these services at all.

Here’s are two very important things you should be doing if you want Discord to remain Roblox-accessible:

  1. Don’t make requests to Discord at all, its blocked, and circumventing, or continuing to make requests that are going to get denied is wasting their resources and puts pressure on them to keep Roblox blocked.
  2. When (and if!) Discord unblocks Roblox, everybody who is using Discord webhooks should either be properly implementing rate limits, or simply not making requests to Discord. Blocked requests (rate limited, or now, by force) still have a cost to the service, and you should not be repeatedly making requests that are just getting blocked.
  3. I’ll say it again, please ensure you’re respecting the rate limits and ToS of any services you’re utilizing before you start using them again Discord Developer Portal

Additionally do not just switch to Trello. If you really need a free logging DB, again, use a service that’s designed for this sort of mass, frequent requests, like Google analytics, hell, even Google sheets is better for this than Trello.

Simply switching everything to Trello is immediately going to get Roblox blocked there as well, you should not be using these services for this sort of thing with the scale of the Roblox platform, they have each made it clear that many cases where Roblox utilizes them are not welcome, and both Discord and Trello have repeatedly asked users to stop sending them requests against their guidelines, and now Discord has issued this second block to Roblox.

Additionally, this resource was shown to me, and, its a perfect example of something designed for this:

12 Likes

Discord is no more a data analysis application than Trello is. :slightly_smiling_face:

Consider using a proper data analysis platform such as gameanalytics or google analytics.

5 Likes

I just realized something: Guilded has webhooks!
And they were bought by Roblox, so they probably won’t rate limit us any time soon lol

This is an even lazier solution than using trello :sunglasses:

image

It seems to work literally the same way as discord. You can literally just replace the Discord webhook URL and it’ll work.

http = game.HttpService
function say(msg)
        local Data = {
            ["content"] = msg
        }
        Data = http:JSONEncode(Data)
        http:PostAsync("https://discordapp.com/api/webhooks/12345678/BLABLABLABLABLABLA", Data)
end
say('such epics! wow')
5 Likes

They will have to still rate limit. The only reason why Discord did is because they are expensive to upkeep. It’s also against their ToS. Guilded nor Discord are meant to be a logging service but a chat.

1 Like

That’s irrelevant to the subject. The issue isn’t “we have no service for logging,” it’s “Discord webhooks don’t work ingame.”

If you want to log something critical, use datastore. Otherwise, this is literally a plug-and-play solution to this issue.

Engineers, can you yourself add a debounce or rate limit on HttpRequests that go to discord? Needa go harsh with people who spam discord webhooks. Maybe if someone spams a discord http take some moderation action on their account? (feel free to disagree)

1 Like

I do believe Discord handles rate limits themselves, to an extent. I believe that when you send a handful of requests they do not get processed instantly like they would if you didn’t send a handful of requests, but rather send in intervals of a second or two, before flat out blocking your requests for a few moments if it becomes too much. But even then, Discord having to queue requests at a large number is resource expensive to do for hundreds if not thousands of requests a minute.

ROBLOX Engineers are not likely to do anything about this issue for a few reasons, one being, they simply don’t care enough to do so. This does not effect their platform so why would they do something about it? Two, even if they did want to impose a restriction like this, they would likely have to redo the entire function for handling HTTP requests, developers are already restricted enough, why limit what they can do even more? Three, it is just basic common sense that if your site can handle HTTP requests then you impose your own restrictions, which Discord has done (and they have been violated to a large extent, leading to an IP block)

If people want to avoid Discord IP blocking they need to avoid hooking up their webhooks to useless crap that can just be simply logged into an array for free with no rate limits on ROBLOX. Things like chat logs, action logs and the likes are a great way to get the entire platform blocked by Discord, once again. Some things should be okay, such as exploit logs, moderation logs, etc, SO LONG AS YOU RESPECT DISCORD RATELIMITS. Please do keep in mind that if you have a front page game, it may only look like a few requests a second, but multiply it by the vast amount of servers active and you can pretty much see the problem.

If developers are unsure or have no clue how to watch their request limit for sites, I recommend this module. Even if you are a person who would have trouble using this module, you can do something as simple as a wait(5) before using PostAsync, it can have a big difference. It won’t kill you to wait a few more moments.

1 Like

Action on their account, absolutely not. That’s not somewhere to even state that.
This issue has happened overtime, not just yesterday, or today. This has been a common issue that discord seeks to be disrupting their services.

There’s a simple solution to this.
Don’t spam requests, or face consequences of everyone-elses downloss.

And to mention this, this is a bug report under the bug report category, this isn’t for cluttering the post, ROBLOX staff has already said not to clutter the post with it, and yet there is development discussion posts about this, post there & not here. Simple.

1 Like

Due to people spamming webhook messages from Roblox to Discord, they decided to block Roblox from sending webhook post requests.
But It’s possible to send a post request to your own server and forward the post request to Discord.

Replace

discord.com

to

discordapp.com

Hope this helps :slight_smile:

1 Like

As said in previous replies by doing this you are just using a loophole that is unintentional, you shouldn’t be using this to get around the ban and should just accept the fact that Discord webhooks are gone.

5 Likes

Found this issue earlier, if you change the “discord.com” from the webhook you can change it to “discordapp.com” and it’ll work!

FWIW it looks like discordapp has stopped working as was inevitable.

11 Likes

About time, and the people who have used this bypass to bypass the ban, congratulations, you most likely got Roblox banned from Discord for good this time

3 Likes

unfortunately, now its time to create discord bot to bypass this

I used a discord bot with a rest api, and it also stopped working.

It’s not the webhooks getting banned, it’s the API.

2 Likes

So you’re saying it’s coming from the api, and not the webhooks? Could you provide some proof of the api itself being blocked?

Are you serious?

How about you try?

Using the REST API doesn’t return any errors, but it still doesn’t work.