Difference between revisions of "Multibot"

From WikiManual
Jump to: navigation, search
m (Fixed typos)
 
(15 intermediate revisions by 9 users not shown)
Line 2: Line 2:
 
Multibots are organisms that are made up of more than one bot. In a MB (MultiBot) the bots are connected by ties . The first multibot was in the form of a triangle where each bot worked independently, but all three coordinated their movement in order to obtain food.
 
Multibots are organisms that are made up of more than one bot. In a MB (MultiBot) the bots are connected by ties . The first multibot was in the form of a triangle where each bot worked independently, but all three coordinated their movement in order to obtain food.
  
[[Image:Triangulus_P.jpg|frame|right|This is one of the first and simpliest Multibots there is]]
+
[[Image:Triangulus_P.jpg|frame|right|This is one of the first and simplest Multibots there is]]
  
This is a picture of the Triangulus_P bot, the first MB ever created.  
+
This is a picture of the Triangulus_P bot, the first MB ever created.
  
 +
[[MB Construction]]
  
--------------------------------------------------------------------------------
+
== MB Commands ==
  
'''MB Commands'''
+
[[MB Sharing]]
  
The bots in the MB must be connected with each other, and for that they use ties . The bots within a MB can share information, energy and protective layers with each other. Bots can learn whether they are a part of MB using the .multi command, which returns 1 when the bot is a part of a MB(intentially or not), and 0 when it is not.
+
The bots in the MB must be connected with each other, and for that they use ties . The bots within a MB can share information, energy and protective layers with each other. Bots can learn whether they are a part of MB using the .multi command, which returns 1 when the bot is a part of a MB(intentionally or not), and 0 when it is not.
  
 
The presence of a tie alone does not make the bot a multibot.  The tie must first harden.
 
The presence of a tie alone does not make the bot a multibot.  The tie must first harden.
  
--------------------------------------------------------------------------------
+
== MB Advantages ==
  
'''MB Advantages'''
+
MBs have several advantages over a normal [[Single Bot]](SB). They are less likely to die of [[Shock Death]] since the cost is determined over all connected bots. All bots in a MB are teleported together into another simulation from a teleporter in [[Internet Mode]] (up to a maximum of 50 connected bots). Adjacent bots in a MB can also help each other including access to Mb sharing.
  
The MBs have some advantages over a normal [Single Bot]](SB).  Most of these are in the form of cheaper actions (costs of actions divided by number of other bots the current cell is connected to).
+
== MB Problems ==
  
 +
Many MBs have difficulty when it comes time to reproducing. Coordinating motion in one direction amongst the bots can also prove difficult. With good coding, however, any problem can be solved.  Helios is a good example of a MB that is stronger than most [[Single Bot]]s.
  
--------------------------------------------------------------------------------
+
== MB philosophy and reality ==
 +
Note that while the program will regard any two bots that are connected by a permanent tie as a multibot, users generally have more strict criteria.
  
'''MB Problems'''
+
The MB philosophy mirrors what separates real-life multicellular creatures and simply bacteria that are stuck together.  This applies primarily to the [[Multibot League | MB]] [[league]].
  
Many MBs have difficulty when it comes time to reproducing. Coordinating motion in one direction amongst the bots can also prove difficult. With good coding, however, any problem can be solvedHelios is a good example of a MB that is stronger than most SB.
+
*Differentiation - Although not required, a good multibot should be differentiated into a head and body at the very least.
 +
*Discreteness of Identity - Fancy way of saying that there is a clear boundary between what is part of the multibot and what is not.  A large mass of veggies that are all tied together in an amorphous blob is not generally considered a MB.
 +
*Cooperation - A bot that just ties to everything and anyone it can is not a multibot.  Likewise a tie feeder that has permanently connected to a veggy isn't either. Both bots in a permanent tie should be cooperating with each other.
 +
*Structure - The bots should have some clear form of structural organization.  This is not as strict as the others, but its a good rule of thumb.  3 bots that just randomly connect to each other will not be as structured as 3 bots that link together to form an equilateral triangle. The more symmetric the organism is, the more structured it could be said to be.
 +
*Reproducibility - The collection of bots should be able to form a new collection of bots with the same general properties as itselfThis often involves a life process from egg to larvae to adult.  A triangular MB should be able to form a new triangular MB.  The method of this reproduction is not at all standard.
 +
 
 +
== Batterybots ==
 +
 
 +
A [[batterybot]] is a special type of multibot. It ties to a veggy, thus gaining a theoretically limitless energy supply. I am not sure if they are classed as true multibots but they do have ties.
 +
 
 +
==Types of Multibots==
 +
Multibots can be linear or [[amoeba]]s. In general, linear bots are easier to program, but lining up the bots can be tricky. Amoebas are often very chaotic; so much so that it is almost impossible to make them move predictably.
 +
[[Category:Bottype]]

Latest revision as of 23:13, 15 February 2014

Multibots

Multibots are organisms that are made up of more than one bot. In a MB (MultiBot) the bots are connected by ties . The first multibot was in the form of a triangle where each bot worked independently, but all three coordinated their movement in order to obtain food.

This is one of the first and simplest Multibots there is

This is a picture of the Triangulus_P bot, the first MB ever created.

MB Construction

MB Commands

MB Sharing

The bots in the MB must be connected with each other, and for that they use ties . The bots within a MB can share information, energy and protective layers with each other. Bots can learn whether they are a part of MB using the .multi command, which returns 1 when the bot is a part of a MB(intentionally or not), and 0 when it is not.

The presence of a tie alone does not make the bot a multibot. The tie must first harden.

MB Advantages

MBs have several advantages over a normal Single Bot(SB). They are less likely to die of Shock Death since the cost is determined over all connected bots. All bots in a MB are teleported together into another simulation from a teleporter in Internet Mode (up to a maximum of 50 connected bots). Adjacent bots in a MB can also help each other including access to Mb sharing.

MB Problems

Many MBs have difficulty when it comes time to reproducing. Coordinating motion in one direction amongst the bots can also prove difficult. With good coding, however, any problem can be solved. Helios is a good example of a MB that is stronger than most Single Bots.

MB philosophy and reality

Note that while the program will regard any two bots that are connected by a permanent tie as a multibot, users generally have more strict criteria.

The MB philosophy mirrors what separates real-life multicellular creatures and simply bacteria that are stuck together. This applies primarily to the MB league.

  • Differentiation - Although not required, a good multibot should be differentiated into a head and body at the very least.
  • Discreteness of Identity - Fancy way of saying that there is a clear boundary between what is part of the multibot and what is not. A large mass of veggies that are all tied together in an amorphous blob is not generally considered a MB.
  • Cooperation - A bot that just ties to everything and anyone it can is not a multibot. Likewise a tie feeder that has permanently connected to a veggy isn't either. Both bots in a permanent tie should be cooperating with each other.
  • Structure - The bots should have some clear form of structural organization. This is not as strict as the others, but its a good rule of thumb. 3 bots that just randomly connect to each other will not be as structured as 3 bots that link together to form an equilateral triangle. The more symmetric the organism is, the more structured it could be said to be.
  • Reproducibility - The collection of bots should be able to form a new collection of bots with the same general properties as itself. This often involves a life process from egg to larvae to adult. A triangular MB should be able to form a new triangular MB. The method of this reproduction is not at all standard.

Batterybots

A batterybot is a special type of multibot. It ties to a veggy, thus gaining a theoretically limitless energy supply. I am not sure if they are classed as true multibots but they do have ties.

Types of Multibots

Multibots can be linear or amoebas. In general, linear bots are easier to program, but lining up the bots can be tricky. Amoebas are often very chaotic; so much so that it is almost impossible to make them move predictably.