I'm d/c'ing every 5-10 seconds while hitting mobs when i'm alone on the map. When there are other people than me it doesn't happen. It's like this since Friday. I've been merching whole two days with my shop surviving 10 hours without disconnect before... And now I can't do anything lmao.
At first, it happened on my islander only, but i didn't really care, because i just logged on to check out how's royals going. That was like two weeks ago. Now, after I came back, I've trained my islander from 51 to 52 and leeched my friend from 11 to 15 on F/P mage without any problems. Disconnect issue came back when I made my warrior and it was happening on both my islander and warrior while grinding since then. Few hours ago I was able to train warrior from 20 to 21, even though it was laggy as hell it didn't d/c me. Now, five minutes ago when I tried to grind my Warrior, it dc'd me after like 15 seconds. Right after d/c I hopped onto my Islander, was grinding for straight minute, and it didn't d/c me or even lag. That's weird. I've made a video to show how it looks like:
Agree, this is unplayable. This video represents my situation perfectly for the last month or more. Please guys, do something about that.
Looks like I'm not the only one who experiences this problem. Let's hope staff will try to fix it immediately.
Ill try and throw some water on this fire. First things first, we need to isolate the problem, can you please run a traceroute to the mapleroyals server you can get the IP from the resource manager in windows when you are connected to maple royals. The IP I observed is (45.34.6.3) this may change (staff if the server ip should not be here please remove it or let me know and i will remove it) Here is a link to how to run a trace route. Please Private message the output of Traceroute to staff. do NOT post the log into the forum as it will contain your IP and other information. https://kb.intermedia.net/Article/682 The output will tell us what we are dealing with and who's fault it is, this could be an American ISP issue in the backbone someone playing dirty with internet routes. who knows.
since we suffer from the same issue Ill post my tracert dump here aswell. Code: C:\WINDOWS\system32>tracert 45.34.6.3 Tracing route to unassigned.psychz.net [45.34.6.3] over a maximum of 30 hops: 1 18 ms 15 ms 6 ms 2 11 ms 12 ms 10 ms 3 16 ms 32 ms 15 ms 4 112 ms 110 ms 111 ms 5 190 ms 182 ms * 6 190 ms * 172 ms xe-7-3-1.cr0-mia1.ip4.gtt.net [77.67.78.85] 7 190 ms 188 ms * et-5-1-0.cr4-dal3.ip4.gtt.net [89.149.135.229] 8 189 ms 201 ms 208 ms ae3.tinet-dal.AS40676.net [104.216.247.69] 9 189 ms * 203 ms edge-dal.AS40676.net [104.216.247.3] 10 198 ms 205 ms 190 ms unassigned.psychz.net [45.34.6.3] Trace complete. C:\WINDOWS\system32> Second attempt : Code: C:\WINDOWS\system32>tracert 45.34.6.3 Tracing route to unassigned.psychz.net [45.34.6.3] over a maximum of 30 hops: 1 * 20 ms 41 ms 2 11 ms 13 ms 19 ms 3 * 14 ms 62 ms 4 110 ms 111 ms 109 ms 5 180 ms 193 ms 179 ms 6 * 180 ms 172 ms xe-7-3-1.cr0-mia1.ip4.gtt.net [77.67.78.85] 7 * 190 ms 200 ms et-5-1-0.cr4-dal3.ip4.gtt.net [89.149.135.229] 8 204 ms 192 ms 190 ms ae3.tinet-dal.AS40676.net [104.216.247.69] 9 298 ms 670 ms * edge-dal.AS40676.net [104.216.247.3] 10 188 ms 188 ms * unassigned.psychz.net [45.34.6.3] 11 204 ms 190 ms 191 ms unassigned.psychz.net [45.34.6.3] Trace complete. C:\WINDOWS\system32> anyways it will probably be different since every pc and ISP is different. So OP if you see this, post yours aswell.
@DarkWolf if you want to post your logs I recommend you blank out some of the IP's from lines 1~5 just to protect your location and IP address. I also ran a tracert here are my results (I would like to clarify that I am not having any connectivity issues to the server) Code: 1 2 ms 1 ms 1 ms 2 17 ms 14 ms 13 ms 3 * 11 ms 13 ms 4 15 ms 13 ms 15 ms 5 14 ms 12 ms 16 ms 6 16 ms 16 ms 13 ms 7 14 ms 14 ms 15 ms 8 30 ms 30 ms 28 ms 9 38 ms 36 ms 37 ms 10 95 ms 49 ms 48 ms 11 58 ms 58 ms 58 ms 12 72 ms 59 ms 58 ms ae5.telia.DAL.us.AS40676.net [104.216.247.73] 13 145 ms 83 ms 424 ms edge-dal.AS40676.net [104.216.247.3] 14 60 ms 59 ms 62 ms unassigned.psychz.net [45.34.6.3]
@DarkWolf yea its better. your having the same issue that the OP is correct? Just some info to understand what all these numbers mean. -all the asterisks in the tracert are packets that never got acknowledged or were lost. -the numbers with ms are 3 round trip pings to each hop so that's the time for the message to get to the address and back. 1000ms is 1 second. -the first line or "Hop" should be your internal network (your router/modem) @DarkWolf a packet lost and 20~40ms latency at your internal network is not so good, for example im at 1~2ms latency over wifi. To look further into this I used a software to force a added 150ms of latency to my connection with MapleRoyals and added a packet loss of 5~30% and i managed to simulate the exact behavior that was in the OP's youtube video. 5% was annoying but playable, 20% was bad but no dc, 30% was exactly what the OP posted. I would conclude that the issue the OP and you are having is related to packet loss between your computer and the maple royals server and not the maple royals server itself. This may be related to one of the hops dropping lots of packets or something inside your home network is dropping packets. I would recommend plugging directly into your modem and testing maple royals to see if its any better maybe its your router or wifi (to defend blaming your home network I would look at HOP 1 of your second tracert having a * which should not happen). here is my simulated +150ms latency + 30% packet loss Code: 1 162 ms 159 ms 159 ms 2 165 ms 199 ms * 3 173 ms 200 ms 201 ms 4 197 ms 201 ms 196 ms 5 192 ms 198 ms 201 ms 6 * 181 ms 198 ms 7 196 ms 254 ms * 8 186 ms 197 ms 199 ms 9 203 ms 202 ms 197 ms 10 212 ms 237 ms 209 ms 11 227 ms 239 ms 238 ms 12 240 ms 241 ms 235 ms ae5.telia.DAL.us.AS40676.net [104.216.247.73] 13 258 ms * * edge-dal.AS40676.net [104.216.247.3] 14 399 ms 399 ms * unassigned.psychz.net [45.34.6.3] 15 * 407 ms 403 ms unassigned.psychz.net [45.34.6.3]
@WatIsHarbor local network packet loss would affect everything. Packet loss in the internet backbone would be hit or miss depending how the traffic gets routed. So if you lived in The UK and the Maple Royals server is located in Texas that is 1 route, that could drop packets, but if you say wanted to play some CS:GO and connected to a server in France it would take a different route where the network hardware between you and the server is not dropping packets. If there is no packet loss in your home network, and maple royals works fine for 98% of the the community. Its out of our control... edge-dal.AS40676.net [104.216.247.3] This may be the culprit, but I haven't seen your tracert. That was the hop with the highest ping for me, and @DarkWolf had packet loss on both of his tracert's. But really this is just a poke in the dark.
