-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bot Inventory Management #1637
Comments
I do not think this is within the scope of ASF |
@JustArchi Is it out of scope for ASF to expose steam inventory in api? |
@MrBurrBurr not necessarily, since ASF already has this functionality - if you decide it'd be good idea to add such feature, then each bot can expose its own inventory without issues. |
Sounds nice. What kind of information would that endpoint expose? Do you have an example? |
Pretty much https://steamcommunity.com/inventory/76561198006963719/753/6, plus maybe some additional data we already have from ASF parsing for easier comparison of steam items. |
Great, I would like that 👍 |
Checklist
Enhancement purpose
It is currently difficult to visualize and modify the inventory of bots, which makes it a challenge for users who operate multiple bots and need a quick overview or to adjust the inventories of their bots.
Solution
I propose the implementation of a new inventory management module within ASF-ui. This module would display a clear, tabulated view of each bot's inventory. Users could then be able to perform actions such as moving items between bots (similar to the loot or transfer commands) and unpacking booster packs (similarly to the unpack command).
Why currently available solutions are not sufficient?
The existing ASF-ui does not provide a dedicated interface for inventory management. Users have to use commands or manually log into each bot's account to view or manage their inventories. This can be very tedious and time-consuming.
Can you help us with this enhancement idea?
Somehow, I can test and offer feedback, but can't code
Additional info
No response
The text was updated successfully, but these errors were encountered: