annsanns / betch Goto Github PK

https://github.com/Atmosphere-NX/Atmosphere/blob/4d430a4c61ef65fab66556788107085ca2f98b16/libraries/libvapours/include/vapours/results/err_results.hpp#L27

Jaki recommended https://prometheus.io/

It appears that Discord rolled something breaking out that the bot can't handle. Updating discordpy might solve it.

• Add "watching/playing" status
• Show some stats about active servers it's on
• Improve compatibility with Robocop somehow ... ? (maybe change prefix)
  • Yes but actually no
• Add ability to sent suggestions
  • Delayed to v2
• Improve "Unknown" to be a bit more specific
• Add manual updating command with cooldown

The easiest way would be to just grab them while betch.scrap is running and convert them JIT

https://switchbrew.org/wiki/Panic_codes

Shouldn't be hard but requires a lot more edge case programming and I'm lazy

Discord decided to radically enforce their new "Slash" commands. This sadly also means that we will need to rewrite a lot of the bot to use the completely different system.

If you are curious why this is happening, please read the statement by the discord.py author: https://gist.github.com/Rapptz/4a2f62751b9600a31a0d3c78100287f1

For now we will try to support the old commands while it is still possible.

• Add ability to scrap fatal error codes
• Add ability to scrap fs error codes
• Add ability to sent suggestions
  • Sounds useless if I think about it
• Everything in #1

Error caused by failure to connect to a working server. No clue why it's that module but it is what it is.

While extremely rare (once a week at max.), it seems like the discord bot sometimes suddenly dies.

The easy fix would be to just restart it whenever it crashes, which I'm probably going with.

As I transition this to a local server, the API and discord bot is currently down for the first time in nearly a year.

• https://github.com/switchbrew/libnx/blob/master/nx/include/switch/result.h
• Goldleaf

EdiZon
Atmosphere