GearSwap - Re-enabled

GearSwap works via outgoing action packet injection, and in the last patch SE increased the outgoing action packet size quite a bit (16 bytes -> 28 bytes). Until we figure out what the last 12 bytes are doing, it probably shouldn't be used.

No one is currently in danger because Windower API problems prevented it from injecting packets, but when that is fixed it would become an issue.

As such, I've disabled it by uploading a version that has an unload command on line 131 of gearswap.lua. If you remove that command, it should load and will probably work after the Windower API problems are fixed, but you're risking your account by sending out bad packets. When the new packet structure is understood, someone will upload another version that doesn't have the unload command and everything will go back to working.

Completely understandable and I'm glad you guys take these pre-cautions rather than adopt a "*** it, it'll probably be ok" attitude.

That said an extended period of time without Gearswap is probably going to kill me! ^^

Thanks for the heads up.

So many people in my LSs left paralyzed by no gearswap it seems. Time to take a vacations boys!

Ha I think Avalon was moaning at us for not wanting to do anything with no Gearswap.

That was what I was doing yesterday.

Maybe I'm not as good as some who use it, but at times like this I'm glad I have 8553 macros that, while slightly cumbersome, work well enough to get the job done.

100 gearsets really isn't enough if you play a lot of jobs...

No lua makes me gimp as hell lol
Time to learn macros ingame till its solved :)
Thanks in advance for all the work you all put in those windower programs.

Sweet, I have an excuse to put my BRD on vacation.

I suppose I could always level a new job, want to get that level sync RoE done.

Thanks a lot for the heads up - and for all the work you all do!

Thanks for the info, I can't help but think reasons like this is why spellcast should of never been fully discontinued. Back to windower scripts, assuming those still work.

Spellcast wasn't really discontinued, I'm sure you'd be welcome to try and keep up with it's breaking, but the windower guys got sick of having to fix plugins constantly breaking when there has been a replacement for quite a while.

Besides, as far as I'm aware, there's basically one active windower developer right now.

Spellcast was discontinued because it was impossible to keep maintained.

In addition to the usual complications with plugins vs addons (have to recompile them, have to fix them individually vs just fixing luacore), Spellcast in particular was a pain to deal with.

I've taken a couple of pokes at giving Gearswap a Spellcast style mode, where it would just spit out /equip lines instead of doing packet injection, but it's not really built for that and it was never a real concern previously. If this ends up being an ongoing issue maybe I'll dust that off and get it to work.

If anyone is playing with windower but without GearSwap, I'd appreciate it if you could load this addon:
https://www.dropbox.com/s/a7lweujwsxgogzp/action_monitor.lua?dl=0

I logged in to a spare account and played around with the new action packet, but I find the new bytes are always zeroed out. This addon will display a message if the new bytes are used or an unfamiliar action packet is sent. If you see a message, please report the full message to me and tell me what you were doing when you saw it.


As far as I can tell, they just put a bunch of zeros at the end of the old action packet. The live version is still stubbed off with the unload statement (probably for another day, assuming no reports from this addon), but the dev repository just has a longer action packet now.

For the rest of the Windower API problems, Arcon figured out how the target struct changed and fixed it in hook but didn't have time to rebuild plugins. Those will probably be fixed before tonight.

[Edit: Fixed your link, B. --Rooks]

Call me a moron, but do I need to put this someplace special in my Windower folder for it to work properly? I just want to make sure I'm doing it right so I can pass on accurate info (if any).

The addon system wants a directory and lua named appropriately - for this, you'd make an action_monitor directory in addons, and put that lua in there.

Windower\addons\action_monitor\action_monitor.lua

The link is giving me a 404.

Fixed.

Edit: Nvm durped

I only fixed Byrth's original post. Use that one, not any of the quoted ones.

Thank you sir, I'll put it in there and post if anything funky pops up.

Edit: I'll also let my LS know of the project and direct them here.

I don't know if this is important, but everytime I try to talk to a gobbie box goblin I get the following lua error:

action_monitor: Lua runtime error: .../Windower4//addons/action_monitor/action_monitor.lua:22: attempt to call method 'hex' (a nil value)

Same message pops up in the console from the goblin in West Adoulin and the one in Lower Jeuno.

I'll look into it. Thanks!

We used it as an excuse to cancel last night, but it was largely just because we were all pretty beat so we figured...eh. Why not take it easy?

Hmm... I talked to the goblin in West Adoulin and didn't get a message.

After seeing the light, I don't want to live on a planet where Gearswap doesn't work.

Goodbye cruel world.

Got a runtime on line 22 when calling method 'hex' with actionmonitor when interacting with the home point in Kamihr; waypoint by MH in West Adoulin; Gobbie in South Sando; Survival Book in North Sando.

Ok, it's not just the gobbie box goblins... It seems most NPCs I talk to in West Adoulin are prompting this error. I went around the corner and talked to everyone in mummers coalition, the only ones that DO NOT trigger the error are the Task Delegator, the Civil Registrar, and Peladi Shalmohr who triggers a small CS for me for some quest I ignored. All other mummer NPCs trigger the hex called on a nil value error, as well as the porter moogle, the nearby food merchant, the linkshell NPCs, and the delivery specialist.

Edit: Pagnelle the elf just outside mummers doesn't cause the error, nor does the waypoint. Charutata the Tarutaru outside does cause the error. It seems like "Quest NPCs" are not causing it.

I just about read all that but seriously, use paragraphs.