search

xNarnia / TCR-TerrariaChatRelay

Self-serving Terraria Chat Relay with extensible chat service support
https://forums.terraria.org/index.php?threads/tcr-terrariachatrelay.78196/
MIT License
32 stars 16 forks source link

websocket #39

Open MaksDragon opened 1 year ago

MaksDragon commented 1 year ago

3 - Restarting client...

[TerrariaChatRelay] | [Discord]: Error: WebSocket connection was closed [TerrariaChatRelay] | [Discord]: Attempting to reconnect in 10 seconds...

MaksDragon commented 1 year ago

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

Exeden commented 1 year ago

same

memella commented 1 year ago

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 commented 1 year ago

i think this plugin not supporting anymore

liubquanti commented 1 year ago

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

memella commented 1 year ago

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)