location_type=interior... means "inside the house"?
recentSales()... includes auctions!!! Thanks!!
Posted 5 months ago by
UXRoot

|
Permalink
in recentSDBs()... we have the sdb_tsid twice... and we don't know in which streetId is placed that sdb. please tell me this is not by design...
Posted 5 months ago by
UXRoot

|
Permalink
another question, in auctions methods, the "id" was the "PlayerId-Number"... here recentSales() has only the "Number". is that number "unique"? I though that the auction id had the PlayerId too, because it wasn't unique.
TIA
Posted 5 months ago by
UXRoot

|
Permalink
"location_type=interior" - yes, inside a house. types are "interior, exterior, tower", although exterior wont show up here.
"in recentSDBs()... we have the sdb_tsid twice" - once as the key and once in the object. yeah. it'll always be equal
"we don't know in which streetId is placed that sdb" - i've added that now (along with the owner TSID)
"is that number "unique"?" this is a different ID, unrelated to the auction ID. it is unique within that API method.
(Staff reply)
Posted 5 months ago by
Bees!

|
Permalink
in economySales()... can we have at least the "date_sold" datetime for auctions so we can calculate how long the item was in the AH? ..... please? :)
note: I assume this is not possible in SDBs... or it is?
TIA
Posted 5 months ago by
UXRoot

|
Permalink
BTW... the "since" parameter makes the whole difference... now everything is fast!!
Posted 5 months ago by
UXRoot

|
Permalink
and... sorry... but one more thing, what about adding the ownerTsid of the auction and sdb sale on each economySales() item?
Thanks :)
Posted 5 months ago by
UXRoot

|
Permalink
Not planning to add that information (buyer or seller TSID) just yet - keeping the full sales information semi-anonymized
(Staff reply)
Posted 5 months ago by
Bees!

|
Permalink
I've renamed `date_create` to `date_sold` since that's what it actually is. I've also changed the type on the date, quantity and cost fields to numbers, since it was dumb that they weren't.
(Staff reply)
Posted 5 months ago by
Bees!

|
Permalink
Ok. if the field is really date_sold... it is ok that we use param "since" to filter for that field? it is "since" param, comparing to field date_sold too?
note: if we could have date_created too... that would be really good :)
again... thanks!
Posted 5 months ago by
UXRoot

|
Permalink
Yes, `since` is comparing against the same field as `date_sold`.
We're not tracking the date the item was put on sale, since it rarely makes sense for SDBs. If an SDB had 100 stock, then had 50 purchased, then was restocked to 80, then had 70 purchased, what was the start time of each purchase?
(Staff reply)
Posted 5 months ago by
Bees!

|
Permalink
sorry... I mean only on Auctions... I would like to start using only the new api, and stop (in steps) to use the old one (for auctions).
Posted 5 months ago by
UXRoot

|
Permalink
+1 Most definitely Thank you! I am going to give my try at a Web app.
Posted 5 months ago by
Arthur Dent-Ur

|
Permalink
It seems like there are a few bugs. One thing that I have found is that if you remove all items from an SDB that has a price set, the API doesn't tell us about it. Here are the steps to recreate this problem:
1. Shove some items into an SDB
2. Set the price for the item
3. ....wait a minute or two for an update.....
4. Remove all items from the SDB
5. ....wait a minute or two for an update.....
6. No update that the items were removed: item is still on my app with full quantity and price
Posted 5 months ago by
Malero

|
Permalink
yes, I saw the same problem:
Test Cases:
* "stop selling" button: reported OK
* "stop selling" button, then remove everything from SDB, let the SDB on the wall: reported OK
* remove everything from SDB (the owner), and let the SDB on the wall: NOT reported on the API!
* remove everything from SDB (other player, not the owner), and let the SDB on the wall: reported OK
* remove everything from SDB, remove the SDB from the wall and put it again on the wall: NOT reported
* the price is $999777, I then set a new price "0" cero... reports ok. it reports that the new price is 0, with qty=0.
the SDB I used is sdbTsid: BHV2208095V27BA
so, yes, the problem is when the "owner" removes everything and it has a price.
Posted 5 months ago by
UXRoot

|
Permalink
Thanks for the report - I'll get that fixed.
(Staff reply)
Posted 5 months ago by
Bees!

|
Permalink
How about getting some item_defs like in auctions.list?
Posted 5 months ago by
scragz

|
Permalink
@scragz +1
That would be nice. I've come access a few items that I don't have in my database.
Thank you for providing the Glitch API for us developers to use! I have been having a lot of fun with it. =)
Posted 5 months ago by
Malero

|
Permalink
After a few tests this morning, I have found that the bug that UXRoot and I submitted has not been fixed. Can we get an update on the status of this bug, please?
Posted 4 months ago by
Malero

|
Permalink
so... the bug is fixed! (just checked all cases)
Posted 4 months ago by
UXRoot

|
Permalink
The economy methods can now optionally return item defs
(Staff reply)
Posted 88 days ago by
Bees!

|
Permalink