1 2 3 Previous Next 68 Replies Latest reply on Nov 19, 2013 4:09 PM by nicedrewishfela RSS

    FYI Let me explain the patching process.(AKA give devs a break)

      I do not work for Activision however I do have extensive IT experience and the principles are the same as game development. So here is an idea of what it takes to patch an error:


      1. Error is reported on a significant enough level to justify a fix.

      2. Incorrect code must be found/identified.

      3. Code must be studied and possible fixes discussed(considering costs, labor, feasbility)

      4. Decision must be made on best way to implement and benchmarks to determine if it worked.

      5. New code must be written.

      6. New code gets patched/tested locally.

      7. Nothing does what you wanted it to so repeat steps 5 and 6 until it gets close enough.

      8. Patch gets tested by more people on a larger scale.

      9. Review is conducted to determine if patch is ready for distribution.

      10. Decide if it should be launched alone or wait until you can bundle a few, method is scheduled and implemented.

      11. Patch pushes, wait to see what actually works(fingers crossed).

      12. Work on the other 50 patches you have in the works.


      The game mode stuff and others they know about they have probably not stopped working on and are just feeding them out as they finish them. Implementing new patches on a game, console, or computer is a laborious process so don't be too hard on developers. Then you have the hackers that go and f everything up and create security issues, which also have to be patched.

        1 2 3 Previous Next