MzBot

1. When it all started
Oct/Nov 2006, when my final year examination is over ( In which I slacked and scored only 73% ), I am really have an amount of time for me to spend on hacking.
One of my friend, tsj4j ( Spencer Thang, from RI ), came and ask me for a simple Autoclicker for use in Trickster Online, which also use the nProtect GameGuard. So I just use the same simple method of bypassing the usermode hook, and inject into the game process.
However, he later reported back to me that it doesn’t work!
I instructed him to briefly debug the Autoclicker, it ended up that the loophole of allowing the game process to bypass the SSDT hook is patched.
That inspired me to screw their hook.

2. November holiday, when I am bored
I went back to Taiwan on Mid November…
That was when I thought of the SSDT relocation, which is documented in both my blog ( See the MSBot case ) and in Dual’s blog.

3. Ideas put in action
At the end of the November, I wrote the driver and tested it out. ( The command line debugging utility for MzBot.sys, TiMBuS seen it before. )
The GUI is done on the 1st of December.
That night, my mom went to hospital to look after my grandpa ( who died just recently.. T_T ), so I can sleep anytime I want…
Around the midnight, I thought I want to leave something for the iNCA people, just in case it leaked out, so I wrote and embedded a letter to iNCA in MzBot. ( You all should try to get it out? )
I don’t really treat MzBot as an important project, neither would it be public, that’s why I didn’t really give it a proper protection, I only packed it with ASPR, and added a small anti-unpack ( Still can’t fool SunBeam.. )

4. Sigh…
Around the end of Feb 2007, many people in MSS requested me for MzBot, so I made a version that expires on 15 Feb, and gave it out, by sending it to them individually.
Then, somebody gave it to BrandonMS ( Thanks to SunBeam for notifying me. ), that’s how it all got leaked…

Appedix 1: Regarding the Autopotting:
The autopotting is working on my computer, so I don’t see why it isn’t working on yours…
There’s a way to make MzBot bypass MSBot or MSPro, but it is private. I only told 1 person about it, so if you are the person, you should know better than to leak.

Sigh… I wish I can #undef LEAKERS and LEECHERs…

This have been the major problem for almost all MapleStory cheating community — Leakers, Leechers, and spammers.

There was 3 recent case that discouraged me in great extent:
1. The Rajinn and ZTrainer case:
ZTrainer is one of the internal DA project, just a trainer with most of the usual functions like auto-CC, auto-pot and stuffs, it was made around Aug 2006.
Later, Rajinn was expelled out of the Dark Alliance, the reason being mainly pissing dL off.
However, he already have the ZTrainer source code the time he is expelled. Later, I went to tell him why he is expelled. He is so angry that he asked me to suck his d*ck… ( I ain’t g@y… )
Then, he just renamed ZTrainer into JinnTrainer, without any credit given. Furthermore, he claimed that ZTrainer just sucks…
Halfway through his renaming, he still have the face to come and ask me how to move a label in my ZTrainer… -_-”
2. The Linosal and DA website case:
The Dark Alliance was set up on the new year of 2006, or perhaps before that, by Kenshim and Zaros.
I joined in around April, when I made ZE, the first UCE in the MapleStory hacking history.
Around August, both Kenshim and Zaros went inactive, and I was elected the new leader. I then decided to fork out the DA from the CE Forum. Linosal volunteered to host the new forum.
Everything is fine till this Feb, when all of a sudden, all public can visit the Dark Alliance forum. At first, I thought the DA site is hacked, however, later Linosal say that he “liberated” the forum!
Just to earn a few dollars from the google ads he put up on the site after he “liberate” it, he betrayed all of us…
3. The MzBot issue:
Will be posted in the next blog entry.

Debian Etch, nVidia x86_64 and Beryl Window Manager.

It was recently that I attempted to install x86_64 nVidia video card driver on my Debian Sarge box, equiped with Sempron 2800+ and onboard nVidia GeForce 6150. Somehow, the driver installer just crash with Segmentation Fault ( Oh… well, it is equivalent to the memory access exception/violation on Windows ). I tried whatever I can, it just doesn’t work. I was very sad, so I boot back with my x86 kernel on Sarge. Then I forget about it…

Debian Linux have a long developement cycle, Sarge is already one and a half year old. More recently, the going-to-release Debian Etch caught my attention. It looks very promising, now the x86_64 ( aka amd64 ) architecture is officially supported. Also, x.org is now the official X Server, implying that XGL/AIGLX/Composite rendering is supported, and we can use the Compiz/Beryl Window Manager.

At first when I tried out the Debian Etch RC1 amd64 version, I met an error, but it was quickly solved by throwing my questions onto the debian-boot mailing list, refer to my post here: http://lists.debian.org/debian-boot/2007/02/msg00167.html

Most of my old problems with Debian Sarge is automatically solved by installing the new Debian Etch, especially the nVidia driver problem. The GeForce 6150 just works great with Debian Etch! Also, the problem with Chinese Input method is also solved.

I also installed the Beryl Window Manager, the GUI’s absolutely sweet ( ha… eye candy! )
Here’s a few screenshots:

The normal desktop.

Displaying the virtual desktops as a cube

Ring alt-tab

Feature similar to Mac OS X’s Expose

That’s what happens when you drag a window?

You can find out more about Beryl Window Manager at its homepage: http://www.beryl-project.org/
Or, you can search for Beryl on YouTube.