Blue Eye Macro

Do con is pretty boring cause you need to punch "infinite" times to get .1 at high con but it's kind of a must in game, cause it will gives you more hp and bagweight everytime you level up, making big difference in later lvs.

I tried it a few ways with "color. find RGB", "mouse.click RGB" and those relative to then like "...at first appeareance..." but didin' managed to create one :S

Which comands should i use to make something like this:
1 - I wanted my guy to "patrol" a determinated area (don't want him to go away while hitting mobs and end up in a hard mob and die)
2 - How can the macro find the closest mob on screen and know when he died? My failed attempt made me click,randomly, every mob on the screen and i ended up dying cause i was taking too much dmg (i tried that "at first occurance" didn't work :S)

So basically is this, he will hit the closest mob, until the mob die, then he click the next closest one and keep on but in a determinated area.

Thats a pretty advanced macro, but definitely doable, I will try to help you out listing the things to do, but I'm only on from my phone right now, but I will think about it and guide you in the right direction...

No matter what though it will be a pretty hard one to do...

uhm... a really noob question lol, hex is more accurate than coordinates? Does that work for pixel and colors aswell?

Sorry about the late answer, HEX is just a different representation of a specific color, just like RGB, if you try open the investigator, grab a screendump and click a pixel in it, you will see both the R, G and B value of the color, as well as the HEX representation.

The HEX colors is only used when doing object recognition (similar to pixel patterns and image recognition), the reason for this is simply that if I used RGB I would also need 3 times as many argument boxes, since what takes 3 values in R,G and B can be expressed as just 1 Hex value.

For more info on object recognition please check out: http://www.blueeye-macro.com/viewtopic.php?f=162&t=305

First of all, you need to know where you are in the game, so I suggest you use Cheat Engine to locate the base pointer for the X and Y coordinates in the game, and then you can use that to figure out where to go along that path.

Next you need to locate a distinct color of the mobs around you, that you want to target, Id suggest locating the monster closest to you with the following command:
Color.Find coordinate of occurrence on screen near coordinate (RGB)

You can specify the maximum allowed distance between you and the monster, and if multiple monsters are found, it will always return the location closest to the coordinates specified by you (which would be the location of your character, I'm guessing roughly 400, 300 as your usually in the middle of the screen)

Actually you are also able to detect whether or not your currently targeting a monster, by reading from memory what the current mouse cursor is, (if it changed to a dagger), you can find this memory address by using the "has changed" searches in Cheat Engine.

Last thing you have to do is click the monster, and wait for the cursor to change back to a hand or a spinning dagger, which means the monster is dead.

Then you should probably always click the ground below the monster you just killed, to get any drops that might be there.

So, like I said, its a pretty advanced bot to do, but if you do go ahead and give it a go, ill assist you the best I can.

Good luck

Uhm, and that image capture? There is an option on macro "mouse. find image..." would that work if i take a screenshot of the mob and tell macro to click on it?

you can try it with this:

where X and Y is your char location, you can get that easily by:

you have to change the values a bit, but youll get the start

btw finding image for me is the last solution, id reccomend you to use pixel pattern.

There is one problem with pixel patterns though, or actually its not a problem, its the way its meant to be, anyway: A pixel pattern is a series of pixel placed at specific locations with the exact colors specified in the pattern.

For instance its awesome for finding a red pixel that has to be placed next to a black pixel, which has to be exactly 4 pixels below a yellow one (replace red, black and yellow with actual RGB values ofcause)

This means that the pixel pattern will only be a match if the colors your analysing is exactly the same as at the time the screendump was taken using the investigator.

Im guessing it wont be, since the monster your trying to track might be heading in the wrong direction, or there may be a little less light etc.

In fact I think you might have a chance with the image recognition, and setting the accuracy to like 20% and make sure the image only includes a small part of the monster, like the top of its head, something that will look fairly similar in all directions, and includes some colors that will always be present.

However, the very best solution just might end up being the object search, since object search wich is similar to pixel patterns, but do not require all pixels to be found, nor do the pixels have to be arranged in the exact same way, as long as all or some of the colors specified is found within the specified range of each other.

You can read more on Object searches here: http://www.blueeye-macro.com/viewtopic.php?f=162&t=304

And in this case the "object" is the monster.

Note: Object searches works the best right now if you specify all colors, actually I have done some improvements to the speed and accuracy of object searches in the current developer build, so you will see some improvements there with the next upcoming version of BE

Object searches are meant for this kind of job, where you need to locate something that wont be exactly the same as it was when you created the screendump, but contain some of the similar colors, when using it though, make sure to select some distinct colors, this might be a read stripe in the monsters hair, or a yellow gold pad on its shoulder or something similar.

Once you find the monster, I suggest you target it my moving your mouse above the area it should be, and then read from memory if the cursor actually changed to a dagger.