Ok so that issue I had before with the "Next Skill ID/ Off GCD", wasn't that it doesn't work, I just had to be in combat+target something. So I'm guessing the "Combat Status: Any" is not working properly. I have to be in combat+have a target for the skills to fire, even though those skills should fire outside of combat and without a target requirement.
(07-17-2014, 01:10 AM)jackie1234 Wrote: [ -> ]no it means when your skills are on GCD if the ability is an off GCD ability it will only use it when your currently on GCD but not while casting.
So this is really not good for casters to have on then, cause for casters you'd want to use Off-GCD during the cast and not after. Since none of your spells would be on GCD after you're done casting a spell. This is more for physical dpsers? Or was it coded to apply different operations for caster/non-casters? trying to understand the best use for this.
Edit: nvm it all makes sense now, regarding the off-GCD skills. it's not using those skills cause I was on SCH(a caster) and since you wont have any spells on GCD, it wont trigger the off-GCD skills. I guess it is working as intended, though wish it would have a different function for casters, like weaving in those off-GCD during the casting of a spell. What change is, I now have to target something for the swiftcast>summon to work.
Curious, do we have an expected or estimated time some of the features of the beta will be incorporated into the live version?
(07-18-2014, 02:00 AM)andysx Wrote: [ -> ]Ok so that issue I had before with the "Next Skill ID/ Off GCD", wasn't that it doesn't work, I just had to be in combat+target something. So I'm guessing the "Combat Status: Any" is not working properly. I have to be in combat+have a target for the skills to fire, even though those skills should fire outside of combat and without a target requirement.
(07-17-2014, 01:10 AM)jackie1234 Wrote: [ -> ]no it means when your skills are on GCD if the ability is an off GCD ability it will only use it when your currently on GCD but not while casting.
So this is really not good for casters to have on then, cause for casters you'd want to use Off-GCD during the cast and not after. Since none of your spells would be on GCD after you're done casting a spell. This is more for physical dpsers? Or was it coded to apply different operations for caster/non-casters? trying to understand the best use for this.
Edit: nvm it all makes sense now, regarding the off-GCD skills. it's not using those skills cause I was on SCH(a caster) and since you wont have any spells on GCD, it wont trigger the off-GCD skills. I guess it is working as intended, though wish it would have a different function for casters, like weaving in those off-GCD during the casting of a spell. What change is, I now have to target something for the swiftcast>summon to work.
but you cant... you can only cast 1 skill at a time in the game. This isnt a limitation of the bot but a game mechanic. You cant cast one skill(with a cast time) and use an instant cast skill while casting. There are some cases if you have enough spell speed that your cast time is faster then the GCD so you would be slightly on gcd still. but you cannot cast 2 spells at the same time.
Also feature idea, any attempt being made to make the 2D radar capable of compass mode? (to overlap with minimap)
You mean the ingame minimap ? it will be really hard to see anything since the ingame mini map is about 1/4 of the radar ( small version ). You will see dots cover up the whole minimap.
(07-18-2014, 12:04 PM)Skyrift Wrote: [ -> ]Curious, do we have an expected or estimated time some of the features of the beta will be incorporated into the live version?
The beta bot is different from the live bot. Eventually the beta bot will REPLACE the live bot. They are keeping live bot updated till they can replace it with the beta version. Therefore, a lot of features that are in beta will not make it to the "current" live version
I'm running into an issue when attempting to run Lost City of Amdapor (any profile). The first step requires two enemies (Madmite) to be killed. The problem is that the bot teleports into position, marks the encounter as completed/valid then immediately teleports to the next step without even attacking the mobs. This occurs again on the second boss which requires a normal mob to be attacked.
As far as I can tell, the issue is that the bot is executing the step before the mobs have appeared, regardless of the wait time. To alleviate the issue, I've added additional steps to the existing profiles (LCoA_Full, etc.) until the problem is resolved.
P.S. Only happening in the beta.
How fast is your client loading the zone ?
(07-21-2014, 12:40 PM)random73 Wrote: [ -> ]How fast is your client loading the zone ?
Reasonably fast, SSD on a SATA 3 connection. Not sure if that's relevant or not, as it's happening throughout the instance. Can anyone else run LCoA_Full or the fixed versions with a clean beta install and tell me if they encounter the same issue?
I'm having the same issue with lcoa. I'm also having issues with if one dies, it breaks the duty mode. will possibly become a leader or follower or will just sit there doing nothing. have to exit, reload all the bots, then can reenter the dungeon.
Large round of fixes incoming for hunt mode, duty, skill manager updates, cast preventions.. the list goes on. Duty is pretty unusable until it goes live though, I had to rework the death cne. I wanted to change the death CNE to not make the follower bots follow the leader temporarily, which somehow worked in my initial testing, but proved to be bad and I had to rework it again. End result should be an improvement, but the current version is useless, so that's my bad.