Timewarp - Real or fake!

[Kannkor]

I've had a few questions about the new Time warp checkbox on the CA/Named CA tabs. They are 'fake'... for now.

What I mean by this, is I designed and coded a full Time warp tab with those options on the Ca/Named CA tab. I'm not happy with all the workings of it, so I removed the timewarp code/tab for now, but forgot to remove it from the CA/Named CA tab.

Just to be clear, the Time warp option on the Ca/named CA tab does NOTHING right now.

I have most of the code in place, but running into some logistic issues. Let me explain~

My first attempt was something of the following..
I'm going to use Kick and Punch as examples.
Timewarp has a 1 minute reuse, and a 10s (there is a slider so you can increase it to 11s if you wish) duration.
My CA list would look like this:
Kick | TW
Punch
Kick

Which in English means:
Use Kick if TimeWarp is up
Use Punch
Use Kick ONLY if would be available for the next timewarp.

I put a 'timeout' function also, which meant if the illy didn't cast timewarp within ___ (lets say 2 minutes), then it would stop holding abilities back. In the case above, it would:
Use Punch
Use Kick

Until a timewarp was cast (putting it back into the rotation). This way if an illy died/wasn't even in the group/paused etc, the profile would still function 'properly'.

The problem I had, was out of combat. Because it would count up that time. (Unfortunately there's no simple way to just check incombat time).

Which lead me to thinking of the following...
Kick TW-Only
Punch
Kick TW-Hold
(random abilities here)
Kick

Which would mean:
Use Kick if TW is cast
Use Punch
Use Kick if it will be back up before TW is ready
(Use random abilities here)
Use Kick (regardless of interfereing with TW)

Which does give more options, but still doesn't allow/fix the issue with the 'timeout' option. Which I could remove/make it an option... [X] Enable Timeout after ___ seconds. But.. I still think we have an issue there.

I'm probably going to work on it this week some if I finish up some of the other things I'm doing, so if anyone has any feedback to make this option make more sense/better/more user friendly, posting sooner than later would be great.

 

[Luclore]

So I know little to nothing about coding. With that out of the way, what about utilizing the announce coding? Meaning having a set of ca's that are set to be used (if up/available) after the Illy announces Time Warp is cast/up/active (I know there is a delay after TW is actually cast, so I dont know how to handle other than putting in some ca's that arent TW dependant at the frontend?). Maybe a TW box (like NamedCAs)?

I do have a caster group that has gotten pretty well geared and puts out some good dps.....and I have survived without this function. So I would say unless there is a material benefit, I would spend your energy elsewhere (like finding a better campspot for the tanks on the Kradon HM fight )

 

[sirbuthed]

well im not sure what to do about the time out function other than adding a toggle/reset button to turn time warp timing function off, or resetting it when your illy gets back into play or having to click before or after combat . however im am now wondering if there is a way to allow a chain tab to fire only when time warp is up with a slider allowing it to fire a few second before . this would be huge for a trouby in the mage group along with a lot of debuffs that need pre casting . and depending on what you want pre cast will depend on how soon you want the chain to fire .

also there is a 15% chance to reset the timer on time warp when casting peace of mind . so a possible option to not cast peace of mind while time warp is eigther up or in the 5 second pre-use phase would be nice as well .

lastly and option to cast time warp only on a certain target might be usefull for adds , witch are ussually the dps checks and remove the need to micro manage your time warp with an mcp button .

 

[sirbuthed]

So I know little to nothing about coding. With that out of the way, what about utilizing the announce coding? Meaning having a set of ca's that are set to be used (if up/available) after the Illy announces Time Warp is cast/up/active (I know there is a delay after TW is actually cast, so I dont know how to handle other than putting in some ca's that arent TW dependant at the frontend?). Maybe a TW box (like NamedCAs)?

I do have a caster group that has gotten pretty well geared and puts out some good dps.....and I have survived without this function. So I would say unless there is a material benefit, I would spend your energy elsewhere (like finding a better campspot for the tanks on the Kradon HM fight )

the campspot work fine , you just arnt big enough . try to find an illusion that makes you bigger . i think kankor has set it up for the size of a big ass ogre

 

[Kannkor]

So I know little to nothing about coding. With that out of the way, what about utilizing the announce coding? Meaning having a set of ca's that are set to be used (if up/available) after the Illy announces Time Warp is cast/up/active (I know there is a delay after TW is actually cast, so I dont know how to handle other than putting in some ca's that arent TW dependant at the frontend?). Maybe a TW box (like NamedCAs)?

I do have a caster group that has gotten pretty well geared and puts out some good dps.....and I have survived without this function. So I would say unless there is a material benefit, I would spend your energy elsewhere (like finding a better campspot for the tanks on the Kradon HM fight )

The coding aspect I can handle fine, it's the logic of how people actually want this to work.

Lack of better words, I'm using the announce from Time warp... But how do YOU want the bot to handle when NOT to cast these abilities.
For example, you want a wizard to use ice comet (Yes bad example.. whatever!) during time warp. Does that mean you do NOT want him casting it otherwise? What happens if the illy dies, or isn't grouped (I don't want to scan the group make up before attempting to cast every single ability), simply never cast ice comet? Or should there be some sort of 'timeout'.

 

[Luclore]

My simple logic says that if TW is active, then the abilities that have TW clicked take priority over all else. If they are available to be cast, than great. If not, move down the list.

 

[Kannkor]

My simple logic says that if TW is active, then the abilities that have TW clicked take priority over all else. If they are available to be cast, than great. If not, move down the list.

So you wouldn't want the bot holding back these abilities at all?

 

[LuranEQ2]

Because I know you'll appreciate the added complication, what about DoTs getting overwritten with TW'd versions of those DoTs, but then not overwriting those (either with or without TW).

As far as holding things back, I don't know for certain but it seems to me that would lead to higher spike damage during TW, but possibly lower or no difference in overall damage output, so I'm not sure the way you've designed it would be all that useful to me personally, though I'd be happy to experiment around with it. However, the ability to selectively overwrite DoTs when TW is up so that they tick out as doubles (even after TW wears off) would be nice.

 

[fl0pster]

Personally yes, I think there should be a delay to see if TW is up… Realistically there are only going to be a few abilities that are checked for tw, and normally those abilities are the longest recast. Finding the comfortable medium between the lack of dps not casting and the potential dps from the few abilities during TW are going to be the pita. 11 seconds to benefit double a normal amount can be huge..

It really will probably have to be evaluated on a class by class basis.. as for raiding most ppl know how many cycles they can get before or with a tw. maybe the question is easier answered when those ppl post their experiences on how they actually play.

 

[fl0pster]

maybe the wait could be half or quarter of the reuse for each ability?

 

[Luclore]

So you wouldn't want the bot holding back these abilities at all?

Hmmmm. Well, yes it would be nice if the bot held those abilities back until TW was active - my earlier posts really were about trying to keep it simple. Not sure if that is the right path or not.

As another poster offered I will too - can help test it out for ya if you want.

 

[Kannkor]

Hmmmm. Well, yes it would be nice if the bot held those abilities back until TW was active - my earlier posts really were about trying to keep it simple. Not sure if that is the right path or not.

As another poster offered I will too - can help test it out for ya if you want.

I'll tinker with it.. Think I'll try the 3 option thing...

TW only
TW hold
(nothing)

TW only - cast during TW only.
TW hold - Cast this ability only if it will be back up when TW *should* hit.
(nothing) - Cast this ability.

Won't have any time out for the current time. So if you have a fully TW profile then you drop the illy, may need to tweak it or something.

 

[leery]

I think that approach makes sense Kannkor. I would want my toons to be able to cast the optimal abilities during time warp. To make that happen, there seems to be that dependency on illy in group=yes or no. If the illy is in group, I would want to use a timewarp optimized profile. If the illy was not in group I would want to use a different profile.

This may be too complicated, but...

What if we had two profiles, and the bot loaded up a different profile automagically -or by asking- based on the addition or removal of an illy in the group?

 

[allania]

Another way and Im not sure if you have thought about doing it this way, but is to have it the opposite way and the DPS tell the illy when they want Time Warp. You could then have a tab on the illy for time warp priority so they would listen to say your warlock over your monk for time warp calls. You could then have a little check box next to the ability to ask for time warp. They would then wait oh 6-7 seconds and use the ability. If time warp was up they would get it. People of course would want to use this on your longer abilities but that is already a given.