Creating a Pixel Bot in C# from zero - "kinda" tutorial

[FearThree]

Use binds? Target Last Enemy -> Interract with Target (need to have ctm on) ez

But how would you navigate to that target asuming you're a ranged class?

Edit: Just realized you mentioned click to move.

[hjalplos]

ye you don't really need to click to move, Interract with CTM On does it for you

[FearThree]

ye you don't really need to click to move, Interract with CTM On does it for you

thanks man

[FearThree]

I too experience wierd Colors of my standalone LUA addon pixel boxes. Depends on where I am in the world. In Durotar close to Razorhill I can make my X-cord box become a strange color by just moving slightly. If i print out the values they don't change. Just the color of the box for no reason. Blizz have some anti pixel code ? or there are some bugs on their side?

I too am having this exact issue. Did you find a solution?

[hjalplos]

No not yet. I was gonna try what stonebent suggested. But I don't have a texture file with all different colors. I can probably make one with a python script. Will try it when I have the time.

Edit: Edited an image 255x255 with this simple python script:
for x in range(0,255):
for y in range(0,255):
img[x,y][2]=x
img[x,y][0]=y
img[x,y][1]=0
So red is x and blue is y. I guess I should stick to 2 colors per texture then atleast we have 255x255 values. Enough for cords I think. I never worked with textures and lua addons so will see how I implement it.

[FearThree]

No not yet. I was gonna try what stonebent suggested. But I don't have a texture file with all different colors. I can probably make one with a python script. Will try it when I have the time.

Edit: Edited an image 255x255 with this simple python script:
for x in range(0,255):
for y in range(0,255):
img[x,y][2]=x
img[x,y][0]=y
img[x,y][1]=0
So red is x and blue is y. I guess I should stick to 2 colors per texture then atleast we have 255x255 values. Enough for cords I think. I never worked with textures and lua addons so will see how I implement it.

Sent you a PM. Seems like we're both working in python and having the same issue.

[hjalplos]

Im stupid WoW only works with textures with the dimensions of power of 2. Working code for creating a texture alltough PNG:
for x in range(0,255):
for y in range(0,255):
img[x,y][2]=x
img[x,y][0]=y
img[x,y][1]=0
matplotlib.image.imsave('my_texture.png', img)

Then convert it to TGA with an online converter or your favorite software. Then you can use it in your addon.

[stonebent]

You can also use a 512x512 blp

[stonebent]

You can also use a 512x512 blp

@hjalplos you're swedish right? I figured by your name

[hjalplos]

ye indeed i am

[FearThree]

No not yet. I was gonna try what stonebent suggested. But I don't have a texture file with all different colors. I can probably make one with a python script. Will try it when I have the time.

Edit: Edited an image 255x255 with this simple python script:
for x in range(0,255):
for y in range(0,255):
img[x,y][2]=x
img[x,y][0]=y
img[x,y][1]=0
So red is x and blue is y. I guess I should stick to 2 colors per texture then atleast we have 255x255 values. Enough for cords I think. I never worked with textures and lua addons so will see how I implement it.

I've looked a bit further into the issue. It's not an issue with colors not reading correctly for me. It's how the angle is calculated that is offset for some reason to the direction the char is facing.

Here is the offsets and the code that calculates it.
Imgur: The magic of the Internet

The code seems alright to me. I am converting the direction from 0-255 values into values from 0 to 2.

Do you see any issues with this?

[hjalplos]

your direction, it's your characters facing correct? You need to calculate a new "bearing" then calculate the difference and turn which ever way is the shortest.
I split it up in 4 different cases so it's not as simple as a few lines of code. Or maybe I overworked it and made it harder than it is.
And IDK something looks wrong in your atan2 I think you need to swap the x's or y's to be correct. I also go over from rads to degrees. But that's optional.

I hope this will get you on the right path.

[FearThree]

your direction, it's your characters facing correct? You need to calculate a new "bearing" then calculate the difference and turn which ever way is the shortest.
I split it up in 4 different cases so it's not as simple as a few lines of code. Or maybe I overworked it and made it harder than it is.
And IDK something looks wrong in your atan2 I think you need to swap the x's or y's to be correct. I also go over from rads to degrees. But that's optional.

I hope this will get you on the right path.

1. The direction the char is facing is correct, but the difference between the direction suggested by def get_angle() is different. The turning seems to work fine, but the direction doesn't match.
2. I tried swapping the x and y's but still the same issue.

EDIT: Fixed it. Turns out I was retared and the x and y was swapped.

[spik96]

Isn't this method of keyboard and mouse going to be detected by the Warden within minutes?
You are not doing a true driver so it can detects that a program, not a human, did the actions.

[someorother]

Any tips for running multiple pixel bots? VMWare just doesnt seem to run wow well enough.