Message from /calladmin pinging entire Discord
Issue #1 Does not send messages back to server

Issue #2 When /calladmin is sent in game the message created in discord pings the entire discord .Not in the private catagory specfifed with the category id.

Discord  croe version : 0.16.9
Extention : 1.0.6
Can you provide your configuration files and logs? I can't reproduce your issues
i have the same issue   bots set to talk to my admin channel and it just pops open for everybody  and  i cant seem to  talk to  or  get msg from a player 

Merged post

{
"CategoryID": "536413108101578768",
"ReplyCommand": "a",
"SteamProfileIcon": "76561############",
"ShowAdminUsername": true
}

all i get is a msg  and if i reply like i normaly did  it dussrent say anything in game  and players cant type to discord eighter 

this is what i get in discord:

Rusty Tools BOT
today at 18:27
@here New chat opened!
You are now talking to Mighty Mike

bot reply from doing /plugins to see what discord related plugins are installed and it dussent see  call admin 

Discord: List of Discord enabled plugins:
DiscordCore
DiscordPlayers
I have the same issue, i have a channel assigned but it creates a new channel and pings everyone in discord instead of posting in private channel.
for me it dussent even make a channel   and its has admin rights its been like that since the beginning  but dussent seem to get fixed
What role does your BOT have on discord? Try going to `Settings` -> `Roles` -> `Select the BOT's role` -> `Click on "View Server As Role"`.
If it doesn't have access to the category, give it.
{
"CategoryID": "67920939723******",
"ReplyCommand": "r",
"SteamProfileIcon": "76561############",
"ShowAdminUsername": true
}

The Bot has permission for view entire discord.  As for logs the plugin does not have any erros when /calladmin is sent. 

Merged post

Also the channel that the /calladmin command creates in discord is at the very top of the channel listings and not assocaiated with the category/ id. 

Is this problem fixed? Do we know?

Are you sure that you are using Discord Extension 1.0.6 or greater? This bug only happened before the 1.0.6