The vast majority of patches by blizzard are trivial in nature however may still implement something big -- in a small package. In the recent patch, it was non-trivial in nature (the first 7.2.5 release which most are anxiously awaiting to bot on), and thus requires more time to analyze as there is more potential dangers to check for and if any new ones are found, to patch the bot to help protect you against that specific threat.
It can be broken down something like this :
* Happy botter, automating tasks.
* Blizzard releases a big patch.
* Bot refuses to work with new patch due to "significant" or "moderate" change.
* Buddy team starts looking at what changes have been made to blizzards anti-fun (bot) system.
Internal plan, and ticket to write a patch to target the issue."}">--- If found > Internal plan, and ticket to write a patch to target the issue.
------------- Research
------------- Develop
------------- Test
------------- Deploy
Double check to see if anything was missed, if still nothing -- update internal anti-bot system/version flag check to allow it to hook under the new patch."}">--- If not found > Double check to see if anything was missed, if still nothing -- update internal anti-bot system/version flag check to allow it to hook under the new patch.
* Happy botter, automating tasks.
I hope this helps you and anyone else who is anxious for the release of a patch, but perhaps is missing the potential effort involved when developing new software. I am sure you would prefer they take their time to look over things carefully before just passing it off, versus releasing something which has glaring targets that could have been mitigated with a bit deeper insight.
As for the minor build revisions -- very rarely is anything significant done in such a minor increment.
