Prior to the new source update, pet auto hp/mp potion did operate regularly under the condition of Dark Sight. While leveling my first shad, I was able to sit in dark sight dropping meso at himes while being attacked by their magic ability and still get healed up by my trusty ol' golden pig. Post-new source this seems to have been removed and even though I initially only saw it as a nerf to dropping meso while in dark sight, I have also experienced it as im using the bstep+ds+assassinate combo that is the main attacking combo for 4th job bandits. If the hit of a boss or mob lines up as I go into dark sight, my pet won't heal me and I will be forced to have to use a potion manually and usually delay my attack. I find this sort of strange that pet auto hp/mp works for every other 4th job while they are using their attacks and it doesn't for essentially only shad because you are either sitting in dark sight dropping meso (if ur range sucks like me) or you are using bstep+dark sight+assassinate which both require dark sight. I believe that pet auto hp/mp should be adjusted so that it again will heal you while in dark sight for dark sight is crucial to be an efficient attacker as a shad.
I have this issue very frequently as well. This is the reason I don't drop mesos during zak bodies is because it's to easy to die with the failing auto hp. There is actually something that might fix this problem and I think that assassinate should be able to be cast while in the air. The problem stems from a delay from getting hit before actually entering dark sight and then being stuck unable to pot yourself. While you are using the bstep>ds>nate macro, if you get hit at the end of the bstep animation (which is when you'll most commonly be hit since bstep has iframes) then your character will get knocked back and then put into dark sight (due to server latency). You are essentially always going to take that hit because your client needs time to communicate with the server that you are actually going into dark sight. The big problem is that when you get knocked back, your macro can't continue because the assassinate can never trigger, since getting knocked back launches you into the air. This leaves you scrambling to leave dark sight manually and the potting manually. If assassinate could be cast in the air, it would be much easier to pot yourself, since you can pot just fine while in the animation for assassinate. I think this is the most elegant way to solve this issue, although I would probably just prefer auto pot working while in dark sight again.
Yes! I understand that issue completely as well and thought about that but don't believe it would be very easy to allow assassinate to be usable in the air. I'm not entirely sure how the code will be in terms of difficulty which is why I just recommended reverting back to the old days where pet auto hp/mp was usable in dark sight. I like your idea too, but think my recommendation is just a simpler fix.
either fix, i'd be totally happy! always makes me happy to see other shadowers speaking out for changes! I feel like we are pretty under-represented on the forums
I agree! the shad buff bringing attention to issues such as these is awesome too! Love all the new buccs/pallys/shads im seeing now. The buffs certainly show that the server cares about future of the game i love.
Another thing worth noting, is that on mounts, you aren't allowed to use pots, similarly to dark sight. But unlike dark sight, autopot still works for mounts
I was wondering about this post earlier when my pet failed to heal me 3x in a row at zak today because my hp dropped while I was in dark sight disallowing my pet auto hp to take effect. This is incredibly bothersome as a shad even over a year later. No other class is forced to use an ability that prevents the use of hp pots to maximise dps other than shad so I feel like it would be a fair change to allow the use of auto pet hp while in dark sight. The previous argument made by @LichWiz that this works while mounted, but not in dark sight is a strong point that I believe should justify this change.
