For the last several weeks, the introduction of third-party bots to online matches – in Competitive Playlists, especially – has understandably been a very active topic among the Rocket League community.

Earlier today, we took action against a number of accounts running bots in Rocket League. This banwave should cover the vast majority of accounts that have used bots since they first appeared in online matches towards the end of 2022, and we will continue to monitor for bots and take appropriate action against any players/accounts using them. Furthermore, to help us address bots in future matches, we have added a “Cheating” report reason back into the game. You can find this in game on the report reason list in the Report/Block menu.

Finally, we are taking steps to introduce additional anti-cheat functionality into Rocket League. This is in progress with the engineering teams, and we’ll share more on this once we’re closer to implementation.

While we have been quiet on the subject during this time, we have been actively investigating these bots since they first appeared late last year. We strive to be active participants when it comes to community conversations about our game, but we are always going to be more deliberate on issues related to game security and competitive integrity, withholding comments until we are ready to take action.

There is a zero tolerance policy when it comes to using bots in online play. This is considered both cheating and matchmaking abuse, and it violates the Rocket League Terms of Use as well as the Code of Conduct. Also, if you are interested in working with Psyonix directly on anything bot-related, you can reach out to us here on Reddit, on Discord, or Twitter. Thanks, everyone.

External link →

For the last several weeks, the introduction of third-party bots to online matches – in Competitive Playlists, especially – has understandably been a very active topic among the Rocket League community.

Earlier today, we took action against a number of accounts running bots in Rocket League. This banwave should cover the vast majority of accounts that have used bots since they first appeared in online matches towards the end of 2022, and we will continue to monitor for bots and take appropriate action against any players/accounts using them. Furthermore, to help us address bots in future matches, we have added a “Cheating” report reason back into the game. You can find this in game on the report reason list in the Report/Block menu.

Finally, we are taking steps to introduce additional anti-cheat functionality into Rocket League. This is in progress with the engineering teams, and we’ll share more on this once we’re closer to implementation.

While we have been quiet on the subject during this time, we have been actively investigating these bots since they first appeared late last year. We strive to be active participants when it comes to community conversations about our game, but we are always going to be more deliberate on issues related to game security and competitive integrity, withholding comments until we are ready to take action.

There is a zero tolerance policy when it comes to using bots in online play. This is considered both cheating and matchmaking abuse, and it violates the Rocket League Terms of Use as well as the Code of Conduct. Also, if you are interested in working with Psyonix directly on anything bot-related, you can reach out to us here on Reddit, on Discord, or Twitter. Thanks, everyone.

External link →

Originally posted by MuskratAtWork

Hey u/Psyonix_Devin, this is obviously one of the biggest questions the community will have:

Will bakkesmod remain functional and usable with the future release of an anticheat?

Will bakkesmod remain functional and usable with the future release of an anticheat?

We're in early stages with AC, so I can't say more beyond what I put in the post.

Finally, we are taking steps to introduce additional anti-cheat functionality into Rocket League. This is in progress with the engineering teams, and we’ll share more on this once we’re closer to implementation.