Transfer Aborded: instance is full

So not only did I get kicked out, it keeps giving me this message… Tons of lag when you actually do get in time rifts, any plans on fixing this?

Edit: got in, boss already dead, thanks blizz.

5 Likes

Who knows. I just jump up and down spamming whirlwind, hoping it hits the boss 15 seconds later!

6 Likes

i spam your face. down with draenei.

It’s ridiculous.

They need to shard the instance more. Like if more than 20 people enter a portal, make another instance for the other 20 people or something.

2 Likes

Yes. It was stated they’re working on it in the interview the other day.

The Time Rifts make it seem like they’ve done the ultimate RNG implementation: whether or not the game will actually function for a given player trying to do a given Time Rift now depends on the fickleness of the RNG gods.

/moo :cow:

1 Like

If people would stop making raid groups, things would go so much easier.

Don’t blame the players for this. This is 100% on Blizzard for creating a pathetic event that should’ve had sharding and separate instances instead of forcing 200+ players into a disgusting lagfest that is barely functional.

2 Likes

Players creating raid groups when there shouldn’t be has always added to the problem. I never said it was the crux of the problem. Just added stress onto the already messed up implementation.

right? Where’s the sharding they love so much?

1 Like

This whole thing needs to be looked at. From the sharding problems, lag, down to the reward structure. Why is it that a mount costs 3000 and a 250 rep token costs 2500?

1 Like

Aborted /10char

What is the difference between 40 players in a raid group doing the event, and 40 people solo doing the event? It’s still 40 people in the same area. Being in a raid group has absolutely nothing to do with the “Transfer aborted: Instance Full” error or the server-side lag issue. Being in a raid group doesn’t suddenly stress the server more. There are people in raid groups where half can’t get in the portal while the other half can.

1 Like

It is part of the RNG of the game! You didn’t click fast enough. Some would say a skill issue. :rofl:

Hey me too! Also how I did the treasure goblin event… who needs to target thru all that toy spam when you can just spam whirlwind! :upside_down_face:

You know I actually saw someone in another one of these threads tell someone that their getting locked out of the boss was a “you problem” and that if they moved faster next time it wouldn’t happen again. :woman_facepalming:

The 40 are adding to the rest, not swapping them out. Just like we had with the goblin event, just like we originally had with the soup event, etc.

Still a developer problem - if raid groups are an issue the servers can’t handle, then they shouldn’t allow people in raid groups to get any rewards, otherwise they should implement whatever they need to shard raid groups appropriately.

Also, players make raid groups because lots of these events have been so poorly tuned or set up in such a way that trying to complete them solo is a major hassle and or leads to inferior rewards.

1 Like

The basic problem is blizzard needs to take two years off between major patches because they are a crippled company and no longer fiducially responsible or capable of running a dev team that can develop content around reasonable deadlines.

It’s not really the devs fault. They really don’t have a choice anymore. Not the lower ranking devs without access to the C-suite

1 Like

It doesn’t matter if they are in a raid group or not. It’s the sheer amount of people in the area, not the grouping of said people. If there were four 40 man raid groups, or 160 solo players the issue would be the same. Being in a raid has absolutely zero bearing for any of the issues with this event or the goblin event or soup or any outdoor event.

1 Like

Yeah, the raid groups don’t matter. I just saw a bunch of players miss the kill again!