Jump to content

[Release] L2-Zur bot - Undetectable - Any L2 server/version


L2-Zur

Recommended Posts

Ok, I see now :)

 

Thanks for answering. I'll test it soon. Keep up the good work!!

 

np!

 

also,

 

New version out:

Added an After-Combat ability, that is executed after killing a target. Usefull for spoil/sweep combo for example.

Link to comment
Share on other sites

You could make a guide of good bot leveling zones.

 

I dont know if I´m making something wrong, but when there is no targeteable mob in range, y starts writting ingame 7target "mobname".

It is like if the bot cant send /, and sends 7. Maybe if you change the bot to send the "/" character instead of "Shitf+7" would help.

Link to comment
Share on other sites

You could make a guide of good bot leveling zones.

 

I dont know if I´m making something wrong, but when there is no targeteable mob in range, y starts writting ingame 7target "mobname".

It is like if the bot cant send /, and sends 7. Maybe if you change the bot to send the "/" character instead of "Shitf+7" would help.

 

Read the FAQ, this is covered. The bot doesnt send Shift+7, it sends a direct keystroke to the L2 window handle, but keyboard settings do come info effect.

Link to comment
Share on other sites

A pixel bot?

Good luck trying to run that for 2h+ straight.

 

Actually, it runs for 8+ hours straight if you set it up correctly.

 

But thanks for your useless post anyway.

Link to comment
Share on other sites

No doubt, with a 20sec response delay.

 

And you got this value by running the bot and measuring with precise timer DLLs injected into my exe I take it? Oh right, no you didnt. Thanks for a free bump!

 

Anyway, to get some actual data posted in here: On my PC the pixel detection for checking if a mob is targeted is ~1.28ms with Improved Mode and ~23ms with Compatibility mode.

Link to comment
Share on other sites

No, the error you are receiving has nothing to do with any timers.

 

There is a new version out now that allows you to choose which pixel capture method to use. Use the "Pixel Capture" tab in the configuration to change the modes.

 

Please let me know if everything works using the "Compatibility Mode"

 

I've got the same problem, and when it is displayed, the L2 session closes. I've tried on both capturing modes and it ocures at the same time: When I start the bot :)

 

ERROR: An error occured getting the client window's device context handle.

Link to comment
Share on other sites

I've got the same problem, and when it is displayed, the L2 session closes. I've tried on both capturing modes and it ocures at the same time: When I start the bot :)

 

ERROR: An error occured getting the client window's device context handle.

 

Your L2 client closes when you start the bot?

 

Also, you cant get the device context error using the compatibility mode, since the compatibility mode doesnt use device context. Please let me know what you get when switched to compatibility mode.

Link to comment
Share on other sites

when I switch to compatibility mode I siomply get my L2 session closed.

 

Can it be some kind of server protection?

 

Does it close right away or after running for a few minutes?

 

Do both the bot and L2 close, or just L2?

Link to comment
Share on other sites

the entire process:

1) Start L2 session

2) Log in

3) Start L2 Zur

4) Configure L2 zur

5) Start L2 zur

6) Delay 2-5 sec

7) L2 closes

8) L2 zur continues to run

 

I believe is some kind of server protection

Link to comment
Share on other sites

the entire process:

1) Start L2 session

2) Log in

3) Start L2 Zur

4) Configure L2 zur

5) Start L2 zur

6) Delay 2-5 sec

7) L2 closes

8) L2 zur continues to run

 

I believe is some kind of server protection

 

Yeah, that sounds like protection indeed. What server are you playing on?

 

I know the bot works with GameGuard, Kasha, Frost, WS protections.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.



×
×
  • Create New...