Self-targetting Mimicry, Ascension, And Relay Dilemma

Midnyte_ride

Active Member
I'm trying to improve my Coercer's Mimicry damage by pairing it with compatible Ascension nukes. I'd like a way to set it up to cast Temporal Mimicry on the Coercer themself prior to casting an Ascension nuke. The problem I'm facing is I can't find a way to apply both the targeting requirement (cast on self) and the cast-before-XYZ-spell trigger.

My first attempt was to add Temporal Mimicry as a pre-cast on Cascading Force. This satisfies the trigger, but not the targeting requirement. So I also attempted to edit the ability export to make Ogre think Temporal Mimicry had to be targeted on myself.
Either I didn't edit the export correctly, or it's not capable of doing what I needed it to do (target that one ability at the PC only, despite it being a targeted spell), because it didn't work. Temporal Mimicry kept being targeted on the Coercer's current target or target's target.

Second attempt was to use the API Relay command (in this case OgreBotAPI:CastAbilityOnPlayer_Relay[CoercersName,Temporal Mimicry,CoercersName] ) set as an announce on Hemorrhage (quick casting, short reuse spell) set as a pre-cast on Cascading Force.
The problem here is the order of events doesn't play in my favor, with Ogre prioritising the pre-cast order over the Relay command. It would cast Hemorrhage, then Cascading Force, then Temporal Mimicry on the Coercer.

So I'm seeking suggestions how to proceed from here. I can reliably get the Coercer to cast Temporal Mimicry when other group members are using their Ascension nukes, but the most effective usage I can think of requires the Coercer be a viable target as well.

Thanks in advance for any replies!
 

Kannkor

Ogre
My first attempt was to add Temporal Mimicry as a pre-cast on Cascading Force. This satisfies the trigger, but not the targeting requirement. So I also attempted to edit the ability export to make Ogre think Temporal Mimicry had to be targeted on myself.
Either I didn't edit the export correctly, or it's not capable of doing what I needed it to do (target that one ability at the PC only, despite it being a targeted spell), because it didn't work. Temporal Mimicry kept being targeted on the Coercer's current target or target's target.
This is working as intended. The reason for it is, if you have a self ability (like a for real one, not a pretend one) you do not have to target yourself to cast it, you can just cast away. So when you marked TM as a self only ability, it said 'great, we don't need a target, just click it!'.

Second attempt was to use the API Relay command (in this case OgreBotAPI:CastAbilityOnPlayer_Relay[CoercersName,Temporal Mimicry,CoercersName] ) set as an announce on Hemorrhage (quick casting, short reuse spell) set as a pre-cast on Cascading Force.
The problem here is the order of events doesn't play in my favor, with Ogre prioritising the pre-cast order over the Relay command. It would cast Hemorrhage, then Cascading Force, then Temporal Mimicry on the Coercer.
This is also working as intended. Once you enter a caststack item, no API commands that are queued can be activated until the caststack item is done. Then it will process any queued items (In this case the cast).


Unfortunately in the end, I don't have a good answer for you. The way pre/post cast was set up, was never designed to deal with a target. If/when I get time, I may look at rewriting the entire thing to support targets. But realistically, you should continue to look for a different solution in the mean time :)
 

Midnyte_ride

Active Member
This is working as intended. The reason for it is, if you have a self ability (like a for real one, not a pretend one) you do not have to target yourself to cast it, you can just cast away. So when you marked TM as a self only ability, it said 'great, we don't need a target, just click it!'.
Yea, I eventually realized that is the case. I held out a little hope that one of the TargetType's might be a target-self-retarget-previous but that was a long shot.

Thanks for the answer Kannkor. It's just bad luck I chose the ascension classes in the combinations I did and haven't really bothered to do more than one per toon. Will work with what I have :)
 
Top Bottom