I have been trying to add an aftermath set to my drk.gs It seems to be working, but there is a delay in equipping the new set. This is the current rule that i am using, when aftermath wears, it changes immediately to the normal set, but when i gain the buff it seems to take a while to equip
function job_buff_change(buff, gain)
if state.Buff['Aftermath'] then
equip(sets.engaged.Apocalypse.AM)
end
end
Any suggestions would be appreciated
Thanks
this should work. on "default tp gear".. put your default set.. or just remove itCode:function buff_change(status,gain_or_loss) if status == "Aftermath" then if gain_or_loss then equip(sets.engaged.Apocalypse.AM) else equip(sets.default.tp.gear) end end end
edit.. Didn't read the part you already had a code for when it wears... but how/where?... would be the best if you post using pastebin or something similar your .lua...
ah is Motente one... I don't fully understand all those code... the one I gave should work.. but no idea if will overlap w/ the codes he have to manage the buff changes...
anytime i engage and that's the only time i see it.
Fairly certain i didn't change anything in my pup file other than gear, but i'm suddenly getting this error message when i load my pup file:
Gearswap: lua error (runtime) - ...ppswindower4/addons/gearswap/data/shepardg_pup.lua:11: attempt to call global 'init_include' (a nil value)
Checked my file vs. the master file from mote's pastebin and that section hasn't changed, so unsure what has a happened :/
EDIT: Nevermind, i'm dumb and checked, and saw that the files were cleaned up and updated, replaced them and good to go now ^^
alright, i have fucked something up
I litterly just uninstalled windower4, deleted the folder with all the stuff i had in it, then reinstalled (didn't reboot, could this have fucked me? no instances of FFXI were open)
I am still getting massive errors on a ton of addons. I have no plugins loaded.
EDIT: (sorta) so gearswap seemed to be working but autocontrol (pup addon) seems borked...
I'm confused![]()
Pushed an update that should solve some issues from the massive refactoring of last time. Also, Manibozho/Bokwus/etc. Augments should now be handled (the same way as the other ones).
As always, please let me know if you guys find any issues: https://github.com/Byrth/Lua/issues?state=open
Hi!
I'm getting also a spam message in the Mote SMN.lua...
SMN.lua:315: attempt to index field 'Avatar' (a nil value)
I'm getting it as soon as the pet attacks.
swaps to midcast magical BP seems not to work...maybe because of the error?!
Ah, if you're using a sidecar, I split the .Pet sets to .Avatar and .Spirit. When I did that I also changed .idle.Pet.Favor and .idle.Pet.Melee to .idle.Avatar.Favor and .idle.Avatar.Melee. You'll want to adjust your sets for that. Sorry about that.
For the midcast stuff, I'll need to look at it and see.
Thx for the quick reply Mote! I'll give it a try^^
Fix for the thf issue people have been having has been pushed.
Hey Mote, I noticed with your COR.lua that when I used the rolls that were enhanced by AF3+2 gear (Casters, Coursers, etc) were not equipping the additional Roll extending gear. So I changed the lines from
toCode:sets.precast.CorsairRoll["Caster's Roll"] = set_combine(sets.precast.JA["Phantom Roll"], {legs="Navarch's Culottes +2"}) sets.precast.CorsairRoll["Courser's Roll"] = set_combine(sets.precast.JA["Phantom Roll"], {feet="Navarch's Bottes +2"}) sets.precast.CorsairRoll["Blitzer's Roll"] = set_combine(sets.precast.JA["Phantom Roll"], {head="Navarch's Tricorne +2"}) sets.precast.CorsairRoll["Tactician's Roll"] = set_combine(sets.precast.JA["Phantom Roll"], {body="Navarch's Frac +2"}) sets.precast.CorsairRoll["Allies' Roll"] = set_combine(sets.precast.JA["Phantom Roll"], {hands="Navarch's Gants +2"})
and it fixed the problem. Just a heads up, thanks for everything as usual.Code:sets.precast.CorsairRoll["Caster's Roll"] = set_combine(sets.precast.CorsairRoll, {legs="Navarch's Culottes +2"}) sets.precast.CorsairRoll["Courser's Roll"] = set_combine(sets.precast.CorsairRoll, {feet="Navarch's Bottes +2"}) sets.precast.CorsairRoll["Blitzer's Roll"] = set_combine(sets.precast.CorsairRoll, {head="Navarch's Tricorne +2"}) sets.precast.CorsairRoll["Tactician's Roll"] = set_combine(sets.precast.CorsairRoll, {body="Navarch's Frac +2"}) sets.precast.CorsairRoll["Allies' Roll"] = set_combine(sets.precast.CorsairRoll, {hands="Navarch's Gants +2"})
Okay, so after looking at these for a while and thinking about it, I've come up with two permanent limitations of GearSwap:
1) There is no reasonable way for me to know which items can be equipped at the same time. Thus, I cannot make GearSwap avoid attempting to equip incompatible items (Staff and Shield, Cloak and Hat, etc.) In those cases, the behavior is undefined. I can't say for sure which you will end up wearing. The safe way to do this is to always set the slot to be empty if you want it empty. So:
This is a limitation that I will never be able to address because there's nothing in the .dats that indicates when one item blocks two slots.Code:{main="Terra's Staff",sub=empty}
2) midaction() and pet_midaction() - The accuracy of these improved dramatically in the last few pushes, but they will *never* be perfect and you will need to design your user files with that in mind. For instance, if you initiate a BP and run over 30' from your avatar's target, you will not see the damage/result in the chat log or the battle animation and thus will not get a pet_aftercast() call. Because you do not get a pet_aftercast() call, pet_midaction() will still return true because the action was initiated and not completed. Similarly, if you (or your pet) start using a WS and get Stunned, Terrored, etc. and don't get a resulting chat log message about the interruption, you will not reset midaction (or pet_midaction()).
There's nothing I can do to react to data that I don't get. User files simply need to be designed to deal with it. Currently I have a 20 second deletion limit on the command registry, so actions that you attempt are deleted after 20 seconds and will no longer affect midaction() or pet_midaction(). This, along with special case handling (like when a monster dies), is about the best that I can do.
On a more positive note, event registration works pretty well now from within GearSwap files. There's still the unregister_event crash bug, but it occurs much less frequently than it used to.
@Johnblaze: Thanks. Fixed and pushed.