Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
Starfox

[Tutorial] Sigma Botfarm Manager Tutorial (Sigma Mule) [Also Great for NON-GOLDFARMERS]

Recommended Posts

Sigma Botfarm Manager Tutorial

This tutorial does not apply to the beta version. If you have questions about the beta version, please message tacomanstan on Skype.

CLICK HERE

NOTE: All recent changes will be shown in RED.
Step 1: Sigma Server and Repository Setup
Step 1.1: Downloading the Sigma Server

The first part to understanding how to set up Sigma Mule is understanding how it works. Sigma Mule communicates through sockets, which is a low-level way of sending packets over connections. In other words, Sigma Mule communicates with its slaves almost instantly.
 
You are going to need to download the Sigma Server, which can be found at the top of the Sigma Mule thread (link above). Once you have downloaded the Sigma Server, you will be able to connect to it from ANY computer, proxy, VPN, VPS, etc.
 
ALWAYS be sure that you are running the most recent version of Sigma Server, or some (or all) functions of Sigma Mule will not work correctly. The file you download will always have a version number, for example, "Sigma Server v0.0.0". You can also see the version number by looking at the name of the Sigma Server window when it is opened.


Step 1.2: Downloading both Sigma Mule and Sigma Slave from the Repository

Realize that Sigma Mule and Sigma Slave work together. The term "Sigma Botfarm Manager" refers to both Sigma Mule's and Sigma Slave's running together to create a farm. Be sure that you add both Sigma Mule and Sigma Slave from the repository.


 
Step 2: Starting the Server, Mule, and Slave
Step 2.1: Starting Sigma Server

Once you have downloaded the Sigma Mule Server, you are going to need to open it before you can start either Sigma Mule or Sigma Slave.
Once you have opened the server, the following window will be opened. Once you add a slave or mule, the area to the right will display a preview of their client. By going into "Preview Options" -> "Block Input", you will be able to control the client directly from the server.

Important Notes:

  • On any connection other than local host (will be explained more later), it is highly recommended that you keep the preview closed. It will potentially cause large amounts of delay, even on fast connections.
  • Having the preview open uses a large amount of CPU, even on a local connection. When you are not using it, be sure to keep it closes by clicking the "Hide Preview" button shown on the right side of the window.
  • Be sure you are always running the correct version. I said that in the previous section, and I will say it again. If you are not running the most current version of Sigma Server, weird things can happen.

xvnjiCv.jpg
 
Below is an example of what the preview looks like.
me19vU6.png

It is also possible that the window might open in its collapsed form, and will look like this. If you want to see the preview, simply click the "Show Preview" button shown on the right side of the window.
6QEHnvN.png
 
Once you have this window open, starting Sigma Mule and Sigma Slave is an extremely easy process.


Step 2.2: Starting Sigma Mule or Sigma Slave w/ Proxies/VPNs/VPSs/etc
If you running your farm on the same computer you are running Sigma Server, and are not using proxies, skip to Step 2.3.

Starting Sigma Mule/Slave through a proxy, on a VPN, or on another computer is extremely easy.
 
The first thing you are going to need to do is get your computer ready to handle the connection. To do this, you are going to need to use Port Forwarding to forward the port 1642 to the computer that you are running Sigma Server on. You cannot run the server on a connection that you don't have access to.

 

If you are unfamiliar with the concept of port forwarding, refer to this tutorialIf you still have any questions after reading the tutorial, feel free to message me on Skype and I will personally help you through the process.
 
Once you have set up the port forwarding, enter in the IP address of the router that is connected to the computer that is running Sigma Server into the arguments of the client (or client starter) before starting the script. Refer to the following image.
PVOuE8g.png
 
Once you have followed those steps, all you have to do is start the script normally, and you are good to go!


Step 2.3: Managing Slaves and Mules in the Sigma Server

Once you have started Sigma Mule or Sigma Slave, you will notice that they will appear in the server Mule List or Slave List, respectively. If they do not, do the following:

  • The connection will not be established until the account is logged in. Wait for the account to log in.
  • If the account still doesn't appear in the server once logged in, make sure you have the most recent version of the Sigma Server.
  • If you have the most recent version of Sigma Server, try restarting the server and all clients.
  • If you have tried restarting all servers and all clients, check your firewall settings to make sure the connection isn't being denied.
  • If the firewall settings (both TRiBot and your local firewall) aren't blocking the connection, try restarting your computer.
  • If you have tried restarting your computer, contact me on Skype immediately so that I can help you troubleshoot.

Once a slave is added, you will notice that the script will have stopped. However, as long as the slave is listed in the server Slave List, it is connected and running. You will then be able to stop the slave by right clicking  and selecting "Stop Slave".
 
Mules are easier to manage. Once a mule is connected, the Mule GUI will appear. In order to stop a mule, all you have to do is close the GUI or click "Stop Script" in the TRiBot client.



Step 3: Setting Up Your Farm
Step 3.1: The Item Editor
Before you get started, be sure that you have a Sigma Mule connected to the server and that the Sigma Mule GUI is visible.

The Item Editor is the base of every type of farm. In order to start a farm, you must enter any item that is going to be used in the farm into the Item Editor.
First, you are going to need to open the Item Editor. Go into "Editors" -> "Item Editor".
cstahSV.jpg

The following window will then be opened. As you can see, adding an item to the Item Editor is an extremely easy process. Simply right click and then selected "Add Item" from the dropdown menu that appears.
XSmQvA4.png

Once an item has been added, the values on the right can be modified. The values are:

  • Item Name: The name of the item. It does NOT need to match the in game name of the item.
  • Item Name (p): The plural name of the item. This is ONLY used for visual purposes, and will have no effect on the functionality of the mule or slave. If you leave it blank, an "s" will automatically be added to the end of the value you entered for "Item Name". An example of when you would want to add your own Item Name (p) would be in the case of Flax, Coal, etc. (You wouldn't say "Flaxs" or "Coals")
  • Item ID: The ID of the item.
  • Item ID (n): The noted ID of the item. If the item cannot be noted, leave this blank.
  • Item Value: If you are going to use a Condition based on value, enter the value of the item here (not required otherwise). Conditions will be discussed in detail later.

mWwfsv7.png

Once you are done adding all of the items you are going to need to the Item Editor, click "Done".
Note that you can add/remove items at any time. If you remove an item that is currently being used in an order, don't worry, it won't have any effect on that order.


Step 3.2: The Order Editor
At this point you should have all of the items that you are going to need entered into the Item Editor. If this is not the case, go do that now.

The Order Editor is going to allow you to add orders that are going to be executed across your farm. This includes transferring items to the slave from the mule, and from the mule to the slave.
First, you are going to need to open the Order Editor. Go into "Editors" -> "Order Editor".
J0P1v7X.jpg
 
The following window will be opened. As you can see, adding an order to the Order Editor is an extremely easy process. Simply right click and then selected "Add Order" from the dropdown menu that appears.
COimrpQ.png
 
Once an order has been added, the values below can be modified. The values are:

  • Order Name: The name of the order. This is going to be what is displayed everywhere the order is being used, so name the order something descriptive.
  • From Bank: If you are going to be doing a bank trade, check this. If an order is a bank trade order, that means that the items in question will be withdrawn from the bank if necessary.
    • An example would be most collecting farms. I'll use fishing as an example. Let's say I have a full inventory of fish, and the script goes to bank them. If my order is to withdraw fish, the script would do so at that time, but ONLY if From Bank is selected.
    • Any Order Part (more about Order Parts in the next section) that is from the slave to the mule will not be affected by From Bank.
  • Should Wait: If Should Wait is selected, as soon as the order is ready, the slave will pause the script and wait for the mule to trade it. If Should Wait is deselected, the slave will not pause the script until the mule is right next to it and ready to trade it.
    • Should Wait should be selected on accounts that login and logout frequently.
    • Should Wait should be selected on accounts that roam frequently, and whose position will likely be dynamic.
    • Should Wait is enabled by default is Bank Trade is selected.

After you have determined the options for the Order as a whole, then you are going to need to add Order Parts to the Order. Right click and then select "Add Order Part" from the dropdown menu that appears.
p4WhGmX.png
 
The following window will then be opened. The aspects of an Order Part are:

  • Amount: This is the field right after "Trade". This is the amount of the item that is being transferred. If you want to transfer all of the item, enter "0".
  • Noted?: If you want to trade the item in noted form, select this check box. If you do not, leave it deselected.
  • Item Dropdown Menu: This is going to be a list of all of the items you have entered into the Item Editor. Select the item that you wish to be traded.
  • To Mule?: If you want the items to be transferred from the slave to the mule, select this check box. If you want the items to be transferred from the mule to the slave, leave it deselected.

4PDpuea.jpg
 
When you are done filling out the Order Part details, click "OK". As you can see below, you can add and remove Order Parts freely. Adding multiple Order Parts will cause all of those items to be traded in the same trade window. This is good not only for efficiency, but to lower the chance of getting a RWT ban.
ut0hGqg.png
 
Once you are satisfied with your Orders, click "Done" to move on. As with Items, you can add/remove Orders at any time.


Step 3.3: The Condition Editor
At this point you should have all of the items that you are going to need entered into the Item Editor, and have all of the Orders that you are going to need entered into the Order Editor. If this is not the case, go do that now.

The Condition Editor is going to allow you to control when an Order is executed. This will allow you to make sure that your mule will not collect too frequently, but also make sure your slave doesn't have too much value on it.
First, you are going to need to open the Condition Editor. Go into "Editors" -> "Condition Editor".
Aycjiyx.jpg
 
The following window will be opened. As you can see, adding a condition to the Condition Editor is an extremely easy process. Simply right click and then selected "Add Condition" from the dropdown menu that appears.
ALwpoq3.png

Once a condition has been added, you will be able to modify the values of the condition below. Those values are:

  • Condition Name: The name of the condition. This is going to be what is displayed everywhere the condition is being used, so name the condition something descriptive.
  • Count/Value: Whether the condition should be measuring the count of the item or the value of the item.
    Remember back to the Item Editor, when you could enter in the value of an item? This is where that comes into play.
  • Noted?: Select this check box if you want to check for noted items. Keep it deselected if you would like to check for non-noted items.
    Note that even if you have "In Bank" selected, still check "noted?" if the items are going to be withdrawn as a note. The reason is, once the items are withdrawn and are in your inventory, those are being counted. Don't worry, Sigma Mule will know to check for the non-noted ID when looking in your bank.
  • Item: The item that you are comparing with the condition. This will be a dropdown menu with all of the items that you have added into the Item Editor.
  • In Bank: Select this check box if you want the items in your bank to be checked. If you only want to check for items in your inventory, keep this deselected.
  • Comparison Operator: The way in which the condition compares the two values. It will be a drop down menu with many options.
  • Value: What value you are comparing the derived value from.

Once you have all the values filled out, you will see that a nice, easy to read sentence if formed in the list above, and will be updated in live time. You can also see the dropdown menu, showing you the two options that you can choose. Refer to the image below.
zZ1RkOQ.png
 
Once you are done adding all of the conditions you are going to need to the Item Editor, click "Done".

Note that you can add/remove conditions at any time. If you remove a condition that is currently being used in an order, don't worry, it won't have any effect on that order. However, if you edit a condition, that condition will be update in live time. Be sure that you disable any orders that are using the condition before doing any editing (more about enabling/disabling orders later).


Step 3.4: The Movement Editor
At this point you should have all transfer aspects of your farm setup, meaning items, orders, and conditions.

The Movement Editor is an extremely powerful tool, and is going to become more powerful as more features are added to it. If you used Sigma Mule BETA, then you will notice that the GUI looks the same, but the functionality is vastly different.
First, you are going to need to open the Movement Editor. Go into "Editors" -> "Movement Editor".
JPydXH5.png
 
The following window will be opened. As you can see, adding a movement to the Movement Editor is an extremely easy process. Simply right click and then selected "Add Movement" from the dropdown menu that appears.
iEbQdR1.png
 
Once a movement has been added, you will be able to modify the values to the right. Setting up a movement is an extremely easy process, and there are very few values that you need to worry about.

  • Movement Name: The name of the movement. This is going to be what is displayed everywhere the movement is being used, so name the movement something descriptive.
  • Teleport Location: This is where the mule will teleport to in an attempt to get as close to the slave as possible. Try to pick the location that is going to make the movement to the slave as fast and as easy as possible.
  • Teleport Enabled: The unlabeled checkbox to the right of the teleport option controls whether or not the mule will attempt to teleport to get to the slave. Even if the teleport is enabled, the mule will try to walk to the slave first if it is within range. ONLY disable this if you are SURE that the mule will not have any complicated paths to walk.
  • Critical Points: This is where the Movement Editor varies drastically from when Sigma Mule was in beta. Instead of plotting out the exact path, all you need to do is specify any critical points. Critical points are areas where the pathfinding cannot physically find a correct path. This means anything that changes the plane of the mule (such as ladders) or teleports the mule, such a levers or portals.
    To add a critical point, simply walk your player to the location you want, and click "Add".

Here is an image of an added movement, and the dropdown menu of teleport locations.
Ze0wJHg.png
 
Important Notes:

  • All paths are 100% generated. The chances of a mule getting stuck, even when walking long distances, is very small.
  • If a mule DOES get stuck, it will attempt to correct itself in a variety of ways.
  • To reduce the chances of your mule getting stuck, try to set the teleport location as close to the slave as possible.
  • All obstacles are handled automatically. If you notice an obstacle that isn't being handled, report it to me immediately so I can fix it.

The Movement Editor is going to be expanding quite a bit in the next month. Be sure to stay tuned for updates!


 
Step 4: Starting the Farm
Step 4.1: Adding a Slave to a Mule
Be SURE that you have Varrock Tabs in your bank before starting the mule. I am working on a fix for this, but as of now it is a necessary security feature.

Once you have the data of your farm ready to go, it's time to actually start it.
First, go to the Sigma Server and select the mule you want to add the slave to, and then select the slave you want to add to the mule. Once both are selected, press enter.
 
You will notice that the slave has appeared in the mule's GUI.
H8vAXxy.png


Step 4.2: Adding an Order to a Slave

Once you have the slave added to the appropriate mule, you can then add an order to it. Right click on the the list titled "Orders" to add a new order.
H8vAXxy.png
 
Once you click "Add Order", the following window will appear. You will notice how the order that we created earlier is there for us to choose. Had we created other orders, those orders would be listed in the dropdown menu as well.
FzVSDNX.png
 
When you have chosen the order you wish to add, click "Select". The order will then appear in the "Orders" list.
zUf7s6S.jpg
 
Once you have your order added, select it and then right click the "Conditions" list. The same type of window will appear as with orders, but will instead contain a list of conditions.
 
Once you have selected, the condition you wish to add, the condition will appear in the "Conditions" list.
iIzsJk7.png
 
Notice that both the condition and order are grey. This means that the order is disabled. To enable it, either select the order and press "e", or right click and select "Enable Order".
Notice that "Remove Order" is now also an option. You can add and remove as many orders and conditions as you need.
TbLh245.png
 
Also, refer to the bottom right corner. By default, before you add an order or do anything else, the first movement in the Movement Editor will be selected as the movement for the slave. Choose the movement that is most appropriate for the slave.


Step 4.3: Enabled/Disabling the Teleport Fallback Feature

If you do not have Varrock Tablets in your bank, you are going to need to disable the teleport fallback feature (disabled by default). Alternatively, if you do have Varrock Tablets, it is a good idea to keep this feature enabled as a security feature, just in case your mule cannot reach a bank.
 
To do this, simply select/deselect "Use Teleport Backup" from the options menu as shown below.
6a4PwZE.png


Step 4.4: Logging the Mule Out

You are now ready to go! The last step is selecting the "Should Logout" option to ensure that the mule is logged out whenever it doesn't have an order that it needs to be executing.
LGXXjau.jpg


 
Types of Farms:
Basic Farm (Not So Good):

A basic (or collecting) farm is the simplest of all farms. It revolves around collecting a lot of a single item, and storing these items on the mule account. An example would be a large woodcutting farm, or a mining farm, or a flax-picking farm. The mule will generally be in one area, and many aspects of the farm must still be done manually.
 
This is NOT the recommended way to use Sigma Botfarm Manager.


Semi-Basic Farm (Good):

A semi-basic farm is the same as the basic farm in all aspects but one. Instead of storing the items that are farmed on the mule indefinitely, you bring a seller into the mix by using Sigma Merch.
 
Setup the mule to transfer the items to the seller at a certain point, and then once the seller gets to a certain amount of gold, transfer the gold from the seller on to the mule. This way, you will come back to find large amounts of gold on your mule, seemingly magically!
 
How can it get better than that??? Keep reading.


Cycle Farm (Better):

A cycle farm is a farm that is just that: a cycle. An example would be the following:

  • Flax pickers pick flax.
  • Flax spinners spin the flax provided from the flax pickers into bowstrings.
  • Woodcutters cut various types of logs.
  • Fletchers fletch the logs provided by the woodcutters and the bowstrings provided by the flax spinners into bows.
  • Sellers (use Sigma Merch) sell the bows provided by the fletchers.
  • The mule collects the gold from the seller.

That is an example of an intricate cycle farm. All of the pieces fit together to get you the most profit possible. So how can it get better than that?


Compound Farm (Best):

A compound farm revolves around the idea of making a slave also a mule. This will make your cycle farm far more efficient, hence turning it into a compound farm.
 
Let's say, for example, you have 15 woodcutters. Your mule will be overworked trying to collect from all of those, so you create a dedicated wood collecting mule. However, this mule will also be running as a slave in the background. You set up your primary mule to collect all of the wood that the wood collecting mule has collected already.
 
You set up every section of your cycle farm in this way. This will make your primary mule as efficient as possible, and lower the chances of it getting banned even lower than they already are! (Have I mentioned that through my 2 months of testing, I have NEVER had a mule banned?).


Player Farm (For Non-Goldfarmers):

Sigma Mule doesn't benefit only goldfarmers! Sigma Mule benefits regular players as well! You can set up the mule to resupply your main with items when you are running low, or set it to take items from you when you are going into the wilderness.
 
Better yet, if the mule doesn't have the item you are requesting, Sigma Mule will do its best to buy the item from Zybez or the Trading Post (when it comes out). This will make playing RuneScape a much more pleasant experience for all players. (This feature will be added once the trading post comes out).


One-Click Orders (For Non-Goldfarmers):

Sigma Mule also has the capability to issue a single order. All you must do is save the order into the "One-Click Orders" editor, and then click "Execute Order".
 
This is especially useful for NON-GOLDFARMERS. Why, you ask? Well, think of it this way: You are leveling some skill, PKing, questing, etc. You then run out of items, or find a really valuable item that you don't want to lose. What can you do?
 
Using a One-Click Order, you can have the mule automatically come to your player and trade you items, have the mule take items from you, or both. The mule will find you wherever you are, and can buy the items that you are requesting if it doesn't already have them.
 
This feature is still in development, and will likely be released around the same time as the Trading Post.

Edited by Starfox
  • Like 3

Share this post


Link to post
Share on other sites
Array

How do you get your slave to connect to mule ? i can see everything in preview window but I cannot get my slave to connect to mule GUI, so I can start orders is this because I dont have a varrock tab even though its walking ?

No, that "bug" has been fixed. I will have the tutorial updated ASAP. Highlight the mule, then highlight the slave, then press enter. The slave will then be attached to the mule that you have highlighted.

Share this post


Link to post
Share on other sites

Amazing after I figured it out worked great i may even make a video tut. However, my mule was banned even though seperate proxy any tips or recommendations you have to prevent this?

Had you botted on that account previously? If so, I have a big hunch the mule is not what got you banned.

Share this post


Link to post
Share on other sites

I have a question about this script.

 

I have setup this whole thing. My mule is not logging in, and my slaves just took all their noted logs from the bank and are just woodcutting like nothing happend. What did I do wrong?

 

It's just spamming some random things in my debug screen

I'm going to need more information than that. Have you read the entire tutorial?

Edited by Starfox

Share this post


Link to post
Share on other sites

I'm going to need more information than that. Have you read the entire tutorial?

Yeah I did, I followed the whole tutorial and did what the tutorial told me. I thought this other topic would fit better so I have deleted this post here and added an post with a little more details here: https://tribot.org/forums/topic/36659-sigma-bot-manager-elite-polished-and-powerful-10month/page-3

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 50 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 86 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
        • Like
      • 25 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
        • Like
      • 51 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...