• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • [Released] YBMoP-BT-Rogue

    Discussion in 'Archives' started by Xcesius, Feb 1, 2013.

    Thread Status:
    Not open for further replies.
    1. Clubwar

      Clubwar Member

      Joined:
      May 3, 2012
      Messages:
      907
      Likes Received:
      3
      Trophy Points:
      18
      Have any button to reset configuration to default in Gui?
       
    2. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      Nothing in the GUI, just delete the settings files instead!
       
    3. Xcesius

      Xcesius Community Developer

      Joined:
      May 1, 2011
      Messages:
      2,050
      Likes Received:
      61
      Trophy Points:
      48
      For assassination rogue use PR instead. I will use some time in the upcoming weekend to rewrite it somehow

      I also need to finish up my dk routine, which takes priority.
       
    4. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      Have PR been updated now then? Cuz ever since you started this CR its been preforming better than PR!
       
    5. xander678

      xander678 New Member

      Joined:
      Jul 13, 2012
      Messages:
      56
      Likes Received:
      0
      Trophy Points:
      0
    6. Refrakt

      Refrakt New Member

      Joined:
      Dec 18, 2011
      Messages:
      130
      Likes Received:
      0
      Trophy Points:
      0
      PR = pure rotation.

      i have been using it. the difference between YBMop and PR are :

      PR open with 5 rupture then slice and dice.
      PR do not have auto preparation when vanish buff detected.

      developers at PR are more busy with warlock cc and dk cc.
       
    7. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      Bored at work, so I decided to look thrugh all code (In hopes of learning stuff, damn thats hard to understand for a total code-noob -.-), found that Anticipation stack checks in YBMoP_Global.cs is set to "{ get { return Me.HasCachedAura(114015, 4); } }", correct me if im wrong here, but shouldnt it be "{ get { return Me.HasCachedAura(115189, 4); } }" ?? There is 1-4, I just used the 4th one as an example.

      114015 Anticipation - Spell - World of Warcraft = The tallent
      115189 Anticipation - Spell - World of Warcraft = The actuall buff


      EDIT:
      I realised something has to be wrong when I found "YBSpell.Cast("Envenom", ret => G.Anticipate4stacks)," in YBMoP_Ass.cs, in my head that line of code means "Envenom whenever Anticipation reaches 4+"
       
      Last edited: May 30, 2013
    8. Xcesius

      Xcesius Community Developer

      Joined:
      May 1, 2011
      Messages:
      2,050
      Likes Received:
      61
      Trophy Points:
      48

      HB detect the buff as 114015. Either that or it won't detect it properly, I will take a look later when I have time

      *update

      [22:01:40.005 D] [SpellManager] Adding known spell: Anticipation (114015)

      The debug also reported the buff id as the same id. Bug has been reported, but hopefully the aura detects it properly.

      So I've changed the id
       
      Last edited: May 30, 2013
    9. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      Ah alright, well it was worth a try I guess :)
       
    10. Xcesius

      Xcesius Community Developer

      Joined:
      May 1, 2011
      Messages:
      2,050
      Likes Received:
      61
      Trophy Points:
      48
      I updated my answer.
       
    11. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      That update seems to have broken the CR, only Singular is showing up in the list now!

      EDIT:
      Adding these lines seems to make it work again:
      internal static bool Anticipate3stacks { get { return Me.HasCachedAura(115189, 3); } }
      internal static bool Anticipate2stacks { get { return Me.HasCachedAura(115189, 2); } }
      internal static bool Anticipate1stacks { get { return Me.HasCachedAura(115189, 1); } }
       
      Last edited: May 30, 2013
    12. Refrakt

      Refrakt New Member

      Joined:
      Dec 18, 2011
      Messages:
      130
      Likes Received:
      0
      Trophy Points:
      0
      Yup, only Singular and PR are shown after update.
       
    13. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      Untill alxaw have updated it again, you can use this file, added the 3 lines to make it work again!
       

      Attached Files:

    14. retalin

      retalin New Member

      Joined:
      Mar 6, 2013
      Messages:
      45
      Likes Received:
      0
      Trophy Points:
      0
      Same with me
       
    15. mcdeman

      mcdeman Member

      Joined:
      May 10, 2011
      Messages:
      389
      Likes Received:
      5
      Trophy Points:
      18
      Compiler Error: \Honorbuddy\Routines\YourBuddy%20MoP%20BT%20-%20Rogue\Routines\YBMoP_Ass.cs(92,150)
      : error CS0117: "YBMoP_BT_Rogue.Routines.YBGlobal" не содержит определение для "Anticipate3stacks"
       
    16. TricksAnthem

      TricksAnthem New Member

      Joined:
      Jan 28, 2011
      Messages:
      93
      Likes Received:
      0
      Trophy Points:
      0
      I'm not sure if this is intended, but i was under the impression that it is bad to mutilate at 4cp just to hit 5cp. The CR is doing that constantly, how do i fix it to envenom at 4/5 cps and not push for 5 cp all the time.
       
    17. Xcesius

      Xcesius Community Developer

      Joined:
      May 1, 2011
      Messages:
      2,050
      Likes Received:
      61
      Trophy Points:
      48
      Commited fix for it.


      Please update :)

      Taking the night now, 6:43 am :)
       
    18. Rangbang

      Rangbang Member

      Joined:
      May 9, 2010
      Messages:
      452
      Likes Received:
      0
      Trophy Points:
      16
      Envenom should ALWAYS be used at 5 points, so if you have 4p its better to Mutilate again to get a 5p Envenom and waste a point (Unless you have Anticipation, then its only saved, not wasted) than to Envenom on the 4 points.
       
    19. Clubwar

      Clubwar Member

      Joined:
      May 3, 2012
      Messages:
      907
      Likes Received:
      3
      Trophy Points:
      18
      I wish see your assesination changes soon, i think your CR is the best for Rogu
       
    20. Refrakt

      Refrakt New Member

      Joined:
      Dec 18, 2011
      Messages:
      130
      Likes Received:
      0
      Trophy Points:
      0
      Long duration (450 +/-20%)
      Mut > SnD > Shadow Blades> Mut > Rupture > Vendetta > Standard Rotation
      Yields:199,079 dps (error: 134dps)
      Distribution - Max: 226,300, min: 176,284 - Range: 50,016

      Mut > SnD > Mut > Rupture > Vendetta > Shadow Blades (*)> Standard Rotation
      Yields: 199,265 dps (error: 134dps)
      Distribution - Max: 226,455 min: 180,126 - Range: 46,329

      Mut > Shadow Blades> Rupture > Mut > SnD> Vendetta > Standard Rotation
      Yields: 198,805 dps (error: 134dps)
      Distribution - Max: 230,443, min: 178,454 - Range: 51,989


      (*) - It is marginally better to wait for the GCD to end before using Shadow Blades here

      Borrowed my old formatting and added range (a higher range means results will be more inconsistent each time you try the opener).

      If people would like me to run this again on short duration (gives a nice view of burst and a "closer" view of the opener) as was done before, let me know.

      This cr always mult - snd - muti to 5 cp then rupture.
       
    Thread Status:
    Not open for further replies.

    Share This Page