-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Long-term suggestions and ideas for AutoRetainer #52
Comments
Add a new filter check for warning gear: This way if a sub reaches farming level and we miss it, we can notice this in our lists of 100s of subs. |
The ability for the Venture Planner to import a Teamcraft gathering list and generate plans from it in the same way Artisan can import the craft list. |
Notes for Inventory management:
|
A feature that can relist/update prices on marketboard listings while running AutoRetainer |
Market board stuff is actually outside of AutoRetainer scope |
level goal flag for submarines, say a sub reaches a predetemend level AR only finalelise the sub insted of resending it |
I would like to see the option to mass entrust shard/crystals/clusters into our retainers. This could be handy when we stock up for patches/expansions. We could even get it to set a certain threshold. Either dump all into retainers, or set a certain amount/threshold. |
As a follow-up to issue #62, I'd appreciate an automated solution for running AutoRetainer with multiple accounts on the same machine (multiboxing). The currently proposed solution with .bat files is somewhat clunky and appears not to work well with launching FFXIV through XIVLauncher, which I assume most people do. |
Maybe a feature to auto vendor certain items? |
AutoRetainer is currently not in active development, which means, mostly bugfixes are being implemented and new features are added slowly. In this list I attempt to gather feature requests from people for further implementation.
Note: requests in this list are not necessarily to be all implemented: they are added before consideration stage.
Please comment in this issue for a feature requests.
We do not guarantee to implement each and every feature request, however
The text was updated successfully, but these errors were encountered: