Treasury Problems With Handling Multiple Character

I've realized that trying to get all your boxes to write to a single file simultaneously is a bad idea, so I've stopped trying to do //send all tr drop add [item name]

But now I'm running into problems where even when Treasury is unloaded on all but 1 character, it still misbehaves. I'll do "//tr drop add global [item]" and it will just add the item to the single character's part of the settings.xml instead of the global part. I'll do "//tr drop add [item]" and it will add the item to a completely seperate character's part of the file when that character doesn't even have tr loaded. In-game it always drops the item correctly, its just the writing to the settings file bit that seems to be getting jumbled up.

I haven't modified the addon at all I just use the one windower comes with it says version 1.2.1.1. Any help is appreciated

Not sure it matters: I use;

//send @all //treasury drop add dart

Not had any issues with it adding the item to 3 character files. Not sure if the slight difference in how it is written matters at all?

Go into the treasury/settings.xml file and remove all the extra crap it wrote wrongly.

Put all the items you want dropped into the global section, reload one by one character.

treasury has a //tr add all command, use that. Do not use send @all.

Side note - XML is very circa 2009. Stop using it ffs.

I modified Treasury for my own multi-box needs (to pass on non-lot-list items when another char lots, e.g.) but even with it I still only update the settings file manually as the add-on does not do well with multiple chars. Likely, it would need to be updated to load separate character-specific settings files but I cannot be bothered to do it.

do you mean this (from the readme)


I tried your //tr add all command and it didn't work, and the global command mentioned in the readme is behaving incorrectly for me. only thing that seems to work now is going on my main and doing "//treasury save"
from the readme:
which just wipes all my other per-character drop lists and moves the main character's drop list to global which isn't ideal but better than nothing I guess

Global, yes, not all. //tr add global <item>

The per character stuff doesn't work. Don't use it.

I'm not having any issues with the functions. Do you know if your settings are connected the demon known as "Microsoft One Drive"?

exorcised that demon long ago. I used to think treasury was working as normal before too but doing this vw campaign recently i noticed everytime I relog my drop lists get wiped. whatever list the other boxes keep in memory ie. when logged in is correct so if you just never log out you'd assume it's working correctly but it's not getting saved to the settings file so they forget what they're supposed to drop on next relog/addon reload (atleast for me)

//tr drop add global [item] command still misbehaving no matter if treasury is reloaded on all characters, unloaded on all then reloaded on 1 etc. even if all the per-character settings in the file are deleted and only the global section left. It seems like it just iterates through each open character and adds the item to that character's specific (rather than global) drop list, but each character only keeps the settings.xml in memory from when they first loaded Treasury, so they just save over each others additions and when you check the settings file its just the last character to go that has that item in their drop list

only functioning workflow for me rn is to just do tr drop add [item] --> saves to that specific character's part of the settings file --> tr save --> moves that to global and deletes the specific character's part again --> reload treasury on all characters.

I'll avoid using the per-character settings from now on as per Dodik's suggestion

Personally I've always avoided the tr functions all together and just edited the global section directly in the settings file.

Also had an alias to reload treasury on each character with a delay in between or reloading would screw up the settings file again.

<moans about xml again>

Same. My best use case has been a macro for exiting Einherjar post victory.

/con send @party //tr drop add Glowing Lamp
/wait 3
/con send @party //tr drop remove Glowing Lamp