JT's Rappelz Bot

huhu,

funktioniert einwandfrei, dafür schon mal ein danke ! :)
aber der bot "scheint" die kamera nicht drehen zu können ? er wechselt zwar die fenster
(rappelz -> JT Bot) aber die position verändert sich net.

hat jemand einen vorschlag, woran das liegen könnte ?

lg
lost ! :)

Quote:

Originally Posted by stickman Cool script ! But i'm clerc and ... I want to my attack skill replace Attack, but it's to long for repeat the skill ... how can i change this ? I kill with my skill and with spirit fragment and not with sword or other weapons. thx

Well, you can try changing the delay between attacks, and changing F1 to either pet attack or attack with pet, while you support using your attack skills. The bot is just a tool to help you setup what you want to be automated, so customize it using the bots features, which, in my opinion, are very flexible at this point :D

i have change the delay 8000 Attack to 1000 or 2000 but ... My cleric has no reaction and wait ... And he make the attack skill and attack ... o_O

Quote:

Originally Posted by stickman i have change the delay 8000 Attack to 1000 or 2000 but ... My cleric has no reaction and wait ... And he make the attack skill and attack ... o_O

Well, there can be many reasons for that... the biggest of which being that you're Chipping the creature, which will automatically cause you to attack unless you turn off this option in Rappelz.

As for the delays, we're talking about two types of delays here. The first is for "Attack", which shouldn't be changed, since this should only be your pet attacking... or, if you don't have a pet, or don't want to use the pet, then your attack skill should go in F1, and the delay should be changed to reflect cooldown. As for the "Attack Skill" delay in the bot, that should be used if you are using "Attack" delay for pet attack, and again, should be delayed according to cooldown.

I hope it makes sense to you now, as this bot should really be used by someone who's at least tried to play the game a little... it's stupid to start botting before you know the different aspects and factors of the game, but the reality is, most people just decide to start playing the game with the bot because they're too lazy to ACTUALLY PLAY THE GAME! lol :rolleyes: (not saying you're one of those people, but it pays to actually learn about the game when setting up such a bot...)

jt could you tell me how you bot gets around the hackshield so you can send it simulated keystrokes and mouse moves. im trying to write my own bot in c++ but hackshield wont allow input from another application. If you only know how to do it in autoit, i also have that program.

Thanks in advance

ps. I have used your bot, and its wonderful. as a programmer i would like to add my own features to it. so instead of asking for your source ill just build my own.

Autoit is not blocked. not even for the mouse movement..the only thing that is blocked are the mouse clicks. to turn around (if i understood it correctly)...you alt-tab to the bot, press and hold the right click button, alt-tab to the game, move the mouse.

rpiolends i dnt think JT should share anything with you.

im not being mean or anything and ill leave it at this post so lets not flame me like im flaming you k.

u as a programer woulld like to add your own features for it and to write """your """own""" (for you) bot....okay lets let JT let you have part of his work thats gone public to u so you can make your own private bot...oh yerrrr

no

I thought that ControlClick() worked but i may be wrong ^_^
On my system ControlSend() works, havnt tested ControlClick()

Erst mal hallo und ein schönnes fetttes DANKE an JT der bot funtzt echt nice wollte mal fragen wie das so aussieht ob man das zb machen kann das man mehr buffs verwenden kann den 4 reichen bei mir nicht aus :). dann ob man das so machen kann das er zb manche mobs nicht angreift das man das rauselektieren kann weil die z.B. zu stark sind das man das selber einstellen kann und so dann das man keine ahnung so eine begrenzungs aria einbaut das er keine ahnung nur auf einen bestimmt feld farmt und darüber hinaus nicht rausgeht oder so. ob sowas geht oder vielleicht noch dem bot beigebracht wird.
Noch mals danke und so ;)

Previously i posted some suggestions, the following is a screenshot of what the gui would look like in MY opinion (if that counts at all hehe).

[Only registered and activated users can see links. Click Here To Register...]

If JT wants, i did that in koda and i'd be happy to give you the source code for it so you impliment your code into that gui...and yes, claim it as your own. I don't care :) I'm just looking to help out to make it even better. Everything is pretty much self explanatory in the gui. As you know, making a working bot is not hard...making a GOOD bot...thats hard...and i believe with timing tweaking such as i propose would make this GOOD bot even better.

Quote:

Originally Posted by Landa JT..JT... ^^ what does that mean ? PixelSearch(9,49,207,49,0x000000,32) can u explain it short...are this the coords of black ? from healthbar0 to healthbar100 ? which windows solution ? and how can i find out coords for different pixel..i try it with mspaint...but it didnt work.. im too stupid.. can u help me please?

ok...

PixelSearch(Xmin,Ymin,Xmax,Ymax,color,# of shades)

$xy = PixelSearch(9,49,207,49,0x000000,32)
$error = @error
$x = $xy[0]
$y = $xy[1]

means it will search the line starting at point (9,49) through point (207,49) for anything that is within 32 shades of the color 0x000000 (pure black). ***IF*** nothing is found in that range of pixels that is within 32 shades of pure black... THEN @error will return the value 1. ***IF*** a pixel is found that is within 32 shades of the color pure black... THEN $xy will return the coordinate values of the FIRST pixel that matches your color value searched. for example:

If your player's HP value was 100% full... There would be no black pixels in the searched pixels... so @error will return the value 1.
If your players HP value was 25% full... The $xy varriable would return with the value of (59,49)... the first black pixel in that string of pixels searched. In order to use this value we have to extract the value we want... the x value. This is done by asking for it:
$xy[0]
This would return the value 59... the x value of the varriable $xy. If you wanted the y value you would simply do $xy[1].
Just as an FYI... this is where the error Line -1 is coming from. I am working on a fix, but I am unable to troubleshoot this since I do nto get the error on any of my computers.

Quote:

Originally Posted by MattMT Previously i posted some suggestions, the following is a screenshot of what the gui would look like in MY opinion (if that counts at all hehe). [Only registered and activated users can see links. Click Here To Register...] If JT wants, i did that in koda and i'd be happy to give you the source code for it so you impliment your code into that gui...and yes, claim it as your own. I don't care :) I'm just looking to help out to make it even better. Everything is pretty much self explanatory in the gui. As you know, making a working bot is not hard...making a GOOD bot...thats hard...and i believe with timing tweaking such as i propose would make this GOOD bot even better.

This is very very nice... I might have to take you up on your offer. I am still working out some bugs and I am trying to finish/finalize the bot-trap detection code... once I am done with that I might explore changing the GUI to make the bot easier to use.

I will send you a pm with the source code of it, and some explanation of how the options would work (at least in my head) hehe

Quote:

Originally Posted by FILOO Code: Target Name: Hungry Kukuri PixelGetColor(( + 0),9) = 0 PixelGetColor(( + 0),10) = 0 PixelGetColor(( + 5),6) = 0 PixelGetColor(( + 5),7) = 0 PixelGetColor(( + 5),8) = 0 PixelGetColor(( + 5),9) = 0 PixelGetColor(( + 5),10) = 0 PixelGetColor(( + 5),11) = 0 PixelGetColor(( + 5),12) = 0 PixelGetColor(( + 5),13) = 0 PixelGetColor(( + 8),9) = 0 PixelGetColor(( + 8),10) = 0 PixelGetColor(( + 8),11) = 0 PixelGetColor(( + 8),12) = 0 PixelGetColor(( + 10),14) = 0 PixelGetColor(( + 12),13) = 0 PixelGetColor(( + 15),9) = 0 PixelGetColor(( + 15),10) = 0 PixelGetColor(( + 15),11) = 0 PixelGetColor(( + 15),12) = 0 PixelGetColor(( + 15),13) = 0 PixelGetColor(( + 19),9) = 0 PixelGetColor(( + 22),10) = 0 PixelGetColor(( + 22),11) = 0 PixelGetColor(( + 22),12) = 0 PixelGetColor(( + 22),13) = 0 PixelGetColor(( + 27),9) = 0 PixelGetColor(( + 27),10) = 0 PixelGetColor(( + 27),11) = 0 PixelGetColor(( + 27),12) = 0 PixelGetColor(( + 27),13) = 0 PixelGetColor(( + 27),14) = 0 PixelGetColor(( + 29),9) = 0 PixelGetColor(( + 29),10) = 0 PixelGetColor(( + 29),11) = 0 PixelGetColor(( + 29),12) = 0 PixelGetColor(( + 29),13) = 0 PixelGetColor(( + 36),10) = 0 PixelGetColor(( + 37),13) = 0 PixelGetColor(( + 38),13) = 0 PixelGetColor(( + 39),11) = 0 PixelGetColor(( + 46),6) = 0 PixelGetColor(( + 46),7) = 0 PixelGetColor(( + 46),8) = 0 PixelGetColor(( + 46),9) = 0 PixelGetColor(( + 46),10) = 0 PixelGetColor(( + 46),11) = 0 PixelGetColor(( + 46),12) = 0 PixelGetColor(( + 46),13) = 0 PixelGetColor(( + 47),10) = 0 PixelGetColor(( + 49),10) = 0 PixelGetColor(( + 55),9) = 0 PixelGetColor(( + 55),10) = 0 PixelGetColor(( + 55),11) = 0 PixelGetColor(( + 55),12) = 0 PixelGetColor(( + 57),14) = 0 PixelGetColor(( + 59),13) = 0 PixelGetColor(( + 62),6) = 0 PixelGetColor(( + 62),7) = 0 PixelGetColor(( + 62),8) = 0 PixelGetColor(( + 62),9) = 0 PixelGetColor(( + 62),10) = 0 PixelGetColor(( + 62),11) = 0 PixelGetColor(( + 62),12) = 0 PixelGetColor(( + 62),13) = 0 PixelGetColor(( + 64),11) = 0 PixelGetColor(( + 70),9) = 0 PixelGetColor(( + 70),10) = 0 PixelGetColor(( + 70),11) = 0 PixelGetColor(( + 70),12) = 0 PixelGetColor(( + 72),14) = 0 PixelGetColor(( + 74),13) = 0 PixelGetColor(( + 77),9) = 0 PixelGetColor(( + 77),10) = 0 PixelGetColor(( + 77),11) = 0 PixelGetColor(( + 77),12) = 0 PixelGetColor(( + 77),13) = 0 PixelGetColor(( + 83),6) = 0 PixelGetColor(( + 83),9) = 0 PixelGetColor(( + 83),10) = 0 PixelGetColor(( + 83),11) = 0 PixelGetColor(( + 83),12) = 0 PixelGetColor(( + 83),13) = 0 End Target

Thanks - will be included in the next version.

Just an FYI -please do not use code-boxes... they remove the varriables from the script. It is not really a big deal, but it does add a few extra steps since i have to add the varriables back into the code.

The varriable $xlet is missing from the above script...

Keep up the great work JT, can't wait to help test the next vers :P

Btw, you get my PM?