[2019] Chat logs of IVANARMY-BLDX explaining how to dupe in their discord, bonus screenshots of grapeshot developers being in the same discord wtf.

The DM included in the OP was sent to me on the day that conversation occurred. We went in and investigated then tried to reproduce the alleged crash strat multiple times with our QA team and we were unable to repro it. It is possible it was resolved due to the fixes we made in a prior deployment or it's possible this was never achievable. It's also possible that there's more to the exploit, but it's not something we've discovered or have had reported to us yet. If there's anyone who is able to get this to happen, don't hesitate to get in touch as we'd be happy to work with you on it.

In regards to Discord DM's, they're pretty easy to manipulate and whilst we will look into reports we receive based on them, they are not a reliable form of evidence. Furthermore, on the topic of being in Company Discords; I'm in quite a few Discords representing different alliances and networks in game. This has directly helped in alerting us to possible exploits along with giving me insight into metas and game balance. That is not to imply that the best feedback is given by the largest Companies exclusively, I also read all of my DM's, even if I can't always respond. Bugs/exploits and valuable feedback quite regularly comes in from members of Companies with less than 5 players or solo players. Also, I like to be available to the community (where time permits) as a large part of my job is liaison between players and the team.

In relation to dupe reports in general, divulging the details of ongoing investigations would be asinine. There are two aspects related to the outcome of these types of investigations: Technical Solutions (Are players really able to do this? Can we repro it? If so, how do we patch the ability for players to do so moving forward) and Enforcement. Again, going into specifics on our enforcement actions can be detrimental. Hundreds of players have been both BattlEye and manually banned and we have performed quite a few dev-wipes dependent on the severity of the situation and the number of people involved. Suffice it to say, sometimes loud outrage and brigading leads to a fire and, at other times, it just leads to hyperbole and misjudged situations spiralling on the premise of a false narrative. I think it's worth noting that some of the, in my opinion, worst cases of exploiting and cheating that have led to us disbanding entire Companies, banning all members and dev wiping haven't even created a blip on the Community radar.

The DM included in the OP was sent to me on the day that conversation occurred. We went in and investigated then tried to reproduce the alleged crash strat multiple times with our QA team and we were unable to repro it. It is possible it was resolved due to the fixes we made in a prior deployment or it's possible this was never achievable. It's also possible that there's more to the exploit, but it's not something we've discovered or have had reported to us yet. If there's anyone who is able to get this to happen, don't hesitate to get in touch as we'd be happy to work with you on it.

In regards to Discord DM's, they're pretty easy to manipulate and whilst we will look into reports we receive based on them, they are not a reliable form of evidence. Furthermore, on the topic of being in Company Discords; I'm in quite a few Discords representing different alliances and networks in game. This has directly helped in alerting us to possible exploits along with giving me insight into metas and game balance. That is not to imply that the best feedback is given by the largest Companies exclusively, I also read all of my DM's, even if I can't always respond. Bugs/exploits and valuable feedback quite regularly comes in from members of Companies with less than 5 players or solo players. Also, I like to be available to the community (where time permits) as a large part of my job is liaison between players and the team.

In relation to dupe reports in general, divulging the details of ongoing investigations would be asinine. There are two aspects related to the outcome of these types of investigations: Technical Solutions (Are players really able to do this? Can we repro it? If so, how do we patch the ability for players to do so moving forward) and Enforcement. Again, going into specifics on our enforcement actions can be detrimental. Hundreds of players have been both BattlEye and manually banned and we have performed quite a few dev-wipes dependent on the severity of the situation and the number of people involved. Suffice it to say, sometimes loud outrage and brigading leads to a fire and, at other times, it just leads to hyperbole and misjudged situations spiralling on the premise of a false narrative. I think it's worth noting that some of the, in my opinion, worst cases of exploiting and cheating that have led to us disbanding entire Companies, banning all members and dev wiping haven't even created a blip on the Community radar.

Interesting video, will check it out. Thanks for sharing.