Zeina Posted December 21, 2017 Share Posted December 21, 2017 I was generate new token, but bot dont accept it help me its keep saying : warn: Invalid backpack.tf token: THIS SOFTWARE IS DEPRECATED AND WE DO NOT PROVIDE SUPPORT FOR IT. The backpack.tf automatic client has severe vulnerabilities and can be exploited, resulting in you losing items. If you know what you are doing and are managing a fork of this software that does not have the vulnerabilities of the official client, add a POST field of i_understand_the_risks set to true. Link to comment Share on other sites More sharing options...
zol Posted December 21, 2017 Share Posted December 21, 2017 1 Link to comment Share on other sites More sharing options...
Zeina Posted December 21, 2017 Share Posted December 21, 2017 7 hours ago, Zeina said: I was generate new token, but bot dont accept it help me its keep saying : warn: Invalid backpack.tf token: THIS SOFTWARE IS DEPRECATED AND WE DO NOT PROVIDE SUPPORT FOR IT. The backpack.tf automatic client has severe vulnerabilities and can be exploited, resulting in you losing items. If you know what you are doing and are managing a fork of this software that does not have the vulnerabilities of the official client, add a POST field of i_understand_the_risks set to true. no one help ??? Link to comment Share on other sites More sharing options...
JRichi Posted December 22, 2017 Share Posted December 22, 2017 17 hours ago, Zeina said: no one help ??? On page 77 of this discussion there is the fix for that. However, automatic isn't working at all even if you fix that part. Slavyanin 1 Link to comment Share on other sites More sharing options...
Walter_ Posted December 23, 2017 Share Posted December 23, 2017 This situation is comparable to destroying a bridge before the people have crossed it. Link to comment Share on other sites More sharing options...
Poot Posted December 23, 2017 Share Posted December 23, 2017 On 12/18/2017 at 7:39 AM, Versal said: You need add this in file app/backpacktf.js after metod:"alive" i_understand_the_risks: "true", somebody know how to generate 24 digits token, cuz automatic does not work with token like this 2s3GN5X0QtlguJgBjIqRHhnWzFsMcSltdK4JFtgiWOE= like in my file Thanks man. fixed the issue. btw what os are you running? Link to comment Share on other sites More sharing options...
Don Martin Posted December 24, 2017 Share Posted December 24, 2017 Unfortunately after this fix it all began to work very slowly = ( Link to comment Share on other sites More sharing options...
Walter_ Posted December 28, 2017 Share Posted December 28, 2017 Thanks Versal for the fix :D. I am a python programmer myself and didn't have to get myself involved in java for now due to that fix. Link to comment Share on other sites More sharing options...
Mr. Sympathy Posted December 29, 2017 Share Posted December 29, 2017 Hello, anyone have a fix for australiums glitch for last version of automatic? Link to comment Share on other sites More sharing options...
Cipis Posted December 30, 2017 Share Posted December 30, 2017 So curently im runing my bot on my old macbook pro late 2011 with newest software awilable. My problem is that i dont have the "Lightning Button" Im using the latest automatic proggram and everything seems to go smoothly but the lighting button still dosent show up. Please help me, i can add more details if needed. Link to comment Share on other sites More sharing options...
Cipis Posted December 30, 2017 Share Posted December 30, 2017 On 2017.12.19. at 9:38 PM, Suͫpͤrͫeͤme said: the fix isn't working for me with sell orders. Also does the lightning icon not show anymore? Same problem here Link to comment Share on other sites More sharing options...
clumba Posted December 30, 2017 Share Posted December 30, 2017 I can see lightning icon at some users: But not with automatic client. How can i know, what bots supported with such icon? Link to comment Share on other sites More sharing options...
LAZy Posted December 31, 2017 Share Posted December 31, 2017 so is it only bots made before the latest update which haven't generated a new token that are able to send heartbeats? Link to comment Share on other sites More sharing options...
Starbucks® Posted December 31, 2017 Share Posted December 31, 2017 It shows up on mine now not sure what i did differently Link to comment Share on other sites More sharing options...
Starbucks® Posted January 1, 2018 Share Posted January 1, 2018 https://backpack.tf/api/IAutomatic/IHeartBeat?i_understand_the_risks=true&method=alive&version=1.3.3&steamid=mysteamid&token=my44characterstoken&buy_orders=true use this with a auto refresh extension on your browser to get the lightning. You might need to replace mysteamid with your steam id and my44characterstoken with your token Slavyanin 1 Link to comment Share on other sites More sharing options...
A Delicious Cashew Posted January 1, 2018 Share Posted January 1, 2018 The way I fixed buy order support, autobumping, and showing the lightning bolt for my bot required these steps: - In the heartbeat function in backpacktf.js, change the path to automatic/v1/pulse. Set buy_orders to "true" in the parameters. Get rid of the version, steamID, and method parameters as well. Change to these two highlighted lines - In the postJSON function in utils.js, return axios.post() instead of axios.get(). Also change to these two highlighted lines. IAutomatic/IHeartbeat is basically dead, so don't use that anymore Slavyanin and JRichi 2 Link to comment Share on other sites More sharing options...
JRichi Posted January 2, 2018 Share Posted January 2, 2018 On 1/1/2018 at 3:22 AM, A Delicious Cashew said: The way I fixed buy order support, autobumping, and showing the lightning bolt for my bot required these steps: - In the heartbeat function in backpacktf.js, change the path to automatic/v1/pulse. Set buy_orders to "true" in the parameters. Get rid of the version, steamID, and method parameters as well. Change to these two highlighted lines - In the postJSON function in utils.js, return axios.post() instead of axios.get(). Also change to these two highlighted lines. IAutomatic/IHeartbeat is basically dead, so don't use that anymore Good job! I didn't know about that api I modified your code a bit to handle better the eventuality of a wrong token provided. also I created a new function called postJSON1 because I don't know if postJSON is used somewhere else in the code. (it's probably fine to just modify the postJSON) Slavyanin 1 Link to comment Share on other sites More sharing options...
A Delicious Cashew Posted January 3, 2018 Share Posted January 3, 2018 5 hours ago, JRichi said: also I created a new function called postJSON1 because I don't know if postJSON is used somewhere else in the code. (it's probably fine to just modify the postJSON) Yeah, that's probably smarter. It's been working perfectly fine so far, so I'm guessing it doesn't matter elsewhere Link to comment Share on other sites More sharing options...
Bank Bot Bob trade.tf Posted January 3, 2018 Share Posted January 3, 2018 On 01/01/2018 at 12:22 PM, A Delicious Cashew said: The way I fixed buy order support, autobumping, and showing the lightning bolt for my bot required these steps: - In the heartbeat function in backpacktf.js, change the path to automatic/v1/pulse. Set buy_orders to "true" in the parameters. Get rid of the version, steamID, and method parameters as well. Change to these two highlighted lines - In the postJSON function in utils.js, return axios.post() instead of axios.get(). Also change to these two highlighted lines. IAutomatic/IHeartbeat is basically dead, so don't use that anymore I did all these steps but it shows this: https://gyazo.com/a0541588bb9f8f6d444f0cfd54dc7259 Link to comment Share on other sites More sharing options...
A Delicious Cashew Posted January 3, 2018 Share Posted January 3, 2018 1 minute ago, Bank Bot Bob trade.tf said: I did all these steps but it shows this: https://gyazo.com/a0541588bb9f8f6d444f0cfd54dc7259 Make sure the code matches with the screenshots. If it's still causing issues, I'm not sure, I'd have to look at it as there's likely something else wrong Link to comment Share on other sites More sharing options...
Bank Bot Bob trade.tf Posted January 3, 2018 Share Posted January 3, 2018 25 minutes ago, A Delicious Cashew said: Make sure the code matches with the screenshots. If it's still causing issues, I'm not sure, I'd have to look at it as there's likely something else wrong https://gyazo.com/c9764d6b2d5923fe091910e83e186370 https://gyazo.com/46581776aa0c20492d7aac7cd7f257f7 Is this correct? If so would generating a new token affect this? Link to comment Share on other sites More sharing options...
A Delicious Cashew Posted January 3, 2018 Share Posted January 3, 2018 15 minutes ago, Bank Bot Bob trade.tf said: https://gyazo.com/c9764d6b2d5923fe091910e83e186370 https://gyazo.com/46581776aa0c20492d7aac7cd7f257f7 Is this correct? If so would generating a new token affect this? I haven't tried anything with the new tokens, and I would be surprised if that was the issue, but I guess it's possible. Maybe try JRichi's code since it looks like he got it to work with the long tokens Link to comment Share on other sites More sharing options...
JRichi Posted January 3, 2018 Share Posted January 3, 2018 8 hours ago, Bank Bot Bob trade.tf said: https://gyazo.com/c9764d6b2d5923fe091910e83e186370 https://gyazo.com/46581776aa0c20492d7aac7cd7f257f7 Is this correct? If so would generating a new token affect this? The Cloudflare message happens because you provided a wrong token once and now it keep saying that. Try my code and it should ask you to enter a new token. Link to comment Share on other sites More sharing options...
SmokE Posted January 3, 2018 Share Posted January 3, 2018 Can someone please upload the working version of bp.tf automatic with all these fixes on GitHub or something; C I am bad with codes and fixing shit Link to comment Share on other sites More sharing options...
SmokE Posted January 3, 2018 Share Posted January 3, 2018 16 hours ago, Bank Bot Bob trade.tf said: I did all these steps but it shows this: https://gyazo.com/a0541588bb9f8f6d444f0cfd54dc7259 I am getting this same error as well !! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now