Friday, May 30, 2008

Found a buddy

Found this blogger, BugHunter
He is similar to me in a lot of areas, i.e. both are engineers, both likes games and both has wife argo...

Well at least I am not alone.

Tuesday, May 27, 2008

Hope in sight

Just read a very interesting piece in http://www.newyorker.com/reporting/2008/06/02/080602fa_fact_wright

Does it mean a new start for Egypt? I don't know. It almost sounds like the protestant reform of the Christians. The protestants freed them selfs from the corrupted church, which used God as their weapon to gather money and power, while Dr. Fadl's refute of the violent ways could free the radical Muslims from the wraith of some of their leaders who uses God as their justification to inflict pain on people and gather power at the same time.

I don't know. With the democracy in Western countries getting old and corrupted (well, the population started to vote stuff for them selfs and demand government taken care of everything for them), the hope lies in the new ones :-)

Saturday, May 24, 2008

Loot problem not so small.

Well, I did notice a strange repeat loot problem recently, but never really cared, as long as it loot most of the time and works, don't want spend time on that.

Recently more and more people start to complain on that. Maybe some glider users who paid $25 and got banned switched? I did a investigation, and found the loot problem might be the cause of the strange program abort on generic error.

What happened is at some version I introduced javascript call backs during wait, but it was not handled in script.js, so everytime there is a loot, during the wait, the call back will occure and cause the find corpse to loot function in script.js to fire, in turn it will find a corpse right in front of it and start loot again, which will again trigger the call back and loot. On slower computers it will show up as multiple loots, on faster ones it will likely cause javascript stack overflow problem.

Thursday, May 22, 2008

No, we are not affected by the ban wave

And please stop send me emails asking me, read the forum or my blog first :-) Even thought zoloFighter development is pretty much a one man army and I don't have money to hire developers/auditors, we are still undetectable and safe, make sure you follow the rules.

And on a side note, here is what the politicians doing to the high gas prices. Shouting murder and increasing tax at the same time:
http://cbs2chicago.com/politics/gas.prices.taxes.2.729939.html

Wednesday, May 21, 2008

New Ban Wave

I learned about the ban wave yesterday, minifss posted on my thread on mmowned and I was surprised that there is a ban wave. I thought Blizzard has give up on bot detections and focused on law suits a long time ago.

Anyway, another user suggested I should blog on the matter to give some comfort on zoloFighter users.

Yes we are safe, as long as you follow the rules, list on the security notice on fighter support forum (thanks the moderator who put it up as announcement). We don't inject, we don't hack WOW by change its memories. We don't do background mode either, which leaves small holes that could be traced. The security is generic (so it persists across patches), and nothing fancy (standard windows security model, which is tested by hackers across the world and patched by Microsoft).

If everyone follows our model, there is nothing Blizzard could do except resort to player reports. I am a little bit surprised that the bots which uses background mode (openbot, glider elite) could last this long. I think Blizzard might been focusing on lawsuits instead of bot detection.

Anyway, that said. It is safe to using zoloFighter during the ban wave, as GMs will rely on software detection to ban players. I was botting non stop during the last few days, trying to reproduce a bug in newer version of fighter that randomly stops on some players machines. (which was stupid of me).

But the period after a ban wave is not safe. As the masses of bots clear out of WOW, GM will have time to deal with player reports because there will be few. So watch out.

Tuesday, May 20, 2008

GenErr bug continues

Over the weekend I reproduced the bug once, which pointed to a corrupted javascript stack. The only possibilities are either javascript engine got a bug (which is highly unlikely) or some unhanded exceptions in native code by pass the stack clean up code in javascript engine.

The bad news is, after plug all the holes in my native code, John still finds the newest release doing the same thing.

That is just bad.

On a side note, CA Supreme-court ruled gay marriage ban is unconstitutional. Gay marriage is legal or not is really not our business and most of us could care less. However the power of the court is rather obvious in this case. Any thing or any law can be marked unconstitutional and out ruled by court, I could foresee one day US will be ruled by court instead of President. Is it a good thing or bad thing? The good thing is a rule of law might be better than mob rule, but if the person who is interpret the law is corrupt, then the rule of law became tyrant rule, especially in established democracies, where the elected leaders are becoming increasingly incompetent.

Friday, May 16, 2008

Strange bug

Recently players reported a bug that stops the bot at random. The bot catches a generic error and stops. I was not able to reproduce it till yesterday. And for now all my code inspections has not produced a good result.

A generic error can be anything, divided by 0, access out of bounds etc. If it is c# this one will be easy, as the stack traces are readily available. But this is good old C++ we are talking about.

So we will see how fast I can track this one down.