Plugins Broken Via Version Update |
||
|
Plugins broken via Version Update
Lakshmi.Konvict said: » Question for anyone that can help, when using SuperWarp and I try to warp to Adoulin 2 it says im already at Adoulin 2 but im actually still at Adoulin 1 and not at 2. To warp to 2 need to manually do it. Does anyone know how to fix that? If you come on the windower's discord, there's a version of the addon that tentatively fixes this. A bit more testing is needed before it's pushed to the official repo, but you can be one of the testers! Not sure if its related to the latest version update, but certain items arent showing up in find on storage slips, and they seem to be recent ones:
ie: Have Lizard Fangs +1 on storage slip 22 do "find lizard f" no items found same for esotreic athame
[+]
likely the slips.lua that maps them was never updated, the client doesn't know what items are on the slips until someone manually adds it to the files
(well technically they're in the dialogue data for the moogle but that's not something that even moderately technical people can access easily)
[+]
Yeah, that seems to be the case. my slips.lua is dated Dec 13 2023.
https://github.com/Windower/Lua/blob/dev/addons/libs/slips.lua I copied the dev version over and it seems to be working as expected. Thanks Thorny Can someone fix the IME ?
Asura.Questaru said: » Can someone fix the IME ? FFXIKeys no longer works with Winrix, Rewardox and Habitox. If you use this addon, you will need to update the NPCs ID in the goblins.lua.
New IDs can be found in game or at https://github.com/DrakeFS/FFXIKeys/blob/master/data/goblins.lua 
Necro Bump Detected!
[130 days between previous and next post]Is there gonna be an update to the windower item resources since Sept update? I haven't been able to use Organizer since I got the new AA taru lockstyle gears a week or two ago since it just errors if there's newly released items in my inventory, or if there's a quick fix way I can edit it in myself so it works?
Moonlightagb said: » Is there gonna be an update to the windower item resources since Sept update? I haven't been able to use Organizer since I got the new AA taru lockstyle gears a week or two ago since it just errors if there's newly released items in my inventory, or if there's a quick fix way I can edit it in myself so it works? Just an educated guess, the IDs *might* be the following (based on the id in the urls from bg-wiki): Code 23846 23847 23848 23849 23850 item name should be: Code Cowardice Petasos Cowardice Coat Cowardice Gloves Cowardice Tonban Cowardice Sabots e.g res/items.lua Not sure how important all fields are but updating the ID and name is probably the bare minimum. Did not change the JP names since I don't know japanese. Code [23846] = {id=23846,en="Cowardice Petasos",ja="ＳＲペタソス+2",enl="cowardice petasos",jal="ＳＲペタソス+2",category="Armor",flags=63552,jobs=16,level=90,races=510,slots=16,stack=1,targets=0,type=5},
As for the file being updated, it was my impression it supposed to be each patch but it might be manual, not sure. If I were you, I'd ask on the Windower discord server. Resources were updated Sept 9th @ 10:37PM (PDT)
https://github.com/Windower/Resources/commit/3c5920a4e0d948c00e416f7c7268a147873b3843 If you are not seeing the correct file in your directory, your update may have failed and got locked up. To fix that you just need to delete the resource folder and the updates folder then launch windower.
[+]
Fenrir.Niflheim said: » Resources were updated Sept 9th @ 10:37PM (PDT) https://github.com/Windower/Resources/commit/3c5920a4e0d948c00e416f7c7268a147873b3843 If you are not seeing the correct file in your directory, your update may have failed and got locked up. To fix that you just need to delete the resource folder and the updates folder then launch windower. Good to know, my file also appeared to miss the entrypoint for this set. Thanks, Nif. Yeah we have been getting more people experiencing the error each update.
But we can't replicate it to find where our error handling is breaking down and letting the app think it successfully completed the download. At what point to the files get locked?
I often open one copy of POL at night to update FFXI files, sometimes I'm still awake and log that one char, sometimes its too late and I just go to sleep. The next morning I open windower, get the updated files, and log in the rest of my chars, and I've had issues with the resources updating. I had to pick the files manually off github. Carbuncle.Nynja said: » At what point to the files get locked? I often open one copy of POL at night to update FFXI files, sometimes I'm still awake and log that one char, sometimes its too late and I just go to sleep. The next morning I open windower, get the updated files, and log in the rest of my chars. By locked up I just mean that windower attempted a resource update, the updated fails but then windower logs it as successful so on any subsequent launch it won't try to update the file again. So you are "locked up" unable to get the update unless you manually delete the files that control the bad update data. By locked I meant files in use and unable to be overwritten, but I was just able to rename my res folder with everything running, so it wasnt an access issue. nvm
Hadn't heard this, was wondering myself when the resources would get updated.
Thought yall were just bein lazy. None of my pcs managed to get updated. I believe Pointwatch is broken after the update. Whenever I try to reload it, the error message is:
Code Pointwatch: Lua runtime error Windower4/addons/libs/files.lua:192: attempt to index local 'fh' (a nil value) Any ideas on how to fix it? There doesn't seem to be any update to pointwatch itself, and I already deleted and let the addon to recreate the settings.xml file but no luck. Thanks. Carbuncle.Elvaanmoq said: » Code Pointwatch: Lua runtime error Windower4/addons/libs/files.lua:192: attempt to index local 'fh' (a nil value) This error means that the addon failed to open the file it is trying to write to, which could be caused by the file not existing, the file being locked by another program, or not having permissions to write to the given file. The only file I can imagine the addon writing to is settings.xml which it can write (if I delete the file and reload the addon it re-creates it with the default values but still gives the error message on load).
Not sure what to do other than the good ol' "restart the computer" in case some process has a file open or something. Multiboxing if that provides some context, but of course restarted everything about an hour ago after the Windower resources update. My Pointwatch is still working perfectly.
He did something to his specifically. Everyone elses should be fine.
Asura.Eiryl said: » He did something to his specifically. Everyone elses should be fine. I didn't "do anything to mine specifically", if I did I would have specified here, but thank you for your not helpful assumption :) I mean yours is broken, no one elses.
Be it your fault or not, the problem is specific to you. No one else needs to worry about or comment that theirs is fine.
[+]
Yup, something got corrupted on the Windower update download this afternoon. Just deleted the "Windower4/updates/" folder and re-executed Windower, redownloaded a bunch of stuff and the addon is now working again. This is also the first time I see something similar, still worth reporting I guess.
Got a windower update this morning and Bidder, JAZero, Packetflow not working. I uninstalled all and reinstalled and still not working. Initially I had yellow exclamation pts next to each.
Also got an update this AM and now can't get past profile selection, non-windower launch (POL) works fine.
crash.log now has this when attempting to launch via windower: Code ´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´ [ 4.3.9067.14532 ] 2024-10-30 15:43:00.7112660 UTC --------------------------------------------------------------------- System.TimeoutException: The operation has timed out. at Launcher.Injector.Inject(SafeSystemHandle process, String hook, Settings settings, TimeSpan timeout) at Launcher.Injector.Launch(String hook, Profile profile, Boolean debug, TimeSpan timeout) at Launcher.Tasks.LaunchTask.Run() at Launcher.Tasks.Task.Run(Core core) at Launcher.Core.Run() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() ´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´´ Horovivi said: » Got a windower update this morning and Bidder, JAZero, Packetflow not working. I uninstalled all and reinstalled and still not working. Initially I had yellow exclamation pts next to each. Bidder is currently not working due to a version issue, if you delete the existing file and your update folder you can get the proper .dll file downloaded. You may need to reenter the code to access these plugins from the launcher. Quetzalcoatl.Mashengo said: » Also got an update this AM and now can't get past profile selection, non-windower launch (POL) works fine. You should come to our discord for support. Fenrir.Niflheim said: » Quetzalcoatl.Mashengo said: » Also got an update this AM and now can't get past profile selection, non-windower launch (POL) works fine. You should come to our discord for support. Fenrir.Niflheim said: » Horovivi said: » Got a windower update this morning and Bidder, JAZero, Packetflow not working. I uninstalled all and reinstalled and still not working. Initially I had yellow exclamation pts next to each. Bidder is currently not working due to a version issue, if you delete the existing file and your update folder you can get the proper .dll file downloaded. You may need to reenter the code to access these plugins from the launcher. Thanks for the help, got it working. |
||
|
All FFXI content and images © 2002-2024 SQUARE ENIX CO., LTD. FINAL
FANTASY is a registered trademark of Square Enix Co., Ltd.
|
||
