rsnrdk

You are right, thats actually doesn`t matter) Thank you for your answers!

About multiple outbound offers, I will cap it at one live offer per bot at a time: 1) bot sends trade offer 2) bot listens to sentOfferChanged event 3a) if user accepts: save data, mark bot as free, move to next offer in queue 3b) if user doesn`t respond within 5 min: bot cancels the offer, marks itself free, moves on (p.s. offers are queued via BullMQ, with concurrency capped at 1 per bot) About replacing asset_id by hash. Good point. I just realised that we can do such operation: The hash is: pattern_id + float + class_id. Where class_id is the unique category of item, so we don`t confuse two different items that have the same float+pattern_id (a very small chance but whatever). And that kind of functionality doesn`t require comparison before and after every trade which won`t get us ratelimited. But here is one little problem: In Counter Strike, there are items that don`t have pattern_id and float values... and i`m talking about vanilla-knifes. So, for normal items the logic above is great fast and reliable, and for vanilla items i don`t know another better solution than compairing inventories before and after trade. Correct me if I`m wrong and thank you for answering.

As I said, in theory, my idea should work. You are absolutely right about the possibility of gaps caused by failed inventory updates. To prevent this, I will save every user`s operation in the database and retry every failed or pending operation until the bot can successfully compare the inventory before and after the trade. Only after the current operation is fully verified will the bot proceed to the next trade. P.S. I hope this will work not only in theeeooryy lol

I tried to visualize my view of how It should work, and actually i cant see any problems except of getting ratelimited due to such operations. Correct me if Im wrong and ask questions Is something is not clear.

Why not? When I save the bot`s inventory data before trade, then after the trade i just compare old inventory with the new one. No matter how much items user will send to my bot. I mean the logic should work like this: Inventory assets before trade: 1111 2222 3333 Inventory assets after trade: 1111 2222 3333 4444 5555 the new one are 4444 and 5555. So the comparison, in theory, should work on DB level. Currently I did not implement this feature due to a large amount of work on other aspects of my project and Im also trying to figure out how to correctly implement this kind of feature. I will be very gratefull if you can clarify how to do this

Thank you very much!😉

Thank you for the answer! You mean I should compare my Bot`s inventory before and after the trade and then exctract the new items by asset_ids that i didn`t have before trade right?

Hi everyone! Any updates on this topic? Currently the issue is still not fixed, maybe someone figured out another way to reliably determine who sent which item without new asset_id? I tried to check by Item Certificate but it also changes after trade between users.