-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GameDig Discord Server Monitoring #4304
Comments
Here are the respective lines that need changing in the first case: uptime-kuma/src/pages/EditMonitor.vue Lines 249 to 260 in d7d57ea
|
How is this a feature request when it is a feature that exists that doesn't work? |
How something is classified does not super matter. |
do these ever get worked on? over 500 open issues seems like a lot. when does gamedig get updated? there are new games missing from the list. |
Please refer to the activity graph. Note I don't like the entitlement/attitude that I am reading into this comment. See our licence: If this issue will get resolved depends on if a maintainer or user finds this issue important enough to invest the time.
Depends..
Gamedig 5.x has some breaking changes, which need migrating. Please refer to #4414 for the issue for this. |
🛡️ Security Policy
📝 Describe your problem
What hostname and port should I use for monitoring a GameDig Discord server? According to GameDig, you are supposed to use the GuildID but that doesn't work when I put it in hostname and I am forced to enter a port.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Docker
🌐 Browser
Opera GX
🐋 Docker Version
24.0.7
🟩 NodeJS Version
No response
The text was updated successfully, but these errors were encountered: