Quote from: natminer on July 01, 2017, 02:03:40 PM

I have a question about this (well about pools in general), in terms of the "worker name". Does it matter if I have more than 1 rig using the exact same "Worker Name" (does the pool care? Does it only matter if one rig has much less hashpower than the other as the amount of shares might not be optimized on one of the rigs then)

It probably depends on the pool you are connecting to, but I don't think this matters in general. I have had two rigs pointed at a pool, and either I didn't set everything up correctly in my BAT file or in AM... and the pool will show the combined hashrate of both rigs as a single "worker". One pool even called the combined worker "noname".

Quote

When I define a pool I can give an optional "Add to worker name" to append, but if I use the same pool (or same Managed Template) with more than 1 rig I don't see a way to set different worker names.

This has to be defined at the Manage Miner config page in the Options. Below the dropdown where you select a pre-defined pool, you have the option to append a rig name to the worker name. You define the worker name in the Pool settings. The default behavior is to send the "worker" name as the name you put in the pool, then a period, then the rig name. So in the case of Suprnova, if you register with them, your "username" that you login becomes your worker name. But the most important part with Supernova is you have to go to their Worker page and manually create the worker names before you point your rigs at them. Your "username" from Supernova then is the first part of your worker name and you put this in the Pool settings. Then you append the rig name in the Manage Miner config page. Ultimately your "worker name" becomes

username.rigname

In the Pool's dashboards you will see each rig individually like this. Some pools you have to experiment with a little bit, and sometimes the mining software you have to experiment with a little bit in the command line settings you can apply to each Managed Miner. For instance, there is one pool that I can't figure out how to do worker names with their convoluted scheme with AM at all. So in the pool definition page, I only put the URL and nothing else. Then in each Managed Miner in the Command Line options, I specify the settings like so:

--port 3043 --user {wallet address I was mining to here} --pass x

So, as you can see AM is very, very flexible. You can either define your settings in all the proper GUI fields in the Pool definitions and Managed Miners as intended, or you can put the actual BAT commands that you would normally use otherwise in each Managed Miner's config screen. You can even setup templates if you swap around to different pools a lot so that you preserve all those precious commands that you worked hard to cultivate. Or just have a Notepad file full of them and manually copy/paste when you switch pools or settings. Templates are much faster though.

Quote

One idea I had is maybe if you configure the "Add to worker name" to take an optional variable that maybe would take the name of the miner or something (like %minername%), so those who want to use it can do that to have each rig append a different name to the worker name.

That already exists in the Managed Miner options, unless I'm not understanding your request.