Difference between revisions of "Waste"

From WikiManual
Jump to: navigation, search
m (waste stuff)
m (waste stuff)
Line 14: Line 14:
 
  .sharewaste inc
 
  .sharewaste inc
  
Causing the bot to give the bot it is tied to 99% of it's waste(see [[MB]] sharing). The last, not so well known method is to use -4 .tieloc store to either give or take waste depeding on the value of tieval. Currently there are some bugs with this involving veggies, but otherwise it works perfectly.
+
Causing the bot to give the bot it is tied to 99% of it's waste(see [[multibot]] sharing).
 +
 
 +
The last, not so well known method, is to use -4 .tieloc store to either give or take waste depeding on the value of tieval. Currently there are some bugs with this involving veggies, but otherwise it works perfectly.
  
 
A [[Veggy]] is capable of metabolising waste, converting it back into nrg for use.
 
A [[Veggy]] is capable of metabolising waste, converting it back into nrg for use.
  
 
A portion of the waste will become permanent(pwaste) even if it has been transfered. This will eventually kill a bot through alzheimers mentioned above. The bot will also have a random chance of death from this.
 
A portion of the waste will become permanent(pwaste) even if it has been transfered. This will eventually kill a bot through alzheimers mentioned above. The bot will also have a random chance of death from this.
 
A handy method for eventually unfixing the stuck bot is shown below:
 
 
' will normally unfix bot by restoring .fixpos to zero
 
' typically I place this in most bots to prevent possible attack and accidental fixing
 
cond
 
start
 
.fixpos *.fixed mult dec
 
stop
 

Revision as of 18:10, 26 December 2005

Waste is a byproduct of energy consumption. Waste has yet to be standardized, so some actions produce disproptortionately more waste than others.

When waste levels in a bot become greater than waste threshold (set in options panel) the bot will undergo 'alzheimers', where random values are placed in random locations in the bots memory, causing many undesirable effects. The most common is for the bot to store some number in fixpos, becoming stuck in place.

Waste can be removed through several methods, the most popular of which is:

-4 .shoot store
*.waste .shootval store

With the value of .waste typically specified in .shootval, all of the waste is shot.

Another favorite method is:

.sharewaste inc

Causing the bot to give the bot it is tied to 99% of it's waste(see multibot sharing).

The last, not so well known method, is to use -4 .tieloc store to either give or take waste depeding on the value of tieval. Currently there are some bugs with this involving veggies, but otherwise it works perfectly.

A Veggy is capable of metabolising waste, converting it back into nrg for use.

A portion of the waste will become permanent(pwaste) even if it has been transfered. This will eventually kill a bot through alzheimers mentioned above. The bot will also have a random chance of death from this.