Code: Haynar * Fixed some weirdness with disbanding from a group, when you have a non-group member targeted. * Fixed a client desync issue. * Horses should now be useable while levitating over water. * Added some netcode changes. This is to help with desyncs and crashes when zoning. Robregen * Revert "fixed a possible world crash." Database: Robregen * Fixed Tigeraptor Tunic recipe.
With netcode. It is always something that needs real use tests under load. I found two real issues. That could contribute to issues ppl were having. One caused you to zone super super slow. If you made it at all. That was a tricky one. Hopefully we see some improvements all around. H
We had a viral link death last night in VT. 20ish of the 50 person raid all went LD within seconds and groups got bugged. Only once -- We haven't had that happen since early NTOV, I think.
We had a lot go LD as well last night when running to the new raid target. Group was bugged for me where the characters would claim they already were considering another group invite, but had none.
I understand there are datacentre hosting issues going on, p99 is suffering too. When I was getting timeouts in-game, I checked takp forums and p99 forums and they were timing out the same.
That makes a lot of sense then. I believe the vendor they use for their connection is the same too I believe.
I saw a weird double invite to a group last night. If you see weirdness like it saying you are invited. Or anything looking to bug groups. Thats important. Post as many details. Like if you were previously in a group. There may be something with disbanding not clearing status or something. I will look at it. H
The character that couldn't be invited that I mentioned had a very long zonetime (2-4 minutes?) just before this happened. The other characters zoned correctly in 30 seconds or less before. No matter who tried to invite this character, they would get the message they were already considering another group. Logging the character to the character screen and back in cleared the problem.
Today I had a weird crash on all 3 clients at the same time. Two clients were in Everfrost, 1 was in POK, all crashed to desktop at the same time. This has never happened before to me, no desync, just straight to desktop. Windows 10 here, great LAN connection. Very unusual for me.
My relevant log snips from the mass-LD and group bug last night: Code: [ Only registered users can see the bbcode. Click Here To Register... ]
Can't edit. More Details: Mass LD, Tarkon was in my group, and was the only one in my group who went LD. When he back logged in, my group UI behaved as though he had zoned in (a greyed out health bar, then red health bar at 0 going immediately up to full) He did not see himself in a group. My group saw him in our group and raid. Could not invite him on CadsuaneY, group leader: Kicked him from group on CadsuaneY: [Wed Apr 17 21:16:11 2019] You remove Tarkon from the party. Some automatic group leader reassignment, as whole group left raid Reinvited and things worked fine.
Data center had issues last night. Mass LD was related to that. P99 is located at same datacenter. They had mass linkdeads too.
All 3 going LD is related to your connection to the server. It has been glitchy for last day. Not as bad as last night. But periodic issues with some ppl today too.
Takp is quality. Data Center issues arn't something to get upset over. O M G, Thank you for this fix!!
I was raid invited last night, while my toon was the group leader it did not indicate it as such on the raid window so could I actually invite someone. The buttons were active to invite but it just wouldn’t work. There was no group leader status for any of my toons in my 3 man group. But before that I was invited by someone else and his 3 disbanded so I was still in the “original group” if that makes sense. So not sure with him inviting my 3 then us traveling from pok to ToV and then him disbanding caused the group leader issues in the raid.
