They are combined. You'll see what i mean when you start up Honorbuddy. Look page 17/18 in this thread if your in doubt.
Used Bowman Marksman on Spine in LFR just now. He stops attacking when Burning Tendon gets up. Seems to be trying to silence shot the cast? This was with RaidBot. I could not upload the log file because it was bigger then 1 mb. If you want it I can try and upload it somewhere else?
On the ultraxion encounter, in LFR atleast, as survival, it presses the Heroic will button constantly
yeah trying to sort the issues. You can simply avoid this by clicking ( Solo/party). Sent several hours at this yesterday and im continuing today. EDIT: Problem has been solved, adding more DS logics in a few!
UPDATE v3.6 - Fading Light, DSNOR/DSHC added. It will now use the action button when you have this debuff - Hour of Twilight, DSNOR/DSHC/DSLFR, fixed. It will now properly use the action button at 800MS left of his cast) - Shrapnel DSNOR/DSHC/DSLFR added. It will now use the action button when theres 2 sec left of the tentacles cast. - A few other minor updates /Shaddar.
shaddar i'm doing 18K dps with 380 ilv is this aint kind of low got all enchant and reforged to arcane shot rotation does it need to be more or is this just it ? this is in party solo and on dummies
Alright, I don't feel like editing this thing all over just to make it better for myself so I'm gonna tell you everything you can do to improve this CC I'm just gonna start going through the code and start writing, so no particular order really. 1. When you call a pet you want to check if it's null, not if it's dead. If the pet is dead you'll still try to call it. Code: !Me.GotAlivePet into Me.Pet == null Also here's my code for calling a pet of your choice Code: public bool CallPet () { if (Me.Pet == null) { if (MarksmanSettings.Instance.PET == 1 && SpellManager.HasSpell("Call Pet 1")) CastSpell("Call Pet 1"); StyxWoW.SleepForLagDuration(); if (MarksmanSettings.Instance.PET == 2 && SpellManager.HasSpell("Call Pet 2")) CastSpell("Call Pet 2"); StyxWoW.SleepForLagDuration(); if (MarksmanSettings.Instance.PET == 3 && SpellManager.HasSpell("Call Pet 3")) CastSpell("Call Pet 3"); StyxWoW.SleepForLagDuration(); if (MarksmanSettings.Instance.PET == 4 && SpellManager.HasSpell("Call Pet 4")) CastSpell("Call Pet 4"); StyxWoW.SleepForLagDuration(); if (MarksmanSettings.Instance.PET == 5 && SpellManager.HasSpell("Call Pet 5")) CastSpell("Call Pet 5"); StyxWoW.SleepForLagDuration(); return true; } return false; } Code: { if (MarksmanSettings.Instance.Revive && Me.Pet == null) if (CallPet() == true) Logging.Write(Color.Cyan, ">> Calling Pet " + MarksmanSettings.Instance.PET + " <<"); } The sleep for lag duration is from your new code and hasn't been tested there but I trust that it works. 2. If you want the bot to stop attacking when you're trying to use the trap launcher or are in feign death, add this: Code: !Me.Auras.ContainsKey("Trap Launcher") && !Me.ActiveAuras.ContainsKey("Feign Death") pretty much everywhere. (Everywhere (including AutoAttack) except for the traplauncher itself) The !Me.ActiveAuras.ContainsKey("Feign Death") hasn't been tested, since I changed it into that from "PlayerHasBuff" as you removed it. 3. My IsTargetBoss code, with additional IsTargetEasyBoss code, EasyBoss is so it'll use trinkets etc. more often. Code: private bool IsTargetBoss() { using (new FrameLock()) if (Me.IsInRaid) { if (Me.CurrentTarget.CreatureRank == WoWUnitClassificationType.WorldBoss || (Me.CurrentTarget.Level >= 87 && Me.CurrentTarget.Elite) || (Me.CurrentTarget.Level >= 88)) return true; else return false; } else { if (UnitClassification == "worldboss" || (Me.CurrentTarget.Level >= 86 && Me.CurrentTarget.Elite) || (Me.CurrentTarget.Level >= 87)) return true; else return false; } } private bool IsTargetEasyBoss() { using (new FrameLock()) if (Me.IsInRaid) { if (Me.CurrentTarget.CreatureRank == WoWUnitClassificationType.WorldBoss || (Me.CurrentTarget.Level >= 86 && Me.CurrentTarget.Elite) || (Me.CurrentTarget.Level >= 87)) return true; else return false; } else { if (UnitClassification == "worldboss" || (Me.CurrentTarget.Level >= 85 && Me.CurrentTarget.Elite) || (Me.CurrentTarget.Level >= 86)) return true; else return false; } } 4. I haven't tested this, but I think it might be a good idea for CastSpell condition Code: SpellManager.GlobalCooldownLeft.TotalMilliseconds < 150 It could reduce "spam" but still cast the next spell asap. 5. This should fix the mend pet spam: Code: !Me.Pet.ActiveAuras.ContainsKey("Mend Pet") Untested though. 6. Add these conditions to readiness: Code: && ((Me.ActiveAuras.ContainsKey("Rapid Fire") && SpellManager.Spells["Rapid Fire"].CooldownTimeLeft.TotalSeconds > 10) || SpellManager.Spells["Rapid Fire"].CooldownTimeLeft.TotalSeconds > 120) It'll make sure that readiness it cast even if Rapid Fire has already ended but there's still over 2 minutes left in the cooldown, but also that readiness isn't cast if Rapid Fire is available but still active. (Happens at End Times dungeon, due to the hour glass) It should work... 7. These conditions will make trinkets, with cooldowns, stop spamming: Code: && StyxWoW.Me.Inventory.Equipped.Trinket1 != null && StyxWoW.Me.Inventory.Equipped.Trinket1.Cooldown <= 0 and Trinket2 for the 2nd trinket obviously Also I haven't tested this (since I don't have a glove enchant) but you might also have to add Code: && StyxWoW.Me.Inventory.Equipped.Gloves != null && StyxWoW.Me.Inventory.Equipped.Gloves.Cooldown <= 0 Not sure about the gloves though, I'm sure you'll figure it out. 8. If you do: Code: addCount() <= MarksmanSettings.Instance.Mobs addCount() >= MarksmanSettings.Instance.Mobs It's going to cast both AoE and Single target rotations when the amount of mobs equals to your mobs setting. So just do Code: addCount() < MarksmanSettings.Instance.Mobs for single target rotation. 9. I noticed you do, Code: !MarksmanSettings.Instance.MMSPEC and !MarksmanSettings.Instance.MMSPEC I don't see a reason to use them as "not" conditions, and you don't even need a setting for both. Just use Code: MarksmanSettings.Instance.MMSPEC for marksman stuff and Code: !MarksmanSettings.Instance.MMSPEC for survival stuff. 10. Instead of Code: Me.CurrentTarget != null && Me.CurrentTarget.IsAlive == true && Me.Mounted == false (Which repeats in the CC many times) I'd rather user Code: Me.GotTarget && Me.CurrentTarget.IsAlive && !Me.Mounted It's shorther, cleaner and should work just as fine. _____________________________________________________________________________ I'm going to add the CC I edited (based on 3.4 I believe) here for you so you can look through to code and see all the stuff I added, incase you want to implement any of those. There's a lot of stuff like, Interrupts, Aggro Management and Melee attacks, all with GUI options, as well other GUI options for spells and focus control for spells. Hopefully you'll find some of it useful and will be able to add some of it to future releases. This might not have been all I had to say but I can't remember anything else right now
Falldown, as i said i really appreciate all the suggestions/ideas and improvements to the CC i really do. So write whatever you want. However you cannot upload versions of your modified CC on this thread, or at the forum without permission from me or my team. Attachment has been removed by CodenameG
And I did! So a tiny update, just to implement some of the code that Falldown so kindly shared with me. Thanks to Falldown, you can with the latest update, choose which pet you want to summon. Some other things have been added as well, minor things which isnt really worth mentioning! - Shaddar
Hi guys, Can someone tell me how to edit out the code for aspect of the fox on movement, i have found a few guys have commented on other hunters in a raid moving around constantly changing aspects and called them botters. cheers.
I havent had any problem but i can see why people say it. Even i see that im a bot when changing aspects everytime i move
The version 3.6a is freezing tha game when cast a shot during 1 seg repeatedly from time to time. The old one 3.3 flows smoothly.. Any help?
No help if you dont attach a log. Which is a pretty standar routine at the forum in general whenever problems occur. This is an Alpha version, and without any feedback and such i cant do any updates.