Openkore.com

Private server anti-bot checks are usually better. There are too many variations, but as long as you know the conditions, and with the tools that we have, they CAN be bypassed. Your ideas, being a bit more complicated, can be done using eval commands. It is sweet that it actually encourages smart bo...

It's not impossible that an NPC conversation like this would pop up: Unknown#12345: [Tool Dealer] Unknown#12345: Do you want to stay? .. which is the reverse of responding "Yes" Thing is, you can't really have a single config that can catch everything. The bot should be monitored and reshaped as reg...

First off, please update to latest Openkore on gitHub. There has been a fix committed regarding NPC talk, and our workaround regarding Sir Windsor may not be needed anymore, since openkore is set to automatically send a talk close packet. Please test it without the reactOnNPC block and see if what w...

Remove useSelf_item.

Enable storageAuto and properly set the other storageAuto_ options

Set saveMap to the correct map and enable saveMap_warpToBuyOrSell and teleportAuto_useItemForRespawn

Make sure also that items_control.txt is properly configured.

Is there some post-delay status after using Venom Splasher? Like "Venom Splasher Delay" or something? Type "s" to check immediately after using the skill. My idea is that you can use that status on a doCommand block to trigger an "a stop" command so openkore will have a chance to switch target if th...

If you use only the "msg_0 [Sir Windsor]" and remove "msg_1" and "msg_2", it would work on all conversations that begins with "[Sir Windsor]". So a single block can be used. Adding msg_1 and msg_2 conditions would make it more specific in case there are other "[Sir Windsor]" conversations that you d...

Ok, I was assuming that only the last conversation per room matters. Then you need 7 blocks.

Can you already configure the 7 reactOnNPC blocks based on the examples?

With this log, the reactOnNPC block is triggering as intended. The conditions are now correct. However, I'm sure you noticed the RO client is sending a packet dissimilar to the packet being sent when you use the "talk no" command. Use this instead for all three reactOnNPC blocks: reactOnNPC eval $me...

Ok, first off, I noticed the code I gave you is wrong, it's missing a line. Try this one: reactOnNPC talk no { type close msg_0 [Sir Windsor] msg_1 /.*/ msg_2 the next level. inMap job_knt } reactOnNPC talk no { type close msg_0 [Sir Windsor] msg_1 ...One stage left. inMap job_knt } reactOnNPC talk ...

reactOnNPC plugin
http://forums.openkore.com/viewtopic.ph ... &start=380