• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Troubleshooting rotations

    Discussion in 'Community Developer Forum' started by Cydex, Jan 17, 2016.

    1. Cydex

      Cydex New Member

      Joined:
      Oct 7, 2014
      Messages:
      24
      Likes Received:
      0
      Trophy Points:
      0
      I have recently bought this bot, and thought id work on some rotations for the classes i currently play - Assassin and Merc. I guess not many really use this bot for anything but low level grinding perhaps?

      My thoughts was to try to optimize dps for use in ops and perhaps some dual-boxing eventually.. But to get to that point i kinda need some troubleshooting. So far i (atleast personally feel) have improved the rotation a bit, upping my "dummy dps tests" a few 100 dps, but there are some bugs i wanna sort out. I also am looking into Assassin darkness (tank) rotation for threat and found something else.

      Not sure if its a "bug", but i cant figure out how to understand WHY it isnt working. I have tried to change the setting in "GlobalSetting" to <LogLevel>Verbose</LogLevel> (From Info), but reading my logs nothing changes from that. Still just lists the rotation and no more info. Perhaps nothing more to be gained?

      Problem #1:
      In my Deception Assassin rotation, i have this :
      Code:
      Spell.Cast("Ball Lightning", ret => Me.BuffCount("Induction") == 2 && Me.HasBuff("Voltage") && Me.BuffCount("Static Charge") < 3),
      Ie. i try to make it skip that one if Discharge is up (And i have voltage debuff that should be up 100%). Anyway, the thing that happens is that it will wait until the CD is up before moving on. The spell itself has a 5 sec cd, regardless of me having Induction buff up. So, why does it wait until the cd is up? Should it not just move on when the spell is on cd? Waiting at that for over 1 second is a waste of dps as imo it should continue to the next line and cast something else.. But that does not happen.

      Problem #2:
      When trying for some Darkness rotation, i want to prioritize "Depredating Volts" when thats up, and added this line in my rotation:
      Code:
      Spell.Cast("Depredating Volts", ret => Me.BuffCount("Harnessed Darkness") == 3),
      Going through this it will cast Depredating Volts a few times when its up, and then just stop casting it altogether. Its "up" and debuff is counting 3 and everything, but it would rather saber strike than cast that... Only way to get it to cast it again is to pause the rotation (F8), cast it manually, then restart the rotation.. then it casts it a couple of more times in the rotation, and it stops doing it again.

      I was initially thinking it might just be that some bug made it think it had MORE than 3 stacks, so i tried adding >= and stuff like that, but to no avail.. (Even tried >2). Still just do the same.

      So, is this a problem with the way the bot counts debuffs (on that particular one), or is it a rotational bug? Setting it to cast it without having 3 stacks is not preferred tho.

      Also the Darkness rotation from "DefaultCombat" is listing Force Lightning as the spell, so i changed it.. Cos its replaced by Depredating Volts..

      Sorry if this the wrong place or method to bring this up, but im trying to learn something :)

      C
       
    2. Cryogenesis

      Cryogenesis Moderator Moderator

      Joined:
      Jul 13, 2010
      Messages:
      2,128
      Likes Received:
      13
      Trophy Points:
      38
      Routines just got an overhaul from lockselector to priorityselector.
      Problem is, this will up the fps but reduces reliability in dps due to the fact its waiting on the game.
      With lockselector the bot forces every frame an update to the game, but you get loss in fps.
      Try to switch and see if you get better results.

      Also log level doesn't function properly. Aevitas is looking into it to log better. Don't know yet what will be changed...
       
    3. Cydex

      Cydex New Member

      Joined:
      Oct 7, 2014
      Messages:
      24
      Likes Received:
      0
      Trophy Points:
      0
      Will do some compares on the dummy between them, but just for laughs and giggles i tried with lockselector in an ops i ran, and the fps loss was rather harsh to be using it like that tbh.

      C
       
    4. Cydex

      Cydex New Member

      Joined:
      Oct 7, 2014
      Messages:
      24
      Likes Received:
      0
      Trophy Points:
      0
      Did some testing today, but i guess i dont really have the patience to do a "large sample" of rounds on my merc..

      The rotation does seem to be a tad more "accurate" using lockselector, but the difference is not that much. The fps on the other hand is. Using the ingame fps thingy, i get dips (inside my ship, so in a ops/world situation the problem gets worse) down around in the 80'ies using priorityselector, where i get dips in the low 50'ies using lockselector. 30 fps difference is not worth the possible more dps i get.

      I would assume the arsenal rotation is one of the easiest around, so i would say its a nice benchmark :)

      C
       
    5. Cass

      Cass New Member

      Joined:
      Jan 24, 2014
      Messages:
      98
      Likes Received:
      2
      Trophy Points:
      0
      Another thing i realized its to try different queue cast time on game preferences. It was stated here before that .25 its the best setting. In my case its .5 because of my lag
       
    6. Cydex

      Cydex New Member

      Joined:
      Oct 7, 2014
      Messages:
      24
      Likes Received:
      0
      Trophy Points:
      0
      I actually did experiment with it some, and for me i found 0.5 to make the rotation a bit unstable, so i just turned it to 0. But it may be .25 is the best setting. Thx for the tip :)

      C
       

    Share This Page