darkcodelagsniper
Member
Quite often I use the maximizer, then say rude words when I realise I'd forgotten to set price back to "don't check" after a previous use. The list of potions is very large for quite a few modifiers, and it can take a good while to run through price checking every one of them.
There are two things I'd like to see to make maximizer behaviour friendlier with regard to price checking:
1) When aborting the maximization (e.g. by hammering the escape button and saying "NO NO NO NO") the price checks should also be aborted. Currently even if you abort the maximization and set price check to "don't check", every potion in the aborted maximize request is still price checked before the maximizer will do anything else.
2) Many user scripts that check item prices will only do so if the historical price is greater than N days old. This would be nice functionality for the maximizer.
There are two things I'd like to see to make maximizer behaviour friendlier with regard to price checking:
1) When aborting the maximization (e.g. by hammering the escape button and saying "NO NO NO NO") the price checks should also be aborted. Currently even if you abort the maximization and set price check to "don't check", every potion in the aborted maximize request is still price checked before the maximizer will do anything else.
2) Many user scripts that check item prices will only do so if the historical price is greater than N days old. This would be nice functionality for the maximizer.