ive been unable to host on minecraft since the 19th of feb or so. (error is 118-0006) i have "nat type B" and i can host on an account that i made a few weeks ago but not on my main regular account and ive been unable to solve this issue. does anybody know?
#cant host
halcyon spoke
vernal hound
So frustrating, I keep getting this error on the 3DS when I try to play Triforce Heroes. I couldn't get any kind of worthwhile response from anyone about what to do or why it's happening tho. Seems like the developers don't even know
exotic kindle
I've been getting this 118-0006 error since the 12th or 13th of March in Splatoon.
I wait forever and after a few seconds (or immediately) after the match starts, I get this error! 😕😭
north stumpBOT
I've been getting this 118-0006 error since the 12th or 13th of March in Splatoo...
halcyon spoke
I've been getting this 118-0006 error since the 12th or 13th of March in Splatoo...
So are you unable to play splatoon then?
exotic kindle
Basically. I just disconnected eventually.
It's only happened recently, I believe sometime after the update. I don't know specifically the time it changed.
exotic kindle
Same.
I actually remember when it happened; I joined a lobby, started a match and midway I got dropped. Then it said "Maps Updated," and afterward I couldn't stay connected.
halcyon spoke
Same.
I actually remember when it happened; I joined a lobby, started a match a...
Do you think your issue is a due to a bad nat type?
exotic kindle
Maybe, I'll have to double check that later.
halcyon spoke
Maybe, I'll have to double check that later.
Did you check?
exotic kindle
I haven't yet.
exotic kindle
I finally checked, I have NAT B.
Connection seemed fine.
I tested the connection in a match, and I got to exactly 1:59 before I got "connection unstable" 4 times, before I got disconnected.
The second match was super laggy and glitchy, I got to 1:55, got a unstable connection warning, but was able to "finish" the match at the ending timer, but then was dropped.
The third match: no problem.
I believe it might have something to do with regions per server*, the latency, or connection strength.
It could also be the new net code that was deployed recently, causing small disruptions that were overlooked.
*I have no idea the placement of the physical hardware, whether placed solely in one location, or spread out across America. It could very well be that (because it's such a small community compared to the industry) most of the traffic is directed to the heaviest area for players to get faster matchmaking time, at the cost of longer routes which can cause packet loss, and connection errors. Again, I don't know the specifics of the physical hardware, so this is all speculation about what could cause this error.
I could even be wrong about this error being caused by hardware placement, it could be purely connectivity for all I know.
Fourth match: got to 2:34 before I got dropped.
Fifth match: no issues.
Going back to my comment on the physical hardware, the inconsistency of these errors could concur with my argument.
Sixth match: 1:24 got 6 connection issues(lol) then disconnected.