Template:Muling - Revision history

Veza: /* Muling */

2026-01-18T17:13:35Z

Muling

← Older revision		Revision as of 17:13, 18 January 2026
Line 21:		Line 21:
	\| '''Reverse Bond if F2P''' \|\| If your account is not members, it will try to receive a bond from the mule.		\| '''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.
	\|}		\|}

Veza: /* Muling */

2026-01-18T17:12:37Z

Muling

← Older revision		Revision as of 17:12, 18 January 2026
Line 21:		Line 21:
	\| '''Reverse Bond if F2P''' \|\| If your account is not members, it will try to receive a bond from the mule.		\| '''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". 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 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.
	\|}		\|}

Veza: /* Muling */

2026-01-18T17:08:31Z

Muling

← Older revision		Revision as of 17:08, 18 January 2026
Line 13:		Line 13:
	\| '''Gold To Keep''' \|\| Amount of gold to keep after muling. More information is above.		\| '''Gold To Keep''' \|\| Amount of gold to keep after muling. More information is above.
	\|-		\|-
	\| '''Ask Mule For Gold At''' \|\| If your ~~bot~~ has less gold than the input value, it will try to receive gold from the mule. Example: If you set this to 10m, and you have less than 10m GP, the ~~bot~~ will request gold from the mule. This amount of gold that's requested can be configured below. Set to -1 to disable.		\| '''Ask Mule For Gold At''' \|\| If your account has less gold than the input value, it will try to receive gold from the mule. Example: If you set this to 10m, and you have less than 10m GP, the account will request gold from the mule. This amount of gold that's requested can be configured below. Set to -1 to disable.
	\|-		\|-
	\| '''Ask Mule For Amount''' \|\| If you are receiving gold, your ~~bot~~ will try to receive this much gold from the mule.		\| '''Ask Mule For Amount''' \|\| If you are receiving gold, your account will try to receive this much gold from the mule.
	\|-		\|-
	\| '''Minimum Membership''' \|\| If a value above 0 is provided, the script will not mule unless you have more days of membership left. Example: If this is set to 2, and you have 2 days of membership left, the script will not mule.		\| '''Minimum Membership''' \|\| If a value above 0 is provided, the script will not mule unless you have more days of membership left. Example: If this is set to 2, and you have 2 days of membership left, the script will not mule.
	\|-		\|-
	\| '''Reverse Bond if F2P''' \|\| If your ~~bot~~ is not members, it will try to receive a bond from the mule.		\| '''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 ~~bot~~ 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 ~~bot~~ 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 ~~bot~~(s) can connect to. The same as dynamic muling; if multiple mules have the same group ID, then the ~~bot~~ 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 ~~bots~~, 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". 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". This setting makes it easy to launch replacement mules, while restricting which accounts can interact with a specific mule.
	\|}		\|}

Veza at 17:07, 18 January 2026

2026-01-18T17:07:07Z

← Older revision		Revision as of 17:07, 18 January 2026
Line 21:		Line 21:
	\| '''Reverse Bond if F2P''' \|\| If your bot is not members, it will try to receive a bond from the mule.		\| '''Reverse Bond if F2P''' \|\| If your bot is not members, it will try to receive a bond from the mule.
	\|-		\|-
	\| '''Mule Group ID''' \|\| This setting exists to give you refined control over what mules your ~~bots~~ will connect to. Most people shouldn't use this setting, as dynamic muling should already be sufficient. ~~The GUI has an explanation of how this works, however~~, here is some examples of how it works: if you have 10 rev bots, and 2 mules. You want 5 accounts to use 1 mule, and 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".		\| '''Mule Group ID''' \|\| Group ID's allow refined control between what mule(s) a given bot 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 bot 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 bot(s) can connect to. The same as dynamic muling; if multiple mules have the same group ID, then the bot 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 bots, 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". This setting makes it easy to launch replacement mules, while restricting which accounts can interact with a specific mule.
	\|}		\|}

Veza: /* Muling */

2026-01-18T17:03:28Z

Muling

← Older revision		Revision as of 17:03, 18 January 2026
Line 8:		Line 8:
	\|-		\|-
	\| '''Error URL''' \|\| A discord webhook URL for error information.		\| '''Error URL''' \|\| A discord webhook URL for error information.
	\|-
	~~\| '''Use Manager Mule''' \|\| If enabled, uses GManager where available to select a mule for you. This setting will be ignored if you manually enter a mule name.~~
	\|-
	\| '''Mule Name''' \|\| Username of the mule. This MUST be correct if populating a name. You can leave blank to connect to any GMuling running on the same computer/server, however if you leave this blank, the port must also be left as 0.
	\|-		\|-
	\| '''Mule At Amount''' \|\| When you have more than this amount + the amount of gold to keep (setting below this) the script will mule down to the amount of gold you want to keep. Eample: You set this amount to 10m, and you set gold to keep to 5m, you will mule when you reach 15m.		\| '''Mule At Amount''' \|\| When you have more than this amount + the amount of gold to keep (setting below this) the script will mule down to the amount of gold you want to keep. Eample: You set this amount to 10m, and you set gold to keep to 5m, you will mule when you reach 15m.
Line 25:		Line 21:
	\| '''Reverse Bond if F2P''' \|\| If your bot is not members, it will try to receive a bond from the mule.		\| '''Reverse Bond if F2P''' \|\| If your bot is not members, it will try to receive a bond from the mule.
	\|-		\|-
	\| '''~~Port (Optional)~~''' \|\| This ~~is an optional~~ setting. ~~We generate a unique port based on the username~~ of ~~the~~ mule. ~~If you're running into issues~~, ~~you~~ can ~~set~~ a ~~specific port. Note: Mule~~ and ~~script port options much match if set~~. ~~If you set port 54321~~ on the mule, ~~then all bots that~~ you want to mule with ~~this mule~~, ~~must also have~~ their mule ~~port set to 54321~~.		\| '''Mule Group ID''' \|\| This setting exists to give you refined control over what mules your bots will connect to. Most people shouldn't use this setting, as dynamic muling should already be sufficient. The GUI has an explanation of how this works, however, here is some examples of how it works: if you have 10 rev bots, and 2 mules. You want 5 accounts to use 1 mule, and 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".
	\|}		\|}

Acans: /* Example */

2025-08-19T11:22:21Z

Example

← Older revision		Revision as of 11:22, 19 August 2025
Line 29:		Line 29:

	===Example===		===Example===
	[[File:muling-example.png\|right]] This example is from my [[~~GZilyana~~]]. In this example, you see I've set up a Discord Webhook if the account trying to trade the mule cannot for any reason. The mules name is included that it'll trade gold to, or request it from. It's setup to mule once it gets to 35m GP, as it needs to give 30m and keep 5m. Or to request 5m from the mule, if it gets below 2m GP from buying supplies. Reverse Bond if F2P is enabled in case the [[#autobond\|Auto Bond]] setting in [[#Misc\|Misc]] tab is set to 0. The port is set to 54321, as this is the port I've manually defined in the settings for the mule running [[GMuling]].		[[File:muling-example.png\|right]] This example is from my [[GDelve]]. In this example, you see I've set up a Discord Webhook if the account trying to trade the mule cannot for any reason. The mules name is included that it'll trade gold to, or request it from. It's setup to mule once it gets to 35m GP, as it needs to give 30m and keep 5m. Or to request 5m from the mule, if it gets below 2m GP from buying supplies. Reverse Bond if F2P is enabled in case the [[#autobond\|Auto Bond]] setting in [[#Misc\|Misc]] tab is set to 0. The port is set to 54321, as this is the port I've manually defined in the settings for the mule running [[GMuling]].

	{{Template:DiscordWebhook}}		{{Template:DiscordWebhook}}

Acans: /* Muling */

2025-08-19T11:22:09Z

Muling

← Older revision		Revision as of 11:22, 19 August 2025
Line 1:		Line 1:
	==Muling==		==Muling==

	All G Scripts have a dedicated Muling tab, where you can customise and set default options. Below is a table of all the settings and descriptions, and below it, an [[#Example\|example]] of my Muling tab from [[~~GZilyana~~]].		All G Scripts have a dedicated Muling tab, where you can customise and set default options. Below is a table of all the settings and descriptions, and below it, an [[#Example\|example]] of my Muling tab from [[GDelve]].

	{\| class="wikitable"		{\| class="wikitable"
Line 11:		Line 11:
	\| '''Use Manager Mule''' \|\| If enabled, uses GManager where available to select a mule for you. This setting will be ignored if you manually enter a mule name.		\| '''Use Manager Mule''' \|\| If enabled, uses GManager where available to select a mule for you. This setting will be ignored if you manually enter a mule name.
	\|-		\|-
	\| '''Mule Name''' \|\| Username of the mule. This MUST be correct.		\| '''Mule Name''' \|\| Username of the mule. This MUST be correct if populating a name. You can leave blank to connect to any GMuling running on the same computer/server, however if you leave this blank, the port must also be left as 0.
	\|-		\|-
	\| '''Mule At Amount''' \|\| When you have more than this amount + the amount of gold to keep (setting below this) the script will mule down to the amount of gold you want to keep. Eample: You set this amount to 10m, and you set gold to keep to 5m, you will mule when you reach 15m.		\| '''Mule At Amount''' \|\| When you have more than this amount + the amount of gold to keep (setting below this) the script will mule down to the amount of gold you want to keep. Eample: You set this amount to 10m, and you set gold to keep to 5m, you will mule when you reach 15m.

Acans at 12:03, 4 July 2025

2025-07-04T12:03:43Z

← Older revision		Revision as of 12:03, 4 July 2025
Line 1:		Line 1:
	==Muling==		==Muling==

	All G Scripts have a dedicated Muling tab, where you can customise and set default options. Below is a table of all the settings and descriptions, and below it, an [[#~~example~~\|example]] of my Muling tab from [[GZilyana]].		All G Scripts have a dedicated Muling tab, where you can customise and set default options. Below is a table of all the settings and descriptions, and below it, an [[#Example\|example]] of my Muling tab from [[GZilyana]].

	{\| class="wikitable"		{\| class="wikitable"

Acans: /* Muling */

2025-07-04T12:03:01Z

Muling

← Older revision		Revision as of 12:03, 4 July 2025
Line 1:		Line 1:
	==Muling==		==Muling==

	All G Scripts have a dedicated Muling tab, where you can customise and set default options. Below is a table of all the settings and descriptions, and below it, an example of my Muling tab from [[GZilyana]].		All G Scripts have a dedicated Muling tab, where you can customise and set default options. Below is a table of all the settings and descriptions, and below it, an [[#example\|example]] of my Muling tab from [[GZilyana]].

	{\| class="wikitable"		{\| class="wikitable"

Acans: /* Example */

2025-07-03T13:47:20Z

Example

← Older revision		Revision as of 13:47, 3 July 2025
Line 29:		Line 29:

	===Example===		===Example===
	[[File:muling-example.png\|right]] This example is from my [[GZilyana]]. In this example, you see I've set up a Discord Webhook if the account trying to trade the mule cannot for any reason. The mules name is included that it'll trade gold to, or request it from. It's setup to mule once it gets to 35m GP, as it needs to give 30m and keep 5m. Or to request 5m from the mule, if it gets below 2m GP from buying supplies. Reverse Bond if F2P is enabled in case the [[#autobond\|Auto Bond]] setting in [[#Misc]] tab is set to 0. The port is set to 54321, as this is the port I've manually defined in the settings for the mule running [[GMuling]].		[[File:muling-example.png\|right]] This example is from my [[GZilyana]]. In this example, you see I've set up a Discord Webhook if the account trying to trade the mule cannot for any reason. The mules name is included that it'll trade gold to, or request it from. It's setup to mule once it gets to 35m GP, as it needs to give 30m and keep 5m. Or to request 5m from the mule, if it gets below 2m GP from buying supplies. Reverse Bond if F2P is enabled in case the [[#autobond\|Auto Bond]] setting in [[#Misc\|Misc]] tab is set to 0. The port is set to 54321, as this is the port I've manually defined in the settings for the mule running [[GMuling]].

	{{Template:DiscordWebhook}}		{{Template:DiscordWebhook}}