Jump to content

Matenia

Elite user
  • Posts

    2226
  • Joined

  • Last visited

Posts posted by Matenia

    •  not happening, you can use a batch file
    • will never happen
    • you can just extract them with dev tools
    • just make your PC auto start after shutdown in BIOS or something
    • already exists, somewhere below in the UI there's a timer for how long the bot is running
       
  1. I don't think you understand how detection works. Detection means the client tells the server the bot is injected.
    If you use patterns, grind for hours on end, don't do quests, use non-human behavior etc they can track that statistically. It doesn't mean the bot is detected.

    I've it for years on Warmane and it's been safe except when I got caught. It was only ever detected on an old version, but that was fixed. So if you are using the old cracked WRobot... go figure.

  2. 22 minutes ago, Nilonja123 said:

    So this is definutely also Warmane detected also..Not worth purchssing

    No, you're an idiot. It's not detected on Warmane. Someone wasn't careful about multi botting (over a month ago - a thread you just necro'd).
    There's some servers that have actually good anti-cheat (because the client is modern or custom and supports better anti-cheat, which base 3.3.5a does not) and instantly ban/detect WRobot.

    Warmane is not a server like that. They have decent detection that's hard to avoid. But it's agnostic to what bot you're using and based on stats and behavior. So it's up to you to avoid that and player reports.

  3. Also, if you're looking to check buffs on party members, you need to replace 

     -- UnitDebuff("player",i)
    UnitDebuff("party1",i)


    Otherwise you're dispelling party members if you have a debuff, which won't work.
    Additionally, this will only work for party1 but then try to dispel everyone. So you need to make your spell actually cast only on party1, not every party member

  4. Well, for starters you've misspelled cleanse as clense where you're searching for it.

    You can also just make it

    then
    	return true
    end

    and not scan for any value.

    Additionally, you're setting a "yes" and "no" string. Have you heard of boolean?
    You want to set true or false. Otherwise you need to adjust the editor to look for the string "yes", which makes no sense.

  5. Then the best you can do is read log events and react to your current target when it happens. That should do the trick for now. 
    Don't use the regular blacklist either (wManager.wManagerSetting.AddBlackList - this isn't realiable), it has to be the property directly on the ObjectManager class as seen here.

    I realize log events won't help much with identifying the mob correctly, but hopefully this will do the trick as your bot is still targeting the mob, so that you can blacklist it and then stop the fight manually afterwards.

  6. I think blacklist events exist, but I don't recall if this case is covered by them. There is a blacklist of GUIDs (which in "real" wow are truly random and NOT re-used like on most p-servers) attached directly to the objectmanager iirc. It's either a list or a map that you can manually add those GUIDs to and they will never be considered in the OM, so for WRobot it's as if those mobs don't even exist. I believe I used this in my free AV plugin for blacklisting AV mobs too.

×
×
  • Create New...