Jump to content
McKay Development

All Activity

This stream auto-updates

  1. Today
  2. Hi guys! What is the best way for me to check if a user (i have their steamid64) has activated their mobile steam guard authenticator and no longer have a 15 days trade probation? for now, im using this method: Bot.tradeOfferManager.createOffer(tradeURL).getUserDetails((err, me, them) => { const error = err?.message?.toLocaleLowerCase(); if (error) console.log(`ERROR in checkForErrors for user: ${userID}: ${error}`); if (error?.includes('inventory privacy')) return resolve('private_inventory'); if (error?.includes('is no longer valid')) return resolve('invalid_trade_url'); if (!options.checkTradeBan) return resolve(''); if (them?.escrowDays > 0) return resolve('steam_guard_not_activated'); if (them?.probation) return resolve('trade_ban'); return resolve(''); }); by the way, I 100% know this is a bad code. but i don't know how else should i do this. (and also, it breaks from time to time and i have to hotfix it. it's broken now and I just want to do it properly, once and for all)
  3. my bad, I've changed log level of newOffer to debug, and didn't check debug logs
  4. Hi! Right now, the contextid is coming as `16` instead of `2`, as it used to be before. Because of this, the `cache_expiration` field is not being set. Looking at the code here, can we just add a similar check for `contextid == 16` to set the cache_expiration as well? Or is there a better way to handle this with the new contextid? Thanks!
  5. Yesterday
  6. There's no reason it wouldn't, a counter-offer is a new trade offer like any other.
  7. After cs2 trade hold update my bot stopped receiving "newOffer" event for counteroffers
  8. the trade offer is not updated during the rollback, only trade. Thus, GetTradeStatus with tradeid from GetTradeOffer returns the correct status 12
  9. Am I trippin or steam added new fields to GetTradeOffer API? eresult: 1 delay_settlement: true
  10. Internal behavior changes when logging on with EAuthTokenPlatFormType.MobileApp Updated reported app version from 3.0.0 to 3.10.3 Updated reported device name from Galaxy S22 to Galaxy S25 Added origin=SteamMobile query string parameter to match official app behavior Full Changelog: v1.9.3...v1.9.4 View on GitHub
  11. As you've figured out, the actual trade offer stays in the Accepted state, but the underlying trade gets rolled back. steam-tradeoffer-manager doesn't poll GetTradeHistory at all right now, so adding support for detecting these rolled back trades would incur additional requests. I'm still working on thinking of the best way to go about this, but for now I suggest you do your own GetTradeHistory polling.
  12. https://github.com/DoctorMcKay/node-steamcommunity/releases/tag/v3.49.0 As far as I can tell, clicking that button in the popup (which is what acknowledgeTradeProtection() does) is all that's needed, and it only needs to be done once per account. If you've already clicked the button on the account(s) you use to trade, you shouldn't need to do anything more.
  13. Added acknowledgeTradeProtection() method Full Changelog: v3.48.8...v3.49.0 View on GitHub
  14. Last week
  15. Thanks, I wasnt aware there was a different contextid for trade protected items.
  16. The sentOfferChanged event does not emit when an offer is rolled back. Please confirm if this is already known, or if this can be addressed in an update. Thanks.
  17. Yes is a bit difficult to use GetTradeHistory, but for the moment this is the only solution, until steam will solve the endpoint. I just implemented GetTradeHistory to track also the rolled back trades (state == 12) and is working. You just have to get the trade history and find that one with your trade id, and you will get the state and the items also.
  18. yep, if you will find other endpoint that will give info about trades on hold let us all know. GetTradeHistory isn't convenient for our use case
  19. I checked also that API endpoint you mention and still same state id, 3 (Completed). Now I thing that is something from steam, they didnt update properly the system, or they didnt update this endpoint. I think that node-steam-tradeoffer-manager module is also using this endpoint, so may not be a problem from module, but from steam. As a conclusion, the trade state is updated only on trade history API: https://api.steampowered.com/IEconService/GetTradeHistory/v1
  20. Thanks doc. Your'e a life saver as always. For now, as a temporary fix, I just logged into the bot using the steam client (or a web browser) and accepted the pop up manually in trade history page. It's working fine for now. currently waiting for the new update. ❤️
  21. Probably a GC limitation. You should wait until the item modified event is emitted after adding or removing an item before moving on to the next one.
  22. This is not unexpected. It was always just happenstance that this method worked via steam-user; it uses a method not used by any official Steam app. You should use node-steamcommunity instead, which uses the official method.
  23. I'm traveling right now. I'll be able to push out an update in the next couple days.
  24. could you check same trade using this api endpoint? I assume steam failed to update it. https://api.steampowered.com/IEconService/GetTradeOffer/v1/
  25. I'm trying to set up two-factor authentication using steam-user, but I keep running into an issue where the enableTwoFactor function consistently fails with result code 2. As a result, I'm not receiving any Activation code via email. I'm logging in with a username and password using steam-user, and once the webSession event is emitted, I start the two-factor setup process. There is currently no Steam Guard enabled on the account, and Steam Mail Guard is also disabled. I assume that if Steam Mail Guard were enabled, it would make sense that the process doesn't work—since Mail Guard is a form of Steam Guard. Is that correct? Interestingly, when I follow the same steps using Steam Desktop Authenticator, everything works as expected. As some other users have already pointed out, could there be an issue with the enableTwoFactor function itself? Or is the problem possibly on my end, in my code? Thanks!
  26. After the new steam update with the ability to reverse trades, I tested the revert system on a trade, but by calling manager.getOffer(), I am getting the same state id 3 (Completed), instead 12 (Rolled Back). This is the history of my trades using https://api.steampowered.com/IEconService/GetTradeHistory/v1 API. You can see how the original trade has been rolled back with status 12, and the other one is the rollback trade, which gave me back the item. And this is the response from manager.getOffer(). The state didnt change and is still 3. Any solutions for this problem? Is there comming a fix for this steam update for node-steam-tradeoffer-manager module?
  1. Load more activity
×
×
  • Create New...