why blizz makes these mini-patches???

[Rettob]

Actually there was a big long discussion in the wow forums with other game developers, discussing anti-bots using small obtuse changes in the DLL files.
Apparently Blizzard listened and has been very vigilant in releasing patches every 3-4 days.

The best way to counter the bot counter is to simply DONT LOG OUT. just put yourself idle with an anti-logout.
Once you log out. the game patches.
As long as your are in the game and dont shut it down. You can continue using the current patch.

I know. I was botting until I had to go to work this morning, when i got home my kid had rebooted my computer to play counterstrike in windows.
Little shit!

Thumbs up!!! I try and do that as well .

 

[shaggsdope]

I' actually surprised they don't do more patches. Most software companies are moving to a more agile style, micro-release standard. So, just be thankful that's not completely happening.... yet

 

[Tarathiel2]

I work as a software engineer for a company that offers a SaaS solution. If we had such a long downtime, we could close.
Vacation is no excuse.

It's easy if you have access to all the source code. Does your job involve carefully scanning and reverse engineering another company's huge, overbloated, 10+ years old patchwork code for hidden booby traps? Yeah, didn't think so.

 

[klepp0906]

So can someone tell me pls why Blizzard is coming out with these fucking mini-patches, and if they will keep making new patches every week???

to fix things

 

[klepp0906]

Does your job involve carefully scanning and reverse engineering another company's huge, overbloated, 10+ years old patchwork code for hidden booby traps? Yeah, didn't think so.

the reverse engineering part is long done and over with. and they dont have to review code they already reviewed.. they have to review the new code which was a micro patch at best. One which is extremely extremely unlikely to have any new detection since the detection they have is already sufficient.

the much more likely scenario is they have 1 dev due to the mass bannings and closure of arena and greed and said dev is on vacation. He lost his pina colada time once, at that point he probably turned off his phone

sometime before tuesday we should see a drop, but tuesday they'll likely patch again since the world is still rife with issues. Get used to no HB for awhile.

 

[shaggsdope]

the reverse engineering part is long done and over with. and they dont have to review code they already reviewed.. they have to review the new code which was a micro patch at best. One which is extremely extremely unlikely to have any new detection since the detection they have is already sufficient.

the much more likely scenario is they have 1 dev due to the mass bannings and closure of arena and greed and said dev is on vacation. He lost his pina colada time once, at that point he probably turned off his phone

sometime before tuesday we should see a drop, but tuesday they'll likely patch again since the world is still rife with issues. Get used to no HB for awhile.

I wouldn't go so far to say the reverse engineering part is over. They have to closely inspect any changed elements, and if kne of them is the main dll or exe which I'm sure it always is, they have to rework everything that touches it and do whatever they do to make sure there's no new counter measures. I would agree that MOST of the reverse engineering is done, but all of it DEFINITELY isn't. Unless they were to never bother checking for new counter measures.

On the note about expecting more patches because the world is rife with issues. I agree with that 100% because I've never had this many connection and stability issues EVER playing wow. I don't know if they're getting lazt, changing the way they're doing things, worse devs or their counter measures are causing issues. Something definitely is, so I'll be expecting a couple patches a week for probably the next month or so, if they're even able to find all their issues.

 

[DarkmincerLSO]

Actually I am surprised that the people here aren't using a DIFF program reviewing files and keeping two. One off line as a previous, and new patch, to instantly find the changes and adjust it at the machine level code.