WARNING! Can't enter GR public at Torment XVI

General Discussion
1

There was a problem searching for a public game (code 24004)
There was a problem joining the game (code 24004)
Am I the only having this problem??

1 Like
2

Nope. Same. Last two days.
Blizzard please replace the hamster. its Dead.
Until fixed, many people running GR through Rift games. Just join rando Rift.

4 Likes
3

There’s been a Technical Support thread all about it for weeks now. Blizzard have asked people experiencing the problem to provide them with requested information…

…so, provide the information, and put it in that thread to help them determine the cause.

1 Like
4

Same in here posted in bug, I could not use the Win Mtr properly maybe you guys can help us further!

5

The post I linked to contains a link to a Blizzard article telling you exactly how to download and run WinMTR, how to export the results, and how to paste it into a forum thread but here you go…

Running WinMTR

1 Like
6

Nope. Game still broken and unplayable. Bliz fix please.

1 Like
7

Here’s my WinMTR. Hope Blizz can fix this 24004 issue at T16, GR public entry.

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             openrg.home -    1 |  150 |  149 |    1 |    5 |   77 |    4 |

|                            10.240.178.5 -    0 |  154 |  154 |    9 |   18 |   71 |   13 |

|                           67.59.241.246 -    0 |  154 |  154 |   10 |   18 |   64 |   17 |

|          ool-4353f594.dyn.optonline.net -    0 |  154 |  154 |    9 |   23 |   92 |   19 |

|                           67.59.239.117 -    0 |  154 |  154 |   12 |   21 |   89 |   16 |

|              451be0c6.cst.lightpath.net -    0 |  154 |  154 |   14 |   23 |   68 |   18 |

|                   nyk-b3-link.telia.net -    0 |  154 |  154 |   13 |   24 |   91 |   23 |

|                  nyk-bb3-link.telia.net -    0 |  154 |  154 |   15 |   24 |   82 |   16 |

|                  chi-b21-link.telia.net -    0 |  154 |  154 |   30 |   39 |   96 |   51 |

|  blizzard-ic-348622-chi-b21.c.telia.net -    0 |  154 |  154 |   30 |   43 |  151 |   35 |

|              ae1-br01-eqch2.as57976.net -    0 |  154 |  154 |   74 |  102 |  769 |   80 |

|                          137.221.65.132 -    0 |  154 |  154 |   74 |   87 |  136 |   88 |

|         et-0-0-2-br01-eqla1.as57976.net -    0 |  154 |  154 |   73 |   88 |  172 |   93 |

|                           137.221.68.83 -    0 |  154 |  154 |   73 |   87 |  170 |  129 |

|                           24.105.30.129 -    0 |  154 |  154 |   74 |   85 |  143 |  123 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like
8

Just join public GR games GR on T15. Lots of people there.
Blizzard cant be bothered to fix this.

2 Likes
9

I have no doubt that Blizzard Classic games must have a back log of thousands of bugs to fix in this game.

Also: Some bug fix’s cause other bugs to pop up.

This is the problem with fixing code written for core game over 5 years ago.
And D3 is over 8 years old.

I feel a bit sorry for the classic game programmers.

They are so busy with so many issues and have many limitations too.

I’ll bet they are not allowed to touch core game.
Also, many tools that were available 5 years ago are gone with Activision’s idea to save money and get rid of “in their mind”, useless stuff.