search

MizaGBF / MizaBOT

Python 3 Granblue Fantasy-themed Discord Bot
MIT License
25 stars 13 forks source link

gbf_access cog not working #7

Closed vSwifty closed 3 years ago

vSwifty commented 3 years ago

Commands under the gbf_access cog don't seem to work Here's the output I'm getting from the bot image

Although it does work on the /gbfg/ discord image

The heroku log shows this 2021-05-08T06:35:22.101422+00:00 heroku[worker.1]: Starting process with commandpython3 bot.py 2021-05-08T06:35:22.787417+00:00 heroku[worker.1]: State changed from starting to up 2021-05-08T06:35:30.576604+00:00 app[worker.1]: Invalid key: image_upload 2021-05-08T06:35:30.576651+00:00 app[worker.1]: Invalid key: debug_update 2021-05-08T06:35:30.793872+00:00 app[worker.1]: Invalid key: you_private 2021-05-08T06:43:29.244062+00:00 app[worker.1]: /app/.heroku/python/lib/python3.9/site-packages/pydrive2/auth.py:187: ResourceWarning: unclosed file <_io.TextIOWrapper name='settings.yaml' mode='r' encoding='UTF-8'> 2021-05-08T06:43:30.502809+00:00 app[worker.1]: /app/.heroku/python/lib/python3.9/site-packages/pydrive2/auth.py:187: ResourceWarning: unclosed file <_io.TextIOWrapper name='settings.yaml' mode='r' encoding='UTF-8'> 2021-05-08T06:55:30.802789+00:00 app[worker.1]: /app/.heroku/python/lib/python3.9/site-packages/yaml/constructor.py:49: ResourceWarning: unclosed <ssl.SSLSocket fd=8, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.18.53.222', 43204), raddr=('142.250.65.74', 443)> 2021-05-08T06:55:30.803021+00:00 app[worker.1]: /app/.heroku/python/lib/python3.9/site-packages/yaml/constructor.py:49: ResourceWarning: unclosed <ssl.SSLSocket fd=9, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('172.18.53.222', 53294), raddr=('172.217.15.74', 443)> 2021-05-08T06:55:30.808441+00:00 app[worker.1]: /app/.heroku/python/lib/python3.9/site-packages/pydrive2/auth.py:187: ResourceWarning: unclosed file <_io.TextIOWrapper name='settings.yaml' mode='r' encoding='UTF-8'>

I followed the wiki instructions and referenced #1 on getting the bot up, as far as the config goes I've only got debug_channel, debug_server, and owner filled out and I've 0'd out the majority of the rest.

MizaGBF commented 3 years ago

Long story short, it's intended. The GBF_access cog is a special case and needs some specific setup to work.
It's not documented anywhere on purpose, because it could, in bad hands, be used for some nasty stuff.
As a result, I won't detail the process, sorry.
It might change in the next version, as I'm rewriting it from scratch in preparation for the v2 of discord.py but no promises. If it's for a /gbfg/ crew, I can probably provide you an invite link with my fully functional version, just contact me (I have limited resources on my host so I'm not giving it to everyone).