I'm about to create an extension that 'bypasses' Unexpected response (400), is it worth it?

[Eureka]

Yes. I have an idea how to fix it on your side and it should work.
Its a bit difficult task, but I think I can try.

[Sir Spoon The Second]

there is already a fix

 

[Eureka]

10 minutes ago, Sir Spoon The Second said:

there is already a fix

 

Sadly, but its a poor way to update your inventory.
I have an idea how to make it update at the first try.

Edit: I mean if it works it works.

[Flaim]

nice

[RussellSproutz]

Respect

[shadyfan]

I think the best server-side fix for that would be to implement Abstract's python script into backpack.tf. When someone opens an inventory and it fails to load, it would get added to a queue and that python script would just try to refresh it every 3 mins, until it's refreshed. The only thing that is currently missing in the script is being able to check if the inventory is private.

 

But these errors occur so rarely now compared to what it was like a year ago. It used to sometimes take days to be able to refresh your inventory, even by using the above-mentioned script.

[Eureka]

8 hours ago, shadyfan said:

I think the best server-side fix for that would be to implement Abstract's python script into backpack.tf. When someone opens an inventory and it fails to load, it would get added to a queue and that python script would just try to refresh it every 3 mins, until it's refreshed. The only thing that is currently missing in the script is being able to check if the inventory is private.

 

But these errors occur so rarely now compared to what it was like a year ago. It used to sometimes take days to be able to refresh your inventory, even by using the above-mentioned script.

I actually like how it works, but implementing this feature into backpack.tf could make it slower.

[Eureka]

9 hours ago, RussellSproutz said:

Respect

I appreciate that

[RussellSproutz]

4 hours ago, Eureka said:

I appreciate that

No problem!

[Eureka]

A little sneak peek