Unknown2008-03-25 18:22:05
I have a system for influencing, but I've been hitting lag lately and I want to clean it up a bit. (I'm in Nexus, if that's relevant.)
Currently, it works like this:
Alias to set target
Alias to start system - first influence attack
Trigger detects target's response - set variable determining next influence attack
Trigger detects equilbrium back - next influence attack
Trigger detects success - end system
I could eliminate the first trigger. (Trigger detects equilbrium back - determine next attack, fire next influence attack) Would that use fewer resources?
Currently, it works like this:
Alias to set target
Alias to start system - first influence attack
Trigger detects target's response - set variable determining next influence attack
Trigger detects equilbrium back - next influence attack
Trigger detects success - end system
I could eliminate the first trigger. (Trigger detects equilbrium back - determine next attack, fire next influence attack) Would that use fewer resources?
Krellan2008-03-25 18:58:50
ooh nexusssss
You know what I personally do? Variable called beg. group called influence.
I have an alias for every influence attack cause I'm anal about having an alias for every skill.
In the strongest atack for every group, I added another two lines to:
1) #set beg (second strongest influence attack of that type alias)
2) #groupon influence
In the group called influence I have a trigger for You have recovered equilibrium. I have it do $beg
Then I go to the second alias for the second strong attack and add in the line #set beg (third attack)
Go to the third alias and have it loop to the strongest attack
For example, for begging my aliases are inwhe, inbeg, insup
inwhe-influence $tar with wheedling
#set beg insup
#groupon influence
insup-influence $tar with supplication
#set beg inbeg
inbeg-influence $tar with begging
#set beg inwhe
after this you can have a trigger for success to #groupoff influence to stop it. I've been to lazy to actually do that on any of them. I don't even have this looping thing set up for all the types just begging and something else mostly. It might actually be more lines and work, but I think it's one less trigger than you're using. So it's pretty much the same except the trigger you use to detect target response. Triggers always add more lag than aliases on nexus. Also if you're using any of those variable readers like {w} or whatever they are, they can add a good amount of lag. I don't use a single one and I don't know how Nubby manages it.
aww whoops, I totally wrote all that and didn't even read the last question where you said you could get rid of the line I just told you to get rid of.
You know what I personally do? Variable called beg. group called influence.
I have an alias for every influence attack cause I'm anal about having an alias for every skill.
In the strongest atack for every group, I added another two lines to:
1) #set beg (second strongest influence attack of that type alias)
2) #groupon influence
In the group called influence I have a trigger for You have recovered equilibrium. I have it do $beg
Then I go to the second alias for the second strong attack and add in the line #set beg (third attack)
Go to the third alias and have it loop to the strongest attack
For example, for begging my aliases are inwhe, inbeg, insup
inwhe-influence $tar with wheedling
#set beg insup
#groupon influence
insup-influence $tar with supplication
#set beg inbeg
inbeg-influence $tar with begging
#set beg inwhe
after this you can have a trigger for success to #groupoff influence to stop it. I've been to lazy to actually do that on any of them. I don't even have this looping thing set up for all the types just begging and something else mostly. It might actually be more lines and work, but I think it's one less trigger than you're using. So it's pretty much the same except the trigger you use to detect target response. Triggers always add more lag than aliases on nexus. Also if you're using any of those variable readers like {w} or whatever they are, they can add a good amount of lag. I don't use a single one and I don't know how Nubby manages it.
aww whoops, I totally wrote all that and didn't even read the last question where you said you could get rid of the line I just told you to get rid of.
Unknown2008-03-25 20:20:56
Haha! Thanks Krellan. I forgot I could change the aliases too. I've got a similar setup (ibeg isuppli iwheedle) so that really helps. Time to clear out a dozen triggers with {w}. <_<
