Question - Condition used with |Weave command on Bard

[AnotherJohn]

As the title states I am having trouble getting my condition to work with |Weave and I am having to manually fire "Clickies" and AA's. My first question is, does a Condition or a |Weave work with MQ2Twist? If they do not, then I don't need to proceed any further. If they are supposed to work with MQ2Twist then my question is with the formatting of the command. Would the Condition command or the |Weave command come first?

Blade of Vesagran|75|Cond1|Weave
or
Blade of Vesagran|75|Weave|Cond1

I am having trouble getting just |Weave or |Cond1 to work on it's own which is why I am wondering how it all fits together with MQ2Twist. Is |Weave with a Bard necessary as that is something figured into stopping and starting MQ2Twist? Any insights would be appreciated. I am trying to rule out any problems with this part before I move on to other things which may be causing my problem. Thanks

 

[Terit]

I'm pretty sure that you can't use weave and conditions. Weave is intended for spells that are off the GCD and can be cast when everything else is waiting.
Good news though! You don't need it;
DPS1=Blade of Vesagran|75|Cond1

Works just fine.

 

[Killertoxin]

I am using DPS23=Blade of Vesagran|99|Cond9 whereas Cond9=!${Me.Song[Blade of Vesagran].ID}

 

[AnotherJohn]

Thanks guys,
Terit, thanks, was trying to use |weave with "clickies" and AA's and thinking maybe they would either fire while song was casting (AA's) or in between songs of a melody (clickies) and the melody would continue where it left off instead of MQ2Twist starting the melody over. I will take out all the |weave commands and just go that route.
Killertoxin, my Condition on that particular item was Cond1=${Target.Named} && ${Me.XTarget[1].Level}>=${Math.Calc[${Me.Level}-4]} || ${Me.XTarget[1].Level}>=${Math.Calc[${Me.Level}+4]} as I try to set up my ini to "automatically" burn some items and AA's and not have them firing on "trash" and not have them ready when I need them.
Thank you both for taking the time to respond. If anyone else has any additional thought let me know.

 

[Terit]

So
Cond1=${Target.Named} && ${Me.XTarget[1].Level}>=${Math.Calc[${Me.Level}-4]} || ${Me.XTarget[1].Level}>=${Math.Calc[${Me.Level}+4]}
Is clever, but very complicated.

To be clear; you're saying Click my BoV when: Target is a named mob AND is greater than or equal to four levels lower than me
OR
target is greater than or equal to four levels higher than me?

I think you might need some parenthesis around the statement after the AND

Easier might be Cond1=${Target.Named} && (!${Target.ConColor[GREEN]} && !${Target.ConColor[GREY]} && !${Target.ConColor[LIGHT BLUE]})

Which says: Target is Named and NOT Green, NOT Grey, NOT Light Blue

 

[AnotherJohn]

To be clear; you're saying Click my BoV when: Target is a named mob AND is greater than or equal to four levels lower than me
OR
target is greater than or equal to four levels higher than me?

Yes Terit you read it correctly. I am on a TLP and some of the named I encounter even if they are a bit lower in level than I am I need to burn but didnt want to set the burn for too low for all mobs. So I set it to only burn regular mobs if 4 levels higher than me even if they are not named. I can then play with the levels a bit as I advance and need different parameters for new content.

Easier might beCond1=${Target.Named} && (!${Target.ConColor[GREEN]} && !${Target.ConColor[GREY]} && !${Target.ConColor[LIGHT BLUE]})

This is interesting, I never saw an example done with mobs color before and didn't know that could be done. Might be worth a try but I think I would have to add a second part to do what my current condition does to burn higher level unnamed mobs.

Cond1=${Target.Named} && (!${Target.ConColor[GREEN]} && !${Target.ConColor[GREY]} && !${Target.ConColor[LIGHT BLUE]}) || ${Target.ConColor[RED]}

Thanks for your post always nice to learn a new way to do something.

And for anyone reading this later, I have removed all the |weave commands on anything that has a condition. I did however leave the |weave command on two clickies I want to fire every time they are available and can be clicked while song is casting and it works perfectly. So I am guessing the the |weave command and any condition seem to conflict.

 

[Terit]

No problem, not sure if it's easier on a processing level but it seems cleaner atleast (in my opinion). Be sure to test it out first, but I'm 90% sure of my work, lol.

 

[Many_Whelps]

Weave on a bard, I imagine, won't work like it does for casters. Nor do you need it to. Any clicky with a cast time, such as epic 2.0 will always interrupt your twist (or melody). This is a big reason bard players have been begging to have it made instant cast. Any clicky or AA that is instant can be used *while* casting. So there is no need for a bard ini to use weave. On casters, it's absolutely possible to have conditions on weave.

 

[GPS_Soldier]

Instant cast clicky should not interfere with melody or twist. There will be new updates to KISS for bards coming out on the next version. These changes will allow you to have timed inventory items ( such as epic) to fire off and then continue with your twist where it left off.

There really should be no need for |weave either way. I attempted to use weave to help with the bug that could happen causing your bard to have gems locked up and even issuing /twist off|stop still did not fix the locked up gems.

I have even modified my mq2twist to have my epic and other non-instant item be twisted with /twist once itemsong# that I assigned and still had variously lockups.