Windower 4 - Discussion and Support

[Sechs]

Byrth I think I remember one of your first works when the Luacore was released, was an addon tracking Steps on the current mob.
Have you ever thought about developing a new, updated version of it? Would be nice to have a box on screen somewhere displaying current steps, time until expire etc.

[Trumpy]

It was called Daze. when ever i tried it it did nothing that i could tell.

[Byrthnoth]

It wasn't very well made, so when it broke due to some lib change and I went back to look at it I got disgusted and removed it from the repository rather than put in the amount of work that would have been required to fix it. Now that I'm a little better at Lua (the first version of Send was my Hello World, I sent Hello World >.>) it would probably be trivial to re-make it. I'll look in to it in a week or two.

[Sechs]

Thanks byrth, went back on dnc lately and really felt the need of such an add on.

On a side note guys, is the th tracker add on still maintained? Does it check th from the chat or from packets?

[Arcon]

hey guys not sure if this is an gear swap Error but its where i first noticed the Problem, i logged in Earlier and was playing fine then i changed jobs and all of the sudden was getting error messages from gear swap. one.
gearswap: lua runtime error: gearswap/helper_function.lua:680 "spell" is not definided for number, was one of the error messages, i got i was getting alot of different one for some reason? When i looked at the location they were coming from they were all .lua's from the gearswap file so i though there was maybe an problem with gear swap. But when i unloaded gearswap i got error form roll tracker and scoreboard too also the last few days when ive been zoning i have not been able to see poepl when we enter dleve unitll i //reload luacore, im not sure if this i related but i though i shoud mention it
i have trtied to /re download winnower also and got the latest verions but still getting the same Errors but only on start up it says im missing the init.txt file
I really hope u guys can help me out with im off work till the 3rd and was looking forward to having a good go of this and i was until this happened
thank You in advance for any Answers

This was due to a libs update that broke GearSwap. The libs have been reverted for now until GS is adjusted, i.e. it should be "fixed".

[Byrthnoth]

GearSwap has been adjusted and the libs change that was problematic is now on -dev again. Please let us know if you -dev-ers find any bugs.

Also, I have an addon called Organizer that I have been playing with for a while. It's an all-bags version of gearcollector that reads Lua files and does packet-based swapping. Here is an example of it changing all my BLM gear out for DNC gear:


It needs a lot of usability adjustments and I'll probably need to add a config file and all the associated handling, but it's somewhere in the pipeline.

Disclaimer: I started making it in June and look at the project for an hour or two about once every 3 months.

[Sechs]

/boner

[semco]

I logged into the game this morning, after I got the new hook, I noticed as windower was loading I had an error that showed up in the console.

"Luacore encountered a fatal error and must be terminated. Error: access violation in add item method."

[Byrthnoth]

Rerun launcher. You might have to log out and back in. We accidentally pushed a Hook version that was ahead of the live LuaCore version. It is fixed now.

[Bukadan]

is that organizer thing going to make changing jobs as quick as those timestamps show? because thats probably enough to make me want to play the game more often lol

[Byrthnoth]

Yeah, that was the time it took to move 136 items.

Also, some lib changes went live. Please report nil errors here: https://github.com/Windower/Lua/issues

[Bukadan]

thats incredible byrth, lol. jesus christ.

[Sechs]

Maybe just a coincidence... logged today and it downloaded some new plugins/luacore/hook I think.
I crashed 3 times.

Way of crashing:
1) Screen stops for 1-2 seconds
2) Black screen for 1-2 seconds
3) I'm back to Windows with a POL Crash error.

Happened 3 times today after not having a crash in FFXI for quite a long time.

[Raithen]

I can only assume this is a Windower thing as nothing else has changed.
Logged in two days ago fine, FFXI worked normally. Tried to log in today and Windower took a minute to update (I did not look to see what was downloaded) before POL started. Log in and go to start FFXI, POL gives Error 022: FFXI not installed.

Haven't touched any files. What might have caused this?

[Byrthnoth]

It's not a windower thing. Your antivirus program ate your ffxi.dll.
http://forum.square-enix.com/ffxi/th...-%28Nov.-17%29

[Raithen]

Thanks. Apparently my antivirus software, even post-update, is behind the times. It still wanted to quarantine FFXI.dll even after I updated to the current version and would still quarantine after adding exceptions.

Restored FFXI.dll after temporarily turning off antivirus and still get Error 022 though.

[Kuishen]

What the fuck happened to the Timers plugin? It's keeping track of each individual Step on mobs now so when I have 5 steps on mobs I have 5 fucking countdown bars. It's cool that it now keeps track of debuffs on mobs but jesus christ do something about Steps.

[Byrthnoth]

Somewhat related. Someone asked me to remake Daze and here it is:
https://www.dropbox.com/s/3nd142m9940r92q/daze.lua?dl=0

Put it in a windower/addons/daze folder and load it up with //lua l daze

I'll do an official release for it after I get some comments back.

Example:


There we go, the picture with padding.

[Trumpy]

not sure why all the complaints when timers keeps tracks of debuffs. I like that feature, but there is a whitelist/blacklist feature in the settings file I believe where you can tell it not to track them maybe.

@Byrthnoth is that last number a timer? the 5.9 16.0 and 26.7 ? I dont have active sub right now so i cant just load it up and see.

[Byrthnoth]

It's the time until the step wears off on that mob. It tracks mobs by their index. If a mob regens more than 9% between status update packets, it resets the dazes on it. Pretty foolproof. Hope it actually works. =p