JavaScript is required to use Bungie.net

Help

Help us help you.
7/13/2020 2:52:27 AM
3

Almost banned for trying to fix my nat

While this post is probably going to get ignored, I just really wanted to make it considering the amount of time that I've sunk into this game just to see this message appear. Basically, me and two other friends are going to try trials, but we want to warm up in competitive first. As I try to join their fireteam, I start getting countless error messages (go figure) and decide to use the fix that I always use to get in the fireteam of another player. What I do is I switch my nat type from moderate to open, or vice versa. This has always worked for me and never have I had it where I would get a message like this. Anyways, in this case I changed it from open to moderate, and as always the error messages stopped popping up and everything was running smoothly. My friend starts matchmaking, nothing irregular. As we load in to the comp match, we notice that the other team has 2 people on it. We thought that we were just getting lucky, and we won the match. Next match is the same, except with 1 person. Me and the guys are getting a little confused, blaming it on the matchmaking for the time being. Then the next game is 2 people again. At this point I realized why it was happening, and quickly switched it back to open. While the next game was still with 1 person, the games after were normal 3v3s. I thought nothing of it and just told myself to put my nat on open for next time as so we wouldn't just get free wins. But after getting off for a bit, I come back to the game to see the message on my screen in the attached photo. I'm very shook. My intention was never to try and get an unfair advantage, I was just trying to bypass the countless errors this game is known for. And the fact that just flipping a switch in your network settings can do such a thing like this is honestly baffling to me. I have sunk 500 hours so far into this game, and to get banned for something like this would be an actual nightmare. I'm not sure if anyone knows about this but it really does need to get patched ASAP. Thanks for reading this, it means a lot.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • I had the same issue with disconnects with BEAVER yesterday, that I finally found what I needed to make it OPEN. You won't like it though and I'm about to post my own post about it. but you have to go into your router and port forward the following to YOUR computer TCP: 27015-27030, 27036-27037 UDP: 3074, 3097, 4380, 27000-27031, 27036 Some other posts said if you had UPNP enabled it should do the trick, but on mine it was enabled and my god last night was terrible. Once I made the port forwarding changes, the Stun Test went from Moderate to Open and the games responsiveness was SOOOOO much better and I wasn't getting DC'd, but... you are basically pulling your pants down to bungie AND if you have anyone else in the house playing the game, good luck to them cause you can't port forward all the machines at the same time lol...

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon