Is there a way to equip sets based on whether or not you're in a party?
just make a rule in status_change(new,old) function
like
Code:function status_change(new,old) if party.count > 1 or player.isallymember then if new=='Engaged' then equip(sets.Engaged_party) elseif new=='Idle' then equip(sets.Idle_party) elseif new=='Resting' then equip(sets.Resting_party) end else if new=='Engaged' then equip(sets.Engaged) elseif new=='Idle' then equip(sets.Idle) elseif new=='Resting' then equip(sets.Resting) end end end
Two things:
1. Can you get console errors to print to a log? I swear someone mentioned there was a way to do it, but I can't find it in search for the life of me.
2. Anyone have an example of how to do a custom AM3 timer I could look at? I tried ripping off Sechs's code from a few pages ago, but I'm getting errors and can't currently see what they are due to them getting cut off in the console.
Thanks!
well this is the custom AM3 I made for my brd, put this inside precast, have to change the ws... and check durations(in secs) since if its for mythic it varies
and put this into your aftercast functionCode:if spell.english == 'Mordant Rime' then amlevel = math.floor(player.tp / 1000) amtimer = 0 if buffactive['Aftermath: Lv.3'] then amtimer = 1 return elseif amlevel ~= 3 and buffactive['Aftermath: Lv.2'] then amtimer = 1 return else if amlevel == 1 then amdur = 270 -- AM 1 Duration elseif amlevel == 2 then amdur = 120 -- AM 2 Duration else amdur = 180 -- AM 3 Duration end end end
Code:if not spell.interrupted and spell.english == 'Mordant Rime' and amdur and amdur > 0 and amtimer == 0 then am = 'Aftermath: Lv.'..tostring(amlevel) send_command('timers d "Aftermath: Lv.1"') send_command('timers d "Aftermath: Lv.2"') send_command('timers d "Aftermath: Lv.3"') send_command('timers c "'..am..'" '..tostring(amdur)..'') if amlevel == 3 then send_command('wait 150; input /echo 30 secs remaining AM 3 ') end end
Hmm, having a bit of problem during abysea party, curing waltz seems to be downgrading at the worst times, any way to easily disable the automatic downgrading of curing waltz? just want to curing waltz 4, without it downgrading to 3 or 2 if i dont have enuf tp to do it, thx
New user to GearSwap here- quick noobish question: Do I need to go through all of my macros and get rid of all of my windower macro commands? i.e. /console exec WhmCure.txt or can I leave them be in the event GearSwap breaks/will leaving them interfere with GearSwap's functionality?
Hey guys, does anyone know if gearswap or windower resources have been updated with Haste II, and Geo-Haste yet? I'm trying to update my haste rules to account for this, but not having any luck. It's been quite a while since these were added, so I figure I must be missing something.
I've looked in buffs.lua, which has a haste with ID 33, and another with ID 580. (is this haste II?) Using buffactive[33] definitely works, but it also returns true when Haste II is applied.
Any ideas?
I don't think gearswap can tell the difference between Haste and Haste 2, i think they share the same buff slot, but i could be wrong.
yea, Haste and Haste II, give same buff(Haste)
That's unfortunate. I saw there were two Haste's with different ID's and figured it should work.
Can anyone think of another way to achieve this? i.e. Filtering the log, etc.
one is haste the other is geo haste
Byrth what's the status fo the Midaction thing we mentioned? I have issues in trying to keep up.
If I recall the issue was that when using Midcast() sometimes you would get locked in your current gear for X seconds and unable to perform any action.
I remember you saying you had to do quite a long and complex reworking of the midcast function, did you manage to find time to start yet?
Afaik it is done.You need to put:
In aftercast.Code:if midaction() then return end
Will that code prevent the lockin out of being able to do anything? Cause when i am trying to sleep things on my mule lately he just stands there sometimes (he doestn appear to be tryin to cure me or anything either) This didnt seem to be a problem til bout 2 weeks ago or so. I suspect its the midaction thing.
There is nothing in gearswap that will automatically lock you out. If you have a midaction return rule, then it might if midaction doesn't work. AFAIK, the only situation where midaction won't work is when packets are dropped by the server.