What was fixed?
Wait for behead now actually cancels itself after half second if you missed the coordinates.
Useless sleeps while targeting were deleted.
Something for mages was fixed.
If the program detects 0 Hp at start, it warns you about it and tries to fix itself.
I replaced the old link with the new one, but here it is, so you won't scroll so much.

Sorry for the slow targeting bug that I made in the last 10 minutes before releasing the old version. Anyway, I think it's fixed now
First of all Hello!
Second... The post is quite long, and if you don't intent to read it DON'T USE THE BOT.
EDIT: For a limited time YOU DO NOT NEED ANY POSTS ON NOOB.SI, ONLY AN ACCOUNT FOR THE BOT
Also.. do not respond in German (with that I meant I do not care if you talk in German, just do not talk to me, because I do not understand it)!
The bot has been tested and it should work on Windows 2000 or newer OSs. It was written by me to promote Noob.si site with it. The programming language used was C#, which means you will need .NET Framework.
So a bit about the bot: It is a pixel bot, that uses more or less complex checks to detect the monsters and try to play as good as possible and the whole thing then looks like this:

It does not need you to input any color, but it programmatically calculates if the colors is pink.
It was written to offer as much as possible at start, but I'm sure bugs will be found at start, so please be patient.
The thing I like about it the most: If it gets bugged or stops attacking, other stuff, it will always recover in max 10-20 seconds (even less when in combat), so if it fails at the second mob
Also an important thing to know is that you will need to register on Noob.si to get the login that you will be able to use with the bot.
You will also need to post 1 SHORT game review, program review or game guide (hacks, cheats, help... whatever.. a guide) on the site in order to use it. You can do that on your profile page. This was made to prevent useless leeching and wasting of our time. Also, all the posts have to be checked first (might take up to 12 hours, as I am the only one at the moment that have the rights for that) so you won't just come and spam something.
It should work on INT server and private server as well. On Windows XP it has some problems on servers like Pyramids (Probably because of R11), but it works there with Windows Vista and Windows 7 (Tested on both, with 64-bit versions).
Now to some nicer stuff
KalOnline - PixelBot.
If set right, I think it's currently the best public pixel bot. If it won't be working for you it will probably be because you didn't read this very long post.
This is the GUI:
Now to describe some of the stuff.
The Start button obviously starts the bot.
The Settings button opens a full screen settings windows that I will describe later and can only be changed when the bot is not running.
The Quick Settings button has some quick settings that can be changed at any time.
The Show battle log switches the button settings between battle log on the settings.
The Game patch button opens a Folder Browsing Dialog, that will help you patch/depatch the texture folder and full screen/windowed mode.
The button settings allow you to configure the keys that the bot will use.
Skill reuse/cast time are only used for non-repeating skills.
The bot will heal/recharga mana/teleport when the HP/MP gets low enough. He values can be set below button settings.
Now to the settings window. It should look something like this:

Set capture area and Set skill area will make the whole screen go white, and you will be able to drag and select the area you want. Capture area is the operating area of the bot and the skill area is the green area when the bot will use skills if set so.
Now.. Player HP bar stands for the location of the HP and MP bar of the player, you have to set exactly at the right spot or it will not get the right value. (Might get 0 if you set it 1 pixel too left). Those are the red and the blue bar.
Same goes for the Monster HP bar (the green bar). Set it per pixel accurate or it might not work. This one is even more important.
Behead skill box should be set on the white border of the behead skill. It also should be set per pixel accurate, but this one is not important. It cancels after 0.5 second. So I had it somewhere completely different for testing and it also worked.
Window start should be set in the top left border of the window like seen in the picture.
Now for the quick settings, they are quite self explanatory, but I would recommend these settings for fighter classes:
It does pretty good job using skills too.. So if you want you can check that too.
And to use it with a mage, you simple check Use skill instead of normal attacks.
Now to explain about the settings a bit, because some of them have certain problems at the moment.
Wait for behead will check the box that you have used, if the skill is using at the moment, and wait untill its reused, before clicking on another mob. This might get especially useful if you have problems with lag. It should be on, but you will have to do some skill targeting like on this picture.
Split rectangles will split large rectangles into 2 or 4 rectangles, it will look for abnormal height or width of a detected monster in case if it detected one monster instead of two. This doesn't always work, but it is nice to have it on.
Remove close rectangles will remove any close rectangles that aren't big enough and probably don't represent a mob. This is a useful feature if you are fighting fairly big mobs, but you will have to uncheck it when you go on ghosts, masks or some other small mobs.
Behead before picking up is a test feature, and it will only work if only one monster is detected below the yellow line. Then it will first behead the monster and after that pick the items.
Check HP is very important setting! It should be set unchecked unless you have some kind of problems (that I didn't have) with behead lag, it will not check the HP of the monster before attacking it, but it will be much worse at beheading and will tend to wait for the dead monster to disappear before targeting a new one.
I think I have covered most of the things that you should know, I hope I wasn't too long, but feel free to ask me anything if it might not work.
If anything isn't working, try playing around with the settings first, because I tested it almost all week and everything worked more or less.
Before starting the bot be sure to:
- Patch your textures
- Set the game to windowed mode
- READ EVERYTHING ABOVE
- REMEMBER TO UNCHECK REMOVE CLOSE RECTANGLES WHEN BOTTING ON LOW SIZED MOBS
- TURN ON THE OLD UI (The new one was not tested)
- The green line should be somewhere above your characters head (you will see) it is used for plenty of things, so don't miss is!
Since I do not have any high enough level character (with gear) please report how the bot works on masks. I have tried it there, and it worked with problems from time to time.
Now to the downloading and using
Here are the links to download:

or

EDIT 2: I have created a test account that someone can use it to test the bot.
Username: TestAccount Password: TestAccount
As as I said you will need .NET Framework. If you have Windows Vista/Win 7/Win XP SP1+ (Or SP2, not sure) it should work, but otherwise you might need to install it.
It's about 22mb large.
Download link (Microsoft site):

[Currently known bugs: Does a bad job on masks, only detects them if they are close, sometimes have problems if a certain combination of settings is on and multiple mobs attacks, but like I said, it fixes itself]
I guess you will probably not trust me at start since I only have 3 posts, so if you try it, please report about it.
I know I probably missed some stuff in the above post even though it's already very long, so I'll add that stuff later when I check it.
Enjoy!
EDIT:
I've uploaded a preview video, sorry about the frame rate, bad codec. I made it in a hurry... It was working a bit slower than usual, since the recording software used too much CPU.

At 1:00 it clearly shows how it tries to fix itself, because the mob is a no-go. You can also see the approximate position that the green line should have. (It's a bit too high on the video)






