Windower 4 - Discussion and Support

[grevenilvec75]

//load luacore


then you'll have to reload your lua addons, but idr where that script is.

it'll be something like //exec addons/addons.txt (that commands is wrong, i'm sure. just find the file somewhere which has all the lua load comands in it and //exec that)

Is there currently any efficient way to two box across two PCs using widower 4? I'm still using old Windower and a version of RCM I added a socket layer to years ago. It's just getting annoying since <stal> and <stpt> seem to be messed up in old windower (always targets the caster). I could probably update RCM to use the new windowerhelper, but I can't really find a lot of documentation around the new helper API.

I understand that next release may/will have network aware RPC, but is there something people are using, or some way to get things to work until then?

look into the lua addon named "send". It's what I use. Can't remember if it works with <stal> though. I'm thinking it doesnt.

[Talis]

//load luacore

look into the lua addon named "send". It's what I use. Can't remember if it works with <stal> though. I'm thinking it doesnt.

Maybe I'm wrong, but I didn't think that send had support for instances running on different PCs (looked into adding a socket layer to it actually, is there a way to add luasocket support to the lua implementation?).

[Teryu]

Awesome, thanks for the help guys.

[Trumpy]

I tried plugin manager but there was something that i didnt like about it. it was a long time ago so i dont really remember. it might have been at least at the time that u couldnt set it up for two accounts or soemthing. i really dont remember but in the end autoexcet did what i wanted so i jsut said fuck it and used it. Before u posted the 7 step way to reload plugins and stuff i had actually that day loaded /exec autoload/autoload.txt and it worked.

New thing has anyone noticed on occasion when zoning that blinkmenot will kinda reload it self? i am not sure if that is what it is doin but it prints its setting out in the console jsut like it does when u load it. It might be certain zones. i am pretty sure from moghouse to west adoulin was one that has been doing it and from choco circuit to port jueno i think did it. Not that its a problem just it never did this before.

[Khajit]

Just crashed twice in a row when unloading statustimer. Gonna retest once im not in a situation where testing will fuck me up ingame to see if i was right about unloading it causing a crash or if i twas a coincidence.

Tpparty also caused a crash at Tojil
and on the second tojil encountered a fatal error and must be terminated. error access violation in incoming chunk method
updateresources
tpparty
pettpgear collector
attainment logged and spellcast all individually crashed and got that error message in the course of a single tojil just now.

[Cheeri]

Looking for a link to the new ver. of windowhelper.dll the one at the start of the thread no longer works thank you.

[Byrthnoth]

I'm not sure if this is helpful, but here is the github repository for Windowerhelper: https://github.com/Windower/Helper

[Malithar]

Been trying to run Windower scripts to skill up Summoning Magic skill. I've done this with other skills without issue, however with Smn, sometimes the game is convinced I don't have a pet out (thus I have no pet abilities) so the Release JA returns an error of "A command error has occured." However, on the next line of the script, FF returns with "already has a pet" due to...already having a pet out, and thus I get stuck in a loop of errors returned by the game.

Is there anything I could add to the script to remedy this? I can't really track down what causes it, sometimes it happens after a couple of minutes of the script, sometimes after a few hours.

Edit: In order to fix the issue, I have to target my pet, than open the pet commands menu. After that, if flashes like I've just changed pets, but it updates with the list of pet abilities. Doing this then allows the script to continue, or for me to manually do whatever.

[Sechs]

Seen the situation pretty asleep over the last weeks. Anybody mind doing a quick recap about what's going on behind the curtains for Windower 4 and its upgrades? Last I heard you guys were still trying to debug a seriously annoying bug in the new 4.1 version

[Arcon]

Seen the situation pretty asleep over the last weeks. Anybody mind doing a quick recap about what's going on behind the curtains for Windower 4 and its upgrades? Last I heard you guys were still trying to debug a seriously annoying bug in the new 4.1 version

tl;dr version: Same as a month ago.

Longer version:

Bugs left to fix before 4.1 release:
- Memory leak
=> Status: No idea what's causing it yet, but not motivated to investigate since it might be fixed with the coroutines branch, see below
- Send/IPC
=> Status: No idea what's causing it. Debug log has been added, but hasn't revealed much so far

Features to be added, not necessarily tied to 4.1:
- Proper event handler using Lua coroutines, thus enabling reliable sleeping in events
=> Status: Mostly done, but at least one weird bug left to fix and some events remain to be added

Status of the Windower team:
- Largely involved with FFXIV at this point
- The part that isn't is drowning in RL work
- Most addon devs either busy or quiet

In general, not much at all has changed in weeks, no idea when it's gonna pick up again. Personally I'm gonna start working more on issues again this week, even more in two weeks time when my horrible work schedule will finally ease up, but I can't speak for the rest of the Windower team, so I can't give any promises. If someone thinks they're up to the task and wants to help out (C/C++ or good general programming knowledge required, having made a SpellCast XML is not enough), come on IRC and say hi to aureus

[Byrthnoth]

I'm getting demolished at work, but I recently made an issue tracker for my addons: https://github.com/Byrth/Lua/issues

I am trying to address those issues now, as well as release Battlemod v3. When this stuff gets to the general non-experimental Windower base is going to depend on when v4.1 is released. There are also some problems that I can't solve by myself.

[Sechs]

I wasn't trying to bash anybody btw, and had a hunch FFXIV had something to do with it all
Was just curious and wanted to know what was goin around.
Nice to see people are still working on the project ^^


P.S.
With FFXIV you meant people being busy as in playing it? Or trying to release some cool stuff for it?

[Byrthnoth]

Okay, so I released two things for the experimental client today:

1) Shortcuts v0.9 - For a while Shortcuts had a bug where it would fail to create the right target when you didn't provide one but your current target was valid for the spell. Like, if you were targeting a non-party member and used /haste it would cast Haste on you instead of the party member. That problem is now fixed. AFAIK and possibly barring <st> weirdness, shortcuts is pretty much done.

2) GearSwap v0.703 - A few things in this:
* It now checks to see whether your spell target dies while you're casting and resets midaction if it does. There are still a few more action-freeze cases like this out there (like zoning while casting), but this was the last big one.
* It now has case insensitive data tables. So player.ID is the same as player.id. buffactive.pRoTeCT is the same as buffactive.protect, etc.
* The windower data structure is now available for .lua users. It was at least partially available before, but now it's a little bit cleaner. windower.unregister_event(id) causes desktop crashes, but that's just because it's broken at the moment.
* I made some changes to the require function that I forgot to test until just now. Hopefully they work!
* There is now an "export" command that will dump your current set or entire inventory into a GearSwap .lua or Spellcast .xml file. The command is:

//gs export
//gs export inventory
//gs export xml
//gs export inventory xml

It defaults to exporting the currently equipped gear in .lua format unless one of the options is listed. All files are exported to windower/addons/lua/gearswap/data/export/

I made an issues tracker here: https://github.com/Byrth/Lua/issues
Please let me know if you find anything else wrong, and I am still thinking about how to address change_spell() with st targets.

[Arcon]

I wasn't trying to bash anybody btw, [..]

Didn't take it that way

With FFXIV you meant people being busy as in playing it? Or trying to release some cool stuff for it?

Playing only. The idea of doing something Windowery for XIV was discussed a few times, but it doesn't seem necessary at this point. It would have some uses, but not nearly as many as for XI, because XIV barely has a fraction of XI's problems. And for the uses it does have it's quite a large undertaking and would require a lot of collaborative effort, so it doesn't seem worth it right now, although it's still being discussed occasionally, so who knows what the future will hold.

[Sechs]

It would also be useless considering that in the "near" future everybody will be able to develop addons using their tools.

[Darkmagi]

Well I'd imagine their addons will still be relatively limited compared to what someone can do using unsanctioned methods. I'm sure someone will pick it up if nothing else.

[Arcon]

Well I'd imagine their addons will still be relatively limited compared to what someone can do using unsanctioned methods. I'm sure someone will pick it up if nothing else.

This. They've also announced a scripting scheme for XI a while ago, and aside from the fact that it probably won't hit within the next decade given their track record with scheduled updates, I very much doubt it'll allow for more than manipulating the new UI. I could be wrong, but I hardly see them adding packet injection/modification, for example, which you can do with most other third party tools, and I think it'll be very similar for XIV, so there would definitely still be a use. It's merely the effort vs. reward ratio that doesn't look very attractive right now.

[Sechs]

Well I'd imagine their addons will still be relatively limited compared to what someone can do using unsanctioned methods. I'm sure someone will pick it up if nothing else.

Yes but because of them offering the possibility to release addons (as limited as they will be, we'll see that in due time) also means that they will be less "tolerant" towards other third party developed tools compareable to what Windower & relatives have been for FFXI. a scenario where SE showed a lot of tolerance over the year, a lot of "I pretend you don't exist so I'm not forced to take measures agaisnt you", if you get what I mean.

[Byrthnoth]

Gearswap 0.704 is out
I basically just re-worked how the require statement is handled and renamed it to "include" because require has a specific definition in Lua and the function I'm providing no longer fits that. This was necessary so that I could clean up the user environment when people changed jobs. Otherwise files that were required would always be available. Apart from that, I fixed a minor bug in the //gs equip command and Arcon made some changes to windower.unregister_event that allowed me to debug its implementation in the gearswap user environment. Now that works too (whenever the newest version of LuaCore gets pushed).



v4.1 has these problems remaining:
* IPC is broken sometimes (but not others). - This needs to be fixed before release.
* LuaCore has a memory leak to the tune of 1MB/minute with a pretty normal set of addons loaded. (battlemod, plugin_manager, send, respond, answeringmachine, eval, shortcuts, enternity, chars, ffocolor)

There is actually a third version of LuaCore out there that may not leak, but it crashes occasionally on event_addon_command(). It has mostly-implemented coroutines, too, so we could kill two birds with one stone and skip a development cycle if we just finished that one.

Edit: Just checked the coroutines LuaCore without event_addon_command and it does not leak, so that might be the path to pick.

[Foldypaws]

Post version update, I'm getting "luacore encountered a fatal error and must be terminated. Error: Access violation in HandleCommand method."

Also getting things about Critical Error: Failed to find "IsInCombat" when I try to reload it.