Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Hi, I get the following errors: 'Got an HTTP error code that is neither 200, nor 403: 401' when trying to use the !discord command, and
[Discord] [ERROR] HTTP error during request
[Discord] [ERROR] method: GET
[Discord] [ERROR] endpoint: '/guilds/142757984487866368/members?limit=20'
[Discord] [ERROR] err: Couldn't resolve host name
when I changed the discord_api to h.t.t.p.s discordapp.com/api
[Discord] [ERROR] HTTP error during request
[Discord] [ERROR] method: GET
[Discord] [ERROR] endpoint: '/guilds/142757984487866368/members?limit=20'
[Discord] [ERROR] err: Couldn't resolve host name
Should the discord_sv file in the addon update to reflect what I changed in the dev console?
In case you are still having issues after that, I published a new version to GitHub, as well as the Workshop. It should now dump the full URL when it encounters an error, so maybe we can see what is causing the issues.
The only reason where that error would occur is when not all the necessary permissions have been applied. My own bot is configured with "Disable Member input and output" (or something similiar), so it should work in theory. Would you be able to give it full Admin permissions to see if that changes anything?
EDIT: And again, I ♥♥♥♥♥♥ up. Had something messed up with my configuration. Turns out, "Disabling Input/Output of members" (which seems to be "Deafen" in other languages) is totally irrelevant to what the bot does. The important (and the only needed) is actually just the "Mute members" one.
I pushed out an update, please try again. This probably won't fix the issues you originally had, but it will at least display an error message again.