on my discord all emojis are already displayed as 1 even no one has yet reacted on it after reacting on it it changes to 2 and again one and reg player but in in starting its till 1 i dont know its bug or not but am facing this issue since few days also updated to latest version which is just added few hours ago

also new update with latest amonguscapture.exe when i input code among us discord says
in error log
2020/09/25 12:29:30 Detected transition to Menu; not doing anything about it yet

sometimes the bot will only partially unmute the people alive, even with a 450ms delay of discord commands

So the discord portion is saying "this websocket is not associated with any guilds" and "no in game player data was found matching that color!" Please Help.

Would be nice to automatically select a voice channel to autotrack if there is one with the same name as the text channel within (or maybe without? Some servers group these differently) the same group

Looks like the Bot is having issues muting tracked players in a tracked lobby.

2020/09/15 19:28:51 HTTP 400 Bad Request, {"message": "Target user is not connected to voice.", "code": 40032}
2020/09/15 19:29:50 Issuing mute request to discord
2020/09/15 19:29:50 HTTP 400 Bad Request, {"message": "Target user is not connected to voice.", "code": 40032}
2020/09/15 19:29:50 Issuing mute request to discord
2020/09/15 19:29:50 HTTP 400 Bad Request, {"message": "Target user is not connected to voice.", "code": 40032}
2020/09/15 19:29:50 Issuing mute request to discord

I'd be nice to have a support for a dedicated music user. It would be a reverse of other users mute status. Unmuted during the game and muted at discussion time.

Whenever I use the command ".au start". The bot says it is not connected and in the console it is giving this error: HTTP 400 Bad Request, {"emoji_id": ["Value":" is not snowflake."]}

Windows defender is flagging AmongUsCapture.exe as containing Trojan:Win32/Emali.A!cl

We need to do this

With default settings, running the executable with the "discuss" flag, I see the following:
Using .env-provided resolution: 1920x1080
Capture Settings:
Tesseract Path: ....
Fullscreen: True
Resolution: 1920x1080
Discussion Bounds: [537,97]-[1305,205]
ending Bounds: [326,108]-[1574,324]

OCR Results:
[who ts the imaoster? ~]

So right off the bat (and looking at the temp.png) it's only capturing the top bar of "Who is the imposter", which matches the discussion bounds with a height of 108 pixels. I just have no idea why it's only 108 pixels. My game is fullscreen at 1920x1080, and the screen resolution is the same.

I followed all the steps and when a game was started we were never muted. The command line just repeats "waiting for game to begin". is there something I missed?

When still in pregame, closing the chat will mute all.
There should be an exception if the game hasn't started yet.

Currently we just iterate through an un-sorted player list when doing mute/deaf handling.

https://github.com/denverquane/amongusdiscord/blob/master/discord/guild.go#L117

It would be in our best interest to sort this iterator based on in-game alive-ness (with alive players being first) to ensure that there is no potential for audio sneaking through rate limited requests.

The bot doesn't add any reactions automatically.

I'm wondering if I have to do that manually, or if I'm doing something wrong.

The commands with the prefix .au are not working when typed in the server. I accidentally closed the game while playing and 10 players in my server were left server muted

.au dead @Myname doesnt make a lot of sense when most of the time people will report themselves as dead when starting a meeting (not before or else people will see in chat someone has died).

Also to hide that someone is typing in chat that they're dead, it would be far better to just DM the bot and have it register the person as dead, else people can see someone typing in chat

Hey. This is brilliant bot. Thanks for the same. I was just going through some stuff and found that heroku lets you host a discord bot for free. Are you aware of the same? Maybe you can try it out? Sorry if this seems silly.

Thanks and Regards,

you should make it so that if everyone names themselves after their discord the bot will automatically see they are dead in the game and see the username is the same as one in the discord vc and keep them muted automatically

So it just came to mind that it would be great if you could add a command (that can be locked to a single role), that would be able to turn off the looping of the server mutes. Like you type in the command into discord and after that the bot only mutes people once and ignores it until further inputs. If the bot messes up once we just get stuck with no ability to speak currently.
For that part a force unmute would be great too. Not the current one but one that actually makes it stop muting people until a new input comes in (new round etc.)

All other steps working correctly and the game is in fullscreen.
But it is still stuck on that message.

I assume that it is possible to detect a crewmates win by detecting the "Confirm Ejects" text.

When it says "0 Impostors Remains", it can be considered as a crewmates win - game over.

At this point the bot should already think meeting is over (cause we had the results) and try to mute all. This case should stop to mutes and unmute all.

Would it be possible to have the bot move the dead players to a "dead chat" channel?
The idea would be that the dead person is moved after the discussion on the round of the player's death.
Then all dead players would be brought back into the "general" chat (but muted) during the discussion, and back to the "dead" channel (unmuted) for some fellow ghost banter.

Things that would be needed:

• Add a second channel bot assignment to "dead chat"
• Permission granted to move players back and forth
• Keep the currently dead player in "general" channel until after the discussion on the round of their death

We'd love to be able to remove the reactions from the lobby message, they eat up a lot of requests and are still a bit cumbersome for players on mobile.

Now that the capture client is able to emit events for chat messages, we should generate a link number for each player. When a player puts that number into the in-game chat, we link their AU Data like before.

The link codes can probably just be 1-10 or 0-9. In the discord lobby message we put the tracked member's names along with their code. A single digit code should be easy enough to relay via voice for people on mobile who can't app switch.

Example

LOBBY MESSAGE

Linked Players:
@Soup	:aured:
Link Codes:
~@Soup 	1~
@Kyle 	2
...

I think it would be nice to customize a few things via a config file. Some of these would be:

• prefix [prefix] whatever prefix to call the bot commands you would prefer
• permissions [all/owner/admin] would be "all","owner" and "admin". would basically change who can actually use the bot.
• custom emojis [true/false] a true/false setting that would if true, add the custom emojis. if false, use default emojis
• defaults [a,b] Would have multiple values. "a" is default region, "b" is default voice channel.
• mute [instantly/discussion] Allows you to set when players are muted when dead. You can make them mute once discussion when everyone is aware they died, or have them mute on death, to prevent people giving it away.
• status [text] Set the status of the bot.

The bot can recognize the starting screen, but won't unmute people when emergency meetings are called or when the game ends.

The amongusdiscord.exe part of the bot seems to crash. It crashes more frequently when muting/unmuting players at the beginning of the round, however has happened in the middle many times.

I tried about 8 times but was unsuccessful in completing a whole game without it crashing.

I trialed the bot several times with just myself and an alt account and it worked fine. however once playing with 8 people in the discord it crahes.

The final log messages before crashing was:
HTTP 404 Not Found, {"message": "Unknown Message", "code": 10008}

I was using version 2.0.3 but did encounter the same problem in the couple of times I tested 2.0.4

Thanks

When trying your bot out, i noticed that while in game, the current state does not change to tasks after a discussion ends.

I used the 2.0 Prerelease but have the same problem when building the current master branch of AmongUsCapture from source

It seems that the meetingHudState doesn't get updated properly, it stays < 4

So if you .au end in the middle of a task phase, all users will remain muted/deafened until a discord admin manually unmutes/deafens. :)

This bot is great, thank you!

I haven't had any trouble with it, so it would be nice to run it without having it send game messages in Discord. I don't want our text channel to be filled with bot messages.

Could you add the option to have the bot not send messages related to the game?

I do want the bot to be able to receive commands in a text channel, and reply that it understood the command. I just don't want it messaging every time it mutes and unmutes players.

The Bot doesn't recognize the discussion when you are dead.

Screen resolution: 1920x1200
Game resolution: 1920x1200

Anyone else have this issue? Just says waiting no matter if I launch game first or before loading the app. Sometimes it'll detect then get stuck in waiting for discussion or game to end but doesn't do anything or recognize the game has started or discussion ended.

Several users have requested the ability to configure the bot's command prefix (default .au).

We can adapt an implementation from resources like this

I just wanted to throw this out there as an option for making the bot more autonomous and not needing to be run on a players computer. The problem with this is having to share a bot token with other users who might use that maliciously. Which limits the amount of people in a server being able to use the bot.

Idea 1
Instead of having the player run it on there PC just have them live stream instead. Have the bot search a specific voice channel for players live. When it finds a player live (or maybe make it a command to like .au startgame or something) it looks at there live stream to watch the among us game and uses that data to auto-mute/unmute.

Idea 2
Make a client side bot and server side bot. Server side bot is always running. Player runs client side bot and it connects to server side of the bot that is running on the discord servers and it transfers that data of the screen captured to the bot running on the server side which does all the actions.

I am not a dev and honestly have no idea if these things are super difficult to do or not. I just thought I would make the suggestion from a user who likes the idea of the bot but has a problem where its only used when I am online because I dont want to give out a bot token to random people in my community.

"room" in "room Code"
"region"

Super minor issue

I notice i got some problem when i win/lose a game like impostor. Bot doesn't detect when game finish

It's working nice, I like it!

Would be nice to have an .au reset command that resets everything (Especially the mutes) because if I take down the processes mid game the voice channels stay muted until I restart everything and trigger some event like getting in a lobby, this way if the server crashed, I can restart it and reset.

Or better yet, the bot should make sure to reset everything on shutdown (unmuting channels) and on startup

Add a command that will provide the user a key to be used when connecting the capture software to the discord bot. I currently submitted a pull request in the capture software to allow the user to change the host it can connect to, with this anyone can connect to the bot and control whatever game they like. If a key is provided for a new game instance and only using that key can the game instance be controlled, the security issue is avoided when connecting to the discord bot server is opened to any globally routable address

If you install Tesseract in anywhere other then default path you get this error

for instance, I installed tesseract in my D: drive and changed the tesseract path in final.env to my new path and still did not work. just give people a heads up you have to install tesseract in the default location

Could the config file given to us (final.env) include where the bot detects the game? My steam configuration is a bit fucky so it doesn't appear.

when run. amongusdiscord,exe says that the tesseract file cannot be found but it is in the right location

version: '3.3'
services:
  bot:
    image: denverquane/amongusdiscord
    ports:
      - 8123:8123
    environment:
      - DISCORD_BOT_TOKEN=<my token>
    restart: unless-stopped

Program exited with the following error:
error loading environment file; you need a file named final.env, final.txt, or final.env.txt
This window will automatically terminate in 30 seconds

To solve the issue in my case I did this

version: '3.3'
services:
  bot:
    image: denverquane/amongusdiscord
    ports:
      - 8123:8123
    environment:
      - DISCORD_BOT_TOKEN=<my token>
    volumes:
      - type: bind
        source: ./final.txt
        target: /go/src/app/final.txt
    restart: unless-stopped

final.txt contains DISCORD_BOT_TOKEN=<my token>

from: #55

good idea here to create a command to store default lobby region and tracked voice channel to the bot.

I'm having a problem where players who are not dead, are marked dead and can't talk during emergency calls because of this. It happened to me at least once when I was imposter myself and second time for another player. Is there a way I can give more details about this? I had to stop using the bot because of this.

As the bot begins the muting process, the program/script crashes mid process. Restarting the program crashes if the game is still in progress

I got this working on mobile but when there is a discussios it just keeps saying "Waiting for Discussion or Game Over...", game start and end work correctly tho.

I've got the docker server running fine via AWS. When doing .au new ABCD eu it provides a connect code.

When I type the code into the newest standalone amonguscapture .exe nothing happens at all. Not sure if this is expected behaviour? When I try it completely locally it works fine first time with no issues.

the bot works BUT it only mutes SOME people. no one has any roles and they are in the same channel so i have no idea why this is happening

Barring some mechanism for the bot to auto-detect dead players (which would be fantastic!), it'd be great if the bot could accept commands via direct message in addition to the text channel. That way, players could privately mark themselves as dead when they die.