from what i've read the script see's that it "can't buy that item" and assumes on error, and will buy at 1 till its gone, as soon as it moves on to the next stack it will be at 200 again.
What Nuprecon explained , any error while attempting to buy raws and it has to assume there is a problem in buying that stack size , so it moves into buying singles until the next entry is reached.
oh is that what causes it.
<?xml version='1.0' encoding='UTF-8'?>
<!-- Generated by LavishSettings v2 -->
<InnerSpaceSettings>
<Setting Name="Bristled Leather Backpack">1</Setting>
</InnerSpaceSettings>In this instance it was yes , I'm guessing you moved the mouse away from the broker window just as it was starting the buy stack routine.
This is now live in the current ISXEQ2 build. Myprices queues will be broken until this gets updated.
Version 0.13m
uploaded the update to the SVN with server name added.
Just tested the routine , name only and no name but tier and level , both types worked fine...
<Set Name="General">
<Setting Name="SetUnlistedPrices">TRUE</Setting>
<Setting Name="MatchLowPrice">TRUE</Setting>
<Setting Name="IncreasePrice">FALSE</Setting>
<Setting Name="IgnoreCopper">TRUE</Setting>
<Setting Name="BuyItems">TRUE</Setting>
<Setting Name="SellItems">FALSE</Setting>
<Setting Name="ScanSellNonStop">FALSE</Setting>
<Setting Name="PauseTimer">5</Setting>
<Setting Name="Craft">TRUE</Setting>
<Setting Name="Logging">FALSE</Setting>
<Setting Name="MerchantMatch">TRUE</Setting>
<Setting Name="box1">TRUE</Setting>
<Setting Name="box2">TRUE</Setting>
<Setting Name="Natural">FALSE</Setting>
<Setting Name="ActualPrice">TRUE</Setting>
<Setting Name="TakeCoin">TRUE</Setting>
<Setting Name="box3">TRUE</Setting>
<Setting Name="box6">TRUE</Setting>
<Setting Name="box5">TRUE</Setting>
<Setting Name="box4">TRUE</Setting>
</Set> <Set Name="Buy">
<Set Name="NoName S: 1 E: 49 T : 4">
<Setting Name="BuyNumber">0</Setting>
<Setting Name="BuyPrice">880.000000</Setting>
<Setting Name="Harvest">FALSE</Setting>
<Setting Name="BuyNameOnly">FALSE</Setting>
<Setting Name="StartLevel">1</Setting>
<Setting Name="EndLevel">10</Setting>
<Setting Name="Tier">4</Setting>
<Setting Name="BuyAttuneOnly">TRUE</Setting>
</Set>
<Set Name="totem of the chameleon">
<Setting Name="BuyNumber">0</Setting>
<Setting Name="BuyPrice">120.000000</Setting>
<Setting Name="Harvest">FALSE</Setting>
<Setting Name="Buynameonly">TRUE</Setting>
</Set>
</Set>I can make it default to box 1 if no box is selected in the lists , unfortunately the last update removed the old setting from each item so no way to recover that.
Thats wierd , the startup code looks for an entity with a guild ID of 'Guild World Market Broker' and then targets it , what were you targetting before you ran the script?
Yes , the text doesn't change once you get that 'Saving information' , it's finished saving , just a minor cosmetic thing which I WILL get round to fixing.
Yes , thats a pain and a bug with LavishGUI code , I've re-added the box textentry box in the next version to make setting the Primary box a bit easier again , I'll be sending a bug report to Lax about that.
Yes , thats normal for the script , even though the boxes don't exist , it won't actually try and place anything in a box that is non-existant.
The change I did to make it try the guild broker first will get around that now anyway.
Fixed so it's in the right place
1. Ah , ok..I'll check that one....must find a char with no collections to test , unfortunately I've been playing a loooooong time and completed most collections 8)
<grammar-spelling-apostrophe_police>
Any plans on saving that set into an xml? And its not clearing until you log out, which means each character uses the same set. When I log in my next toon he wont auto buy.
Yes , I'm not sure of any way around that....unless they still show as uncollected unless both collections have been completed...I'm fairly sure they still show as uncollected and that's what the script checks for first.
I think its acceptable just to run the script a few times personally. It may take a few hours, but thats what movies and going out to dinner with your *gasp* girlfriend is for =)
I've now got the script waiting till it flags that the examine window was opened before continuing , hopefully that will help with lag.
No.
Thats been there a while now.
Click on an item in the item list and look at the broker window , it does a broker search for each item clicked on , it's sorted by lowest price on top.
I could have sworn the whole undercutting thing was answered in the previous post quite clearly. Posting again with a reworded request for the same thing is NOT the way to a developer's heart. At this point, you're lucky I'm not the maintainer of this script, or I would have flamed you right off these forums and possibly even cost Amadeus your subscription.mycroft said:
Yep , currently it's part of the option to place shinies you have already collected , I'll see if I can stop that happening unless you are actually using the place items option.
I haven't added a prefared box for collections , currently the script will place items in the box with the most space (usually starting with box 6 if there are many with the same amount of space) , then move onto the next box with the most free space.
I've added the option , just need to test it for a while before doing the release , it 'should' notice that error and skip the box , I'll check that portion of the code.
