Jump to content

eeny

Elite user
  • Posts

    987
  • Joined

  • Last visited

Posts posted by eeny

  1. In settings / advanced setting there should be latency""... believe its 300-700 default?  Reduce hat number down to around your game latency wand watch the bot for a bit.  You may see it start to skip looting / skinning in which case bump it back up.. try find a good spot.

     

     Quester.Bot > Pulse(): System.NullReferenceException: Object reference not set to an instance of an object.
       at Quester.Bot.Bot.Pulse(Boolean loadSettingsProfile, String profile)

    You are loading the profile under the wrong type. AKA- you are trying to load a grind / farming profile in quester mode.  check what mode the file should be loaded under and start it with that mode.

  2. 3 hours ago, NiteKat said:

    Thank you, this sort of solved my problem. I had tried it before, but only to 8. Now if I set it to 28, the Hunter will stop at a decent distance... but if won't shot. Just stands there waiting for the mob. If I try using Auto Shoot as a spell, it *keeps* casting it, interrupting the attack, so a shot never gets off. I'm assuming I need to check if it's being used already, but I'm not sure what Auto Shoot is considered as (I'm guessing it isn't a buff?).

    thats because the FC is trying to use a skill outside of the range... put the Me.target.distance setting to = your rage (in yds) and it should stop shuddering and just go to ur FC range and start attacking.

     

    you may set a range in your FC... however the way wrobot works is if u have a target outside range.. it will start tying spells.  Sometimes its good like hunters mark / pet attack, sometimes bad like what you are seeing.  All part of optimising a FC.

     

     

  3. IIRC Droidz put in an option where is a FC has <25 yd range it will trigger auto attack and if its > 25 yds it wont trigger it.

    You would need to write the FC in C# and put a range clause in it.. If you are still keen take a look at my vanilla Hunter FC and look at the range function and change the options to be Mana driven so if you have  <10% mana the range is 5 yds so the bot auto attacks.

     

    Ideally... gear / set the bot up so it wont go OOM or set up wanding for low mana situations.

  4. As someone who has taken " a few"  trips to the white room on LB / ND---once you get ported there you are done...The GM has usually made their choice by then.  

     

    Not recently, but on more than one occasion I have had GM's drag mobs onto my bots - who fired off an alert.  I pause the bot window to fight a bit, only to get get ported to the white room, have a 10 minute conversation with the GM and still the acct got banned. 

    IF you are AFK botting, an automated "wtf mate" is not going to get the GM to send you on your way.

  5. Try this.  had to translate some stuff and may have got it wrong- just make sure that the cat mangle part is spelled the same as the client and it needs all the brackets.

     

    also changed Cat form + prowl behavior to only fire duing combat so u can farm without form thrash (hopefully)

     

            if (ObjectManager.Me.HaveBuff("Cat Form") && ObjectManager.Me.ComboPoint < 4)
            {
                SpellManager.CastSpellByNameLUA("Mutiler (Chat)()");
                
            } 

    BC_Druid_Feral_Français.cs

  6. 29 minutes ago, Stranger said:

    Eeny thank you alot! You are my saviour. The bot fnally casts Curse of Agony once and recasts them when they run off.. 

    I had no idea that clients saw certain things differently.

    Is there any guide or page i can read to learn these differences? Atm ive tried to read what i could find and i also downloaded fightclasses of other expansions and opened these up in the fightclass editor to see how they did certain things. The 'Buff casted by me" came from a WotLK fightclass i opened to learn about fightclasses.

    Good to hear man.

     

    No real guide or page on what works where- just take into consideration that fight class editor was written for WoD/ Legion and back ported to BC and Vanilla.  A lot of the more complex code / LUA it ran on doesnt exist in Earlier WoW.  For an XML fight class, start it simple and just add  more and more conditions.  Simple usually being better.

  7. Secondly- the file has empty quests in it. 

    When the bot loads a quester It checks all the quest's, this file has two empty "<none>" quests which are causing the namespace issue.  remove them and it loads fine.

    Empty_quests.PNG

×
×
  • Create New...