inhouse_bot icon indicating copy to clipboard operation
inhouse_bot copied to clipboard

Discord update solution

Open literallyfabin opened this issue 3 years ago • 18 comments

discord had an update in which the bot stopped working, which in this case commands like prefix ''!, %, $'' don't work. Would you be able to update to commands like /queue top ?

literallyfabin avatar Sep 01 '22 21:09 literallyfabin

Same issue for me as well. As all commands on discord with the bot don't work anymore

spiralwind avatar Sep 02 '22 01:09 spiralwind

let me know if you find a solution please

yenoww avatar Sep 02 '22 02:09 yenoww

So the fix to this in to add " INHOUSE_BOT_COMMAND_PREFIX: COMMAND_HERE(default is !)" in your docker_compose.yml file and run docker-compose up so it recreates it and your all good

spiralwind avatar Sep 02 '22 05:09 spiralwind

As written in the README.md:

As discord.py is not maintained anymore and the LCS player association has developed its own matchmaking system, this bot is not maintained anymore as of December 2021.

It was known that Discord was developping breaking changes that would make the bot require a rewrite unfortunately. I don't have the time to handle that at the moment.

I'll leave the thread open so people can see it here too, but a good title would help.

mrtolkien avatar Sep 02 '22 15:09 mrtolkien

To end this discussion, the solution that worked was as follows: putting "intent.messages = True" in inhouse_bot.py file

(Along with what our friend spiralwind said above)

So the fix to this in to add "INHOUSE_BOT_COMMAND_PREFIX: COMMAND_HERE(default is !)" in your docker_compose.yml file and run docker-compose up so it recreates it and your all good

With that the bot works again through the command ''/''

literallyfabin avatar Sep 03 '22 00:09 literallyfabin

but wouldn't I have to have cloud access to modify the inhouse_bot.py file? If it's possible to fix the bot and you can help me.. call me on discord Rodrigoo#1939 (I'm Brazilian)

yenoww avatar Sep 03 '22 16:09 yenoww

Conseguiram resolver o bot do inhouse bot? Did you manage to solve the inhouse bot bot?

adryel97 avatar Sep 07 '22 03:09 adryel97

Coloquei INHOUSE_BOT_COMMAND_PREFIX: COMMAND_HERE(default is !) e não voltou a funcionar.

I put INHOUSE_BOT_COMMAND_PREFIX: COMMAND_HERE(default is !) and it didn't work again.

adryel97 avatar Sep 07 '22 03:09 adryel97

@literallyfabin conseguiu resolver? não sei como modificar a .py ja que é no docker. Tem como dar uma força ? possuo um servidor grande e preciso colocar o bot do inhouse pra funcionar. Me chama no disc CBLIXO#0068 te dou uma grana se ajudar!

DBVSF avatar Sep 07 '22 04:09 DBVSF

yeah, what are the details needed to login to adminer?

Euphener avatar Oct 21 '22 07:10 Euphener

yeah, what are the details needed to login to adminer?

it was failed to mention but It the same process as done on the youtube tutorial but he forgot to add for the that the username: postgres

spiralwind avatar Oct 21 '22 16:10 spiralwind

Yeah sorry, I did that and it still doesn't work :/ , it just says "connection refused"

Euphener avatar Oct 22 '22 01:10 Euphener

you need to make sure that the you wrote everything right so below System: PostgreSQL Server: db username: postgres password : whatever you set in the POSTGRES_PASSWORD:____________ in docker-compose database: whatever you set in POSTGRES_DB:___________ in docker-compose

spiralwind avatar Oct 22 '22 23:10 spiralwind

you need to make sure that the you wrote everything right so below System: PostgreSQL Server: db username: postgres password : whatever you set in the POSTGRES_PASSWORD:____________ in docker-compose database: whatever you set in POSTGRES_DB:___________ in docker-compose

thank you man, helped out a lot

Euphener avatar Oct 24 '22 03:10 Euphener

someone has able to find how to edit the inhouse_bot.py? to put "intent.messages = True" in inhouse_bot.py file

To end this discussion, the solution that worked was as follows: putting "intent.messages = True" in inhouse_bot.py file

(Along with what our friend spiralwind said above)

So the fix to this in to add "INHOUSE_BOT_COMMAND_PREFIX: COMMAND_HERE(default is !)" in your docker_compose.yml file and run docker-compose up so it recreates it and your all good

With that the bot works again through the command ''/''

Luccaop avatar Nov 07 '22 17:11 Luccaop

Do you know any alternatives or a fix? Trying to set this up

NoatakLoL avatar Nov 09 '22 04:11 NoatakLoL

To end this discussion, the solution that worked was as follows: putting "intent.messages = True" in inhouse_bot.py file

(Along with what our friend spiralwind said above)

So the fix to this in to add "INHOUSE_BOT_COMMAND_PREFIX: COMMAND_HERE(default is !)" in your docker_compose.yml file and run docker-compose up so it recreates it and your all good

With that the bot works again through the command ''/''

Could you please provide more info on how to edit the file, since we do not have the permission to edit files in the original repo?

Cxacho avatar Nov 23 '22 15:11 Cxacho

In the discord development portal, in the guide you have to enable 'Server Member Intent', you must also enable 'Message Content Intent' this is the important step!

In docker compose, under the emojis make sure you enter this in the same tab line, INHOUSE_BOT_COMMAND_PREFIX: '!'
MAKE SURE YOUR COMMAND IS IN SINGLE TICKS

You can change the command to whatever you want, by default it is '!'.

Tr3vvv avatar Nov 27 '22 15:11 Tr3vvv