Skip to content
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

[Craft Queue] Max cost patron orders #805

Closed
ponwerb opened this issue Jan 29, 2025 · 1 comment · Fixed by #806
Closed

[Craft Queue] Max cost patron orders #805

ponwerb opened this issue Jan 29, 2025 · 1 comment · Fixed by #806
Assignees

Comments

@ponwerb
Copy link

ponwerb commented Jan 29, 2025

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Add a maximum cost option for patron orders in the crafting queue just like the "Knowledge point max cost"

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
I have tons of concentration alts and I am just trying to be as efficient as possible. This would speed up doing the patron orders a small bit.
Thank you!

@github-project-automation github-project-automation bot moved this to Backlog in CraftSim Jan 29, 2025
@avilene avilene linked a pull request Jan 30, 2025 that will close this issue
@ponwerb
Copy link
Author

ponwerb commented Jan 30, 2025

Hi, I just made these changes myself to test it out and I realized I explained it wrong. Instead of it using the "crafting cost" number I wanted it to use the "expected profit" number. So that I can filter out all patron orders that have expected profit below -50g for example. Sorry for bad explanation and thank you all for working on this wonderful addon!

@github-project-automation github-project-automation bot moved this from Backlog to Done in CraftSim Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants