tepid oyster
I cannot bandadge myself. it completes the circle and does nothing.
When destroying enemy garrisons the circle is glitched out and does not show properly.
When spawning in the timing is off.
Not sure how you broke these things but please stop messing with the game.
Thanks
high cloud
It’s not t17 or related to the update. This is a server side issue, the GSP already communicated to affected server owners. The solution is for the server owner to restart their server to apply a one time fix.
long lodge
It’s not t17 or related to the update. This is a server side issue, the GSP alre...
Nothing in #telegrams ?
high cloud
Nothing in <#322320603350827010> ?
It’s only relevant to server owners but here you go
From qonzer
As you know we've done extensive testing with Team17 to diagnose and solve the performance issues presented in U18 & U19. On Thursday a patch was released which was aimed towards fixing graphical issues however it was quickly reported that some strange abnormalities was occurring in-game. We very quickly found the cause which was the result of our performance tweaks that were made to improve performance in the previous patch.
These performance tweaks became active upon updating the server thus creating the problem.
A simple restart of the server will resolve the issue and all files are returned to the standard state.
I apologise for any issues caused and will keep all users updated if anything further is required.
Best Regards,
Turion```
pure wyvern
I play on Circle (EU) and, according to their admins, their servers were rebooted.
When I played on one of their full servers (#5), though, the issue was still present as badly as before.
I joined one of their empty servers (#6) and it was totally fine, even when ~10 more players joined.
An hour or so later, I rejoined server #6 (which used to be scarcely populated and fine). This time it was full... and laggy again!
faint token
I play on Circle (EU) and, according to their admins, their servers were reboote...
only Circle 2 was restarted yesterday AFAIK. This statement wasn't seen before servers were seeded, and no players mentioned the issue outside of Circle 2
pure wyvern
Right, makes sense. I can definitely say that, when I asked, many players in-game did reply they also experienced the same problems on those servers. Maybe they just weren't bothered enough to report it