Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

websocket #39

Open
MaksDragon opened this issue Mar 26, 2023 · 6 comments
Open

websocket #39

MaksDragon opened this issue Mar 26, 2023 · 6 comments

Comments

@MaksDragon
Copy link

#3 - Restarting client...
[TerrariaChatRelay] | [Discord]: Error: WebSocket connection was closed
[TerrariaChatRelay] | [Discord]: Attempting to reconnect in 10 seconds...

@MaksDragon
Copy link
Author

how i can fix that? websocket connection was closed everyday..

@Exeden
Copy link

Exeden commented Apr 6, 2023

same

@memella
Copy link

memella commented Jul 2, 2023

Also experiencing this issue

Using TShock - full log section:

Server executed: /reload.
Port overridden by startup argument. Set to 25570
Startup parameter overrode maximum player slot configuration value.
[TerrariaChatRelay] | [TCRDiscord.ChatClient]: Disconnecting TCRDiscord.ChatClient...
[TerrariaChatRelay] | [TCRDiscord.ChatClient]: Disposing TCRDiscord.ChatClient...
[TerrariaChatRelay]: Connecting clients...
[TerrariaChatRelay]: TCR.Discord.TShock Connecting...
Configuration, permissions, and regions reload complete. Some changes may require a server restart.
: [TerrariaChatRelay] | [Discord]: Error: WebSocket connection was closed
[TerrariaChatRelay] | [Discord]: Attempting to reconnect in 10 seconds...
[TerrariaChatRelay] | [Discord]: Unable to establish a connection after 5 attempts.
[TerrariaChatRelay] | [Discord]: Please use the reload command to re-establish connection.

@MaksDragon
Copy link
Author

i think this plugin not supporting anymore

@liubquanti
Copy link

I found a reason!
Simply you must change "MESSAGE CONTENT INTENT" parametr in your bot setings on Discord Developer Portal.

@memella
Copy link

memella commented Aug 5, 2023

I found a reason! Simply you must change "MESSAGE CONTENT INTENT" parametr in your bot setings on Discord Developer Portal.

that was all fine on my end, my bf ended up editing the one of the main dll's something about the polling or checking error messages - it was only displaying them while on a debugging mode or something so he made them show also when not on debugging (sorry I can't be more specific, this is his wheelhouse not mine)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants