Organizer!
Organizer!
i found if i manually put away any etched memorys, eschlixers and copper vouchers it loads pretty good. but if there in my inv its a luacore crash
Sylph.Tbd said: »
i found if i manually put away any etched memorys, eschlixers and copper vouchers it loads pretty good. but if there in my inv its a luacore crash
That's actually very helpful! Thanks :)
Fenrir.Montaeg said: »
Here's the organizer log. I only have 50 mog safe spaces so maybe that's the problem. I know you mentioned that earlier, but I didn't look at the log till now XD.
Yeah, <80 slots will break the version that's out there. I have a fix locally.
Lakshmi.Rooks said: »
Bahamut.Alkk said: »
@Rooks
I have two gearswap files that always seem to crash my lua when I run organizer. Others work flawlessly though.
Do you need any info or should I just sit tight?
I have two gearswap files that always seem to crash my lua when I run organizer. Others work flawlessly though.
Do you need any info or should I just sit tight?
Gimme! More data, the better. Thanks!
Okay, what do I need to do though, send you the two files?
Bahamut.Alkk said: »
Lakshmi.Rooks said: »
Bahamut.Alkk said: »
@Rooks
I have two gearswap files that always seem to crash my lua when I run organizer. Others work flawlessly though.
Do you need any info or should I just sit tight?
I have two gearswap files that always seem to crash my lua when I run organizer. Others work flawlessly though.
Do you need any info or should I just sit tight?
Gimme! More data, the better. Thanks!
Okay, what do I need to do though, send you the two files?
Pastebin, Gist, paste it into a PM, whatever is most convenient for you.
v2015.05.26 was just submitted for review. Changes include:
- fixing of the "my config got blanked" bug
- fixes for <80 inventories (and I resisted the urge to just print a message calling you a scrub)
- a couple of fixes around valid pull/dump locations that may fix some crashes, though I'm not optimistic about that
I don't know how much time I'll have to work on things during the week, but I do read all bug reports and crash logs, so please keep sending them in.
Thanks!
- fixing of the "my config got blanked" bug
- fixes for <80 inventories (and I resisted the urge to just print a message calling you a scrub)
- a couple of fixes around valid pull/dump locations that may fix some crashes, though I'm not optimistic about that
I don't know how much time I'll have to work on things during the week, but I do read all bug reports and crash logs, so please keep sending them in.
Thanks!
[+]
Hey again.
After the update, I tried using //gs org, and now it's stuck at Organizer: Starting...
I tried deleting the settings file as you recommended, and it still doesn't work. It seem to mess up other lua commands I try to use as well. It's like it's stuck or something.
After the update, I tried using //gs org, and now it's stuck at Organizer: Starting...
I tried deleting the settings file as you recommended, and it still doesn't work. It seem to mess up other lua commands I try to use as well. It's like it's stuck or something.
That's a LuaCore crash. And that update isn't out yet - I included the version number in my announcement so you'd know when it was available.
I don't have direct access to the Addon repository; the process is:
- I write code, attempt to test it
- drink heavily
- finish testing code
- submit a pull request
- someone merges that to the development windower
- someone merges that to the live windower when it doesn't blow up the world
We're at step 4 right now, for that patch. Response times vary because people are busy, etc, but they always get pushed through so it's just a matter of time. If you really want the true bleeding edge of development, my development version can be found here though I don't recommend pulling files from there unless you know what you're doing, and with the knowledge that a Windower update will overwrite them.
I don't have direct access to the Addon repository; the process is:
- I write code, attempt to test it
- drink heavily
- finish testing code
- submit a pull request
- someone merges that to the development windower
- someone merges that to the live windower when it doesn't blow up the world
We're at step 4 right now, for that patch. Response times vary because people are busy, etc, but they always get pushed through so it's just a matter of time. If you really want the true bleeding edge of development, my development version can be found here though I don't recommend pulling files from there unless you know what you're doing, and with the knowledge that a Windower update will overwrite them.
[+]
Lmao, thanks a lot bud. I'm not gonna mess with the files, but thanks for giving me the opportunity to do it on my own. :-)
Edit: Actually. Nevermind! I'll try it out! x)
Edit 2: Thanks a lot bud. It works! ^.^
Edit: Actually. Nevermind! I'll try it out! x)
Edit 2: Thanks a lot bud. It works! ^.^
[+]
I need to add some more/better debugging logs, because I am completely unable to reproduce crashes at this point, and yet they keep happening.
Lakshmi.Rooks said: »
Asura.Cly said: »
Lakshmi.Rooks said: »
Asura.Cly said: »
Hey Guys, got a little error when I logged in. I have reinstalled windower with no success. Organizer Log in Error.
Is there anything I can do? Thanks :)
Is there anything I can do? Thanks :)
That looks like it's missing something in settings. Can I see your settings.xml?
Code
<?xml version="1.1" ?>
<settings>
<global>
</global>
</settings>There was a bug in the config handling (which is fixed in my dev copy, with a couple of other things I want to push out today). Delete your settings.xml and reload organizer and it'll work. (Don't delete any of your freeze files, those are fine)
where would i change the delay for getting /putting away items
In Windower/addons/organizer/data/settings.xml, there is an <item_delay>0</item_delay> - change that to 1 for one second, etc
Organizer v2015.05.26 is live.
Asura.Xsabrewolfx said: »
Latest update has some errors, apparently I had to delete the libs files in the different inventory files because I was getting random pulls of over 250+ gear pieces and none had anything to do with my current job's gear when using //gs o. Once I deleted it seems it all calmed down for now.
O.o
What?
I can finally reproduce one of the crash bugs; I have it and a fix for a config bug locally, finishing testing then shipping it off (likely later this morning).
Lakshmi.Rooks said: »
I need to add some more/better debugging logs, because I am completely unable to reproduce crashes at this point, and yet they keep happening.
It seems to be locking up on certain items/gear from what I can tell. I tried to run it 2 more times after logging back in and my only output was:
Organizer: Starting...
Organizer: Getting!
Organizer: Got 0 item(s), and failed getting 0 item(s)
Organizer: Skipping item: (Linkpearl) because it is an equipped linkshell.
Organizer: Skipping item: (Dark Ring) because it is currently equipped.
All bags, except Safe1, at this point had room to stash and all are 80. Both times caused a luacore crash. Meant to add that in to my previous post yesterday but got tied up. I got it to complete the operation by manually stashing items. If you could get it to spit out a log for planned operations before it actually starts the pick/stash operation, you can at least use that as a comparison to see at what point it is locking-up.
edit:Curious what this line means? I assume it means items already in inventory.
Organizer: Cannot move the item (Moonshade Earring). It has already been annihilated.
[+]
So, one of the problems of the debug logs as they were is that the only log after the fact, it didn't tell enough about what it was trying to do. I've added more logging, and changed how it logs. Now it will drop everything into a data/organizer-debug.log, giving you an easy file to send me when things go wrong.
I've fixed at least two crash conditions in this version, so hopefully that's the last of it.
[Edit: I just realized you were asking me to do exactly this, I mis-read your post. There actually WAS code that displayed intentions but it wasn't ever getting called, which is not very useful]
I've fixed at least two crash conditions in this version, so hopefully that's the last of it.
[Edit: I just realized you were asking me to do exactly this, I mis-read your post. There actually WAS code that displayed intentions but it wasn't ever getting called, which is not very useful]
Shiva.Wickedness said: »
edit:Curious what this line means? I assume it means items already in inventory.
Organizer: Cannot move the item (Moonshade Earring). It has already been annihilated.
Organizer: Cannot move the item (Moonshade Earring). It has already been annihilated.
That's an old message! Have you updated recently? I changed that a while ago to say "moved", since that's what it's actually doing. The 'annihilated' refers to its internal table, never the item itself.
Organizer v2015.05.29 has been submitted. Changes include:
- A fix for a config handling bug if you had non-default configs
- Two cases of infinite loops are resolved
- The debug logging has changed significantly, and you have one easy file to send me when things go wrong
- A fix for a config handling bug if you had non-default configs
- Two cases of infinite loops are resolved
- The debug logging has changed significantly, and you have one easy file to send me when things go wrong
[+]
Sylph.Tbd said: »
i found if i manually put away any etched memorys, eschlixers and copper vouchers it loads pretty good. but if there in my inv its a luacore crash
There were a couple of crash conditions around stackable items. It's fixed in the dev version (Arcon just pushed it).
Lakshmi.Rooks said: »
That's an old message! Have you updated recently? I changed that a while ago to say "moved", since that's what it's actually doing. The 'annihilated' refers to its internal table, never the item itself.
Yes that was from a previous version's log. Meant to ask what it was before.
Edit: Another question I had. For the organizer_items = {} set, do the tags matter? Need to make a set to collect all my goldsmith items(mats/fewell/crystals/etc.) and just haven't gotten around to it until now. I was originally planning on just making a dummy GS file with a bunch of dummysets for these items, but if it will read anything as the tags with no limit on the length on that set, it will simplify things. Same with condensing all nonsense items(chapters/seals/etc.)that eventually end up all over the place taking up space.
Shiva.Wickedness said: »
Lakshmi.Rooks said: »
That's an old message! Have you updated recently? I changed that a while ago to say "moved", since that's what it's actually doing. The 'annihilated' refers to its internal table, never the item itself.
Yes that was from a previous version's log. Meant to ask what it was before.
Byrth used "annihilated" as the language for something being removed from the internal structure representing a bag. The first time I saw that in the code I wtf'd pretty hard. I changed the message because it was scaring the crap out of people and rightly so.
Shiva.Wickedness said: »
Edit: Another question I had. For the organizer_items = {} set, do the tags matter? Need to make a set to collect all my goldsmith items(mats/fewell/crystals/etc.) and just haven't gotten around to it until now. I was originally planning on just making a dummy GS file with a bunch of dummysets for these items, but if it will read anything as the tags with no limit on the length on that set, it will simplify things.
The only restriction is that they have to be unique, or the last one you assign will win. I don't know what the maximum length of a string is in lua but I'm pretty sure you won't hit it.
Lakshmi.Rooks said: »
Byrth used "annihilated" as the language for something being removed from the internal structure representing a bag. The first time I saw that in the code I wtf'd pretty hard. I changed the message because it was scaring the crap out of people and rightly so.
lol it sent me into a panic at first until I realized I still had the items. Spit that message out on my 99 ghorn and 99dharp.
Thanks for the info on organizer_items = {}. Creating a file for it now.
Edit:Can't get it to work. I converted my brd.lua(actually just deleted all the gear sets) file into gold.lua with only two gear sets. An idle and an organizer_items={} set. For some reason when I enter //gs load gold.lua, then //gs org, it's still picking items based on the job.lua of whichever job I'm on. Changing jobs then doing //gs load gold.lua results in the same of picking items for that job. The console verifies the gold.lua is loaded. I was able to get it to work properly by renaming gold.lua to PUP.lua(because screw pup) and changing to pup.
Came back home from work, Organizer not working anymore for me.
It empties my inventory just fine, but it stops there. Doesn't get items from my repositories and doesn't put em into my inventory.
Here's my current config, not changed from yesterday (used to work perfectly)
Here's the verbose log I get:
It empties my inventory just fine, but it stops there. Doesn't get items from my repositories and doesn't put em into my inventory.
Here's my current config, not changed from yesterday (used to work perfectly)
Here's the verbose log I get:
All FFXI content and images © 2002-2024 SQUARE ENIX CO., LTD. FINAL
FANTASY is a registered trademark of Square Enix Co., Ltd.