Hello Patrike,

Below are some bug reports and some suggestions:

Bugs:

1) When you copy/paste an address into a field (Nicehash, Hashrefinery, Zpool, etc) it is possible to accidentally paste an invisible new line at the end of the address.
This new line will remain there screwing up your miner's launch and without you knowing why it is failing. Took me about 2 and half hours of debugging to find the culprit.
The program should sanitize that information and remove any non alphanumeric characters.

2) It is impossible to add some algorithms. I mean, you can add them and it seems like they are added but they never appear in the "Online Services" tab (the one with the Revenue/Profit list, not the one inside Options).

Try it yourself... attempt to add "yescrypt" and make it appear for Hashrefinery. I have tried on several computers and the program simply refuses to show it even after following all the steps, adding the algorithm, adding it to the mining software and then adding it to the pool in Online Services (the one inside Options).


Suggestions:

1) Create a rule capable of detecting the algorithm being launched.

2) Allow for "Factor" to be defined for custom pools just like we are able to do with the default ones.

3) The benchmarking tool needs some love. Instead of being forced to benchmark each card one by one, it should benchmark the whole lot together.
I know Nicehash used to do it individually (later improved in the legacy miner) but at least they would launch separate miners depending on the profitability of each card.
Right now your program is not designed to do anything like that, so I don't see any reason why benchmarking has to done one card at a time.
As an example, look at what MultipoolMiner does. Simple, efficient, grouped benchmark.

4) After the previous one, you would want to include several versions of the same miner software (like you do now with two versions of ccminer and sgminer).
Once the benchmarking is handled with all cards as a single group, it should do every algorithm with every compatible miner and keep the best performer.

5) Allow us to define different levels of "-dcri" for Claymore Ethminer. Right now this is impossible to do, even if you try to work around it by creating another algorithm with a new name.
Either allow us to add dual mining algorithms or modify the current one so it is capable of having several fields for several values of "-dcri".

Thanks for reading! Here's hoping to see the bugs squished soon.