Template:Muling: Difference between revisions

Line 21:

| '''Reverse Bond if F2P''' || If your account is not members, it will try to receive a bond from the mule.

|-

| '''Mule Group ID''' || Group ID's allow refined control between what mule(s) a given account will connect to. This setting is used to restrict what accounts can connect to certain mules. If you configure a group ID in here, the account will only connect to a mule that has the same group ID. This is superior than configuring a port, as that forces you to have many profiles to have refined control over which mules the account(s) can connect to. The same as dynamic muling; if multiple mules have the same group ID, then the account will connect to its 'favourite' mule among the mules with the same group id. However, if no mules exist with the same group id, then it will not mule at all. This setting exists to give you refined control over what mules your accounts will connect to. Most people shouldn't use this setting, as dynamic muling should already be sufficient. For more information, here is some examples of how it works: if you have 10 rev accounts, and 2 mules. You want exactly 5 accounts to use 1 mule, and exactly 5 accounts to use another mule. You only need 2 profiles to make this happen, one profile can be running on group ID "a" and one profile on group id "b". Any accounts running on group id "a" will only mule with the mule that also has a group id of "a". As this uses dynamic muling, if you want to run 5 more accounts, you don't need to make a new profile; you can simply run another mule with the group id of "a" or "b", and more accounts on the respective group id. For example, you can run 10 accounts on grooup "a" and 5 accounts on group "b". If 2 mules are running on group "a", then each of the 10 accounts on group "a" will select their favourite mule among both mules running on group "a". In the event of a mule being banned, if another mule exists with the same group id, then the account will simply swap over to use ~~the other~~ mule in the group. This setting makes it easy to launch replacement mules, while restricting which accounts can interact with a specific mule.

| '''Mule Group ID''' || Group ID's allow refined control between what mule(s) a given account will connect to. This setting is used to restrict what accounts can connect to certain mules. If you configure a group ID in here, the account will only connect to a mule that has the same group ID. This is superior than configuring a port, as that forces you to have many profiles to have refined control over which mules the account(s) can connect to. The same as dynamic muling; if multiple mules have the same group ID, then the account will connect to its 'favourite' mule among the mules with the same group id. However, if no mules exist with the same group id, then it will not mule at all. This setting exists to give you refined control over what mules your accounts will connect to. Most people shouldn't use this setting, as dynamic muling should already be sufficient. For more information, here is some examples of how it works: if you have 10 rev accounts, and 2 mules. You want exactly 5 accounts to use 1 mule, and exactly 5 accounts to use another mule. You only need 2 profiles to make this happen, one profile can be running on group ID "a" and one profile on group id "b". Any accounts running on group id "a" will only mule with the mule that also has a group id of "a". As this uses dynamic muling, if you want to run 5 more accounts, you don't need to make a new profile; you can simply run another mule with the group id of "a" or "b", and more accounts on the respective group id. For example, you can run 10 accounts on grooup "a" and 5 accounts on group "b". If 2 mules are running on group "a", then each of the 10 accounts on group "a" will select their favourite mule among both mules running on group "a". In the event of a mule being banned, if another mule exists with the same group id, then the account will simply swap over to use another mule in the group. This setting makes it easy to launch replacement mules, while restricting which accounts can interact with a specific mule.

|}

@@ Line 21: / Line 21: @@
 | '''Reverse Bond if F2P''' || If your account is not members, it will try to receive a bond from the mule.
 |-
-| '''Mule Group ID''' || Group ID's allow refined control between what mule(s) a given account will connect to. This setting is used to restrict what accounts can connect to certain mules. If you configure a group ID in here, the account will only connect to a mule that has the same group ID. This is superior than configuring a port, as that forces you to have many profiles to have refined control over which mules the account(s) can connect to. The same as dynamic muling; if multiple mules have the same group ID, then the account will connect to its 'favourite' mule among the mules with the same group id. However, if no mules exist with the same group id, then it will not mule at all. This setting exists to give you refined control over what mules your accounts will connect to. Most people shouldn't use this setting, as dynamic muling should already be sufficient. For more information, here is some examples of how it works: if you have 10 rev accounts, and 2 mules. You want exactly 5 accounts to use 1 mule, and exactly 5 accounts to use another mule. You only need 2 profiles to make this happen, one profile can be running on group ID "a" and one profile on group id "b". Any accounts running on group id "a" will only mule with the mule that also has a group id of "a". As this uses dynamic muling, if you want to run 5 more accounts, you don't need to make a new profile; you can simply run another mule with the group id of "a" or "b", and more accounts on the respective group id. For example, you can run 10 accounts on grooup "a" and 5 accounts on group "b". If 2 mules are running on group "a", then each of the 10 accounts on group "a" will select their favourite mule among both mules running on group "a". In the event of a mule being banned, if another mule exists with the same group id, then the account will simply swap over to use the other mule in the group. This setting makes it easy to launch replacement mules, while restricting which accounts can interact with a specific mule.
+| '''Mule Group ID''' || Group ID's allow refined control between what mule(s) a given account will connect to. This setting is used to restrict what accounts can connect to certain mules. If you configure a group ID in here, the account will only connect to a mule that has the same group ID. This is superior than configuring a port, as that forces you to have many profiles to have refined control over which mules the account(s) can connect to. The same as dynamic muling; if multiple mules have the same group ID, then the account will connect to its 'favourite' mule among the mules with the same group id. However, if no mules exist with the same group id, then it will not mule at all. This setting exists to give you refined control over what mules your accounts will connect to. Most people shouldn't use this setting, as dynamic muling should already be sufficient. For more information, here is some examples of how it works: if you have 10 rev accounts, and 2 mules. You want exactly 5 accounts to use 1 mule, and exactly 5 accounts to use another mule. You only need 2 profiles to make this happen, one profile can be running on group ID "a" and one profile on group id "b". Any accounts running on group id "a" will only mule with the mule that also has a group id of "a". As this uses dynamic muling, if you want to run 5 more accounts, you don't need to make a new profile; you can simply run another mule with the group id of "a" or "b", and more accounts on the respective group id. For example, you can run 10 accounts on grooup "a" and 5 accounts on group "b". If 2 mules are running on group "a", then each of the 10 accounts on group "a" will select their favourite mule among both mules running on group "a". In the event of a mule being banned, if another mule exists with the same group id, then the account will simply swap over to use another mule in the group. This setting makes it easy to launch replacement mules, while restricting which accounts can interact with a specific mule.
 |}