You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm aware of the warning but I noticed the itemid list during scrubs won't pull item past adaman bullets 19803.
The default list only goes up to that as well.
But looking at the FFXIAH site and the SQLs for LSB, this should be going up to almost 30000. So items are missing it looks like.
Example: 28314 Aetosaur gear, can't get it in the CSV, unless we manually do that, but so much is missing it would take soooo long lol.
It seems like this may be on purpose because alot of items right after those bullets are rare/ex but those stop eventually & the IDs goes back to sellable items
Is there a command we can use to force the scrubber to go up to that #? Or is it already supposed to do that and I'm messing something up here. Maybe I got an old item.csv somehow, or it's an issue?
Thanks!
The text was updated successfully, but these errors were encountered:
I have the same problem, i would like to pull prices for all the new items, but doesn't know how to do it without manually adding them one by one into the .csv, which is somewhat really painful.
If someone have an idea, i will be really interested.
Hey Adam.
I'm aware of the warning but I noticed the itemid list during scrubs won't pull item past adaman bullets 19803.
The default list only goes up to that as well.
But looking at the FFXIAH site and the SQLs for LSB, this should be going up to almost 30000. So items are missing it looks like.
Example: 28314 Aetosaur gear, can't get it in the CSV, unless we manually do that, but so much is missing it would take soooo long lol.
It seems like this may be on purpose because alot of items right after those bullets are rare/ex but those stop eventually & the IDs goes back to sellable items
Is there a command we can use to force the scrubber to go up to that #? Or is it already supposed to do that and I'm messing something up here. Maybe I got an old item.csv somehow, or it's an issue?
Thanks!
The text was updated successfully, but these errors were encountered: