Target slugfit

thanks for the spammer, its still didnt show what monster are we facing when attacking on it and your command would jump to the next and it didnt well worked, but well done

Of course it would'nt show slugfit because it was the problem in the first place, it was untargetable by the bots.

Try adding more packets
Maybe it didn't work well for you because you had a class weaker than VHL?
I used those packets for my bot and they were just enough to kill slugfit

it worked well on the first battle and then it jumped onto the next command
so look a like i need a class with a stable damage for slugfit isn't?or a stable weapon? oh thanks that make sense hahaha thank you

You can just add these "Is in combat" commands in the misc tab for each packet, make sure you have enough packets to kill slugfit

credits to @KekkeTex

A class with high damage output with sustain is very much recommended.

To clarify a bit more. You need to send as few invalid packets as possible. This means, don't spam packets when the enemy is dead. And don't spam an ability when the cooldown is longer.

This is the method that I used, works both for a high and low level character:

The first part is to make you wait if you are already in the map. Cause if you're already there, then the bot already fought slugfit, and need to wait for the respawn.
After that it will auto attack once. If it hits, then you are in combat. So if slugfit hasn't respawned, then it will go back to the top, and wait again.

Every next packet you send should come after "is in combat". aa is auto attack. a1, a2, a3, a4 are the skills.

Instead of trying to figure out the delay that is needed for when you can use your skills again. I find it easier to finish the battle with auto attacks if needed. Slugfit doesn't has that much health.

can some1 tell me whats is this about?

Wow Thanks This What I Looking For.

I too figured I can just packet-sniff the attack commands and just send packet to avoid the Slugfit-targetting issue a few days ago. However I'm still not entirely sure what the packet means so I hadn't edited my bots because, you know, safety reasons


As pointed out by the others, "%aa" can be changed into "%a1", "%a2", "%a3" and "%a4", representing an auto attack and skills 1-4.

The "m:<number>" refers to the mob you'd target in the map. Each mob in a room has been given a number in a chronological order of their appearances. You can know this by auto targeting mobs. The mob with the lower number would be targeted first. E.g. First room has 4 mobs, and you want to target the second mob of the second room, its number is probably 6. If you're not sure, just do a packet sniff and get the whole packet instead

My only concern is the "%0". For each attack command, it goes up by 1, up to %30, which then gets reset to %0. Changing rooms would not reset this, so I believe that every attack commands in the same login session will be logged this way. When we make the bot send packets to the server, it will be a set number and it wouldn't be following the previous numbers. I wonder is this something the server would pick up? If it'd indeed get picked up, it could be used against us players in the future. That is, when they finally decide to take action on botters/exploitative behaviors.

The rest seems to be staples, so I guess the above question is the only doubt I have with this workaround. Any ideas? Or am I overthinking this?