Tree of Savior Forum

Bug after every maintenance - System : please try later - no chats available

Date and Time:
Today 08/08/2017 and every weeks after maintenance

Server Name:
Fedimian

Team Name:
Kestryk

Character Name:
All characters

Bug Description :
I just connect on the game after maintenance and I’m unable to chat either with the guild, party or whisper anyone. Normal chat works.

Any auto-Matching in dungeon give me the message “Please try again later”

I’ve already across the different occurrences try to: Create a character in a new server : Worked only one time.
I kept creating/deleting character in every server since then, everytime.
Relog a 1000 times
Delete the game and reinstalled the game 2 times
Restart the computer
Repair game
Try different connections
Clear Steam cache
Flush DNS
I tried everything that I know of to be honest.
The issue gets fixed randomly after a little while but keeps happening after almost every maintenance.

My friends see me disconnecting and reconnecting in a loop:

I wrote 2 tickets to the customer support about this and I got the same answer that the studio were looking into this but it starts to be a little bit annoying by now, I fear every maintenance.

Screenshots / Video :
I give you a video of it: https://youtu.be/Ukz7gpWfsAE

It happens on 2 different computers, I don’t think the hardware is directly related. On other server I can normally chat apparently.

Please my studio-kenobi help me, you’re my only hope :cold_sweat:

@STAFF_Letitia @STAFF_Amy @Allthepeopleintheworld

So I think I understand what is happening. The game has been logged on 2 computers. Even if both has been logged of after a maintenance somehow the game acts weirdly and one of the computers is trying to log in in vain. When I closed my computer at work (asked someone to do it for me) I could log normally.

This explains why my friends kept seeing me connecting in a loop.

People, if you ever have this issue, try to see if you haven’t use the game on several computers.

Thanks, hopefully I’ll be able to fix this for future instances.