Modern Warfare 2 “DEV ERROR 356”: How to fix, possible reasons, and more

sportskeeda.com:

Call of Duty Modern Warfare 2 has had several bugs and issues that have popped up within hours of its release and have soured the new gaming experience for several players in the community. A new bug has surfaced in the game where the player is abruptly ejected from an ongoing match and it can be in any mode.

The title has been out for around more than a day now and there are already multiple hiccups occurring in-game that are preventing fans from playing the game and experiencing flawless multiplayer gameplay.

Let us take a look at the latest bug that Modern Warfare 2 has decided to throw at the players and make the game even more inconsistent.

Activision has had a somewhat successful series of beta phases where they had ample amount of time to identify, address, and fix the bugs and issues that came up during that time. A sincere nod towards the publishers since they did fix most of the issues that made the game feel rough and ragged during the beta weeks.

However, a new multiplayer game is bound to face new challenges as it makes its place in the wild world of other dominant online shooters looking to continue the legacy of the Call of Duty saga.

The current nature of this new bug “DEV ERROR 356” is unknown but has been seen in multiple iterations of the series. Whenever a Dev Error occurs, the problem is found to be rooted in the localized versions of the language packs.

Assumptions can be made that this error also exists within the local files in Modern Warfare 2 and will be fixed rather quickly with a patch from the publishers.

The error pertains to only a certain percentage of players currently, which leads to the assumption that it can be a corrupt local file or two which causes the game to abruptly crash mid-way