安装 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.