Waste - Revision history

PhiNotPi: Fixed typos

2014-02-15T01:48:46Z

Fixed typos

Havvy: Fixing Spelling

2008-08-05T15:18:51Z

Fixing Spelling

Endy: waste stuff

2005-12-26T22:12:30Z

waste stuff

Endy: waste stuff

2005-12-26T22:10:13Z

waste stuff

Endy: waste stuff

2005-12-26T22:08:38Z

waste stuff

Endy: pwaste info

2005-12-26T22:05:24Z

pwaste info

Numsgil at 13:34, 22 September 2005

2005-09-22T13:34:42Z

66.91.141.218 at 07:26, 22 September 2005

2005-09-22T07:26:54Z

66.91.141.218 at 07:25, 22 September 2005

2005-09-22T07:25:50Z

66.91.141.218 at 23:08, 20 September 2005

2005-09-20T23:08:43Z

@@ Line 1: / Line 1: @@
 Waste is a byproduct of [[energy]] consumption.  Waste has yet to be standardized, so some actions produce disproportionately 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.
+When waste levels in a bot become greater than waste threshold (set in options panel) the bot will undergo "Alzheimer's", 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:
@@ Line 16: / Line 16: @@
 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 depending 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 metabolizing waste, converting it back into nrg for use.
-A portion of the waste will become permanent([[.pwaste]]) even if it has been transferred. 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 transferred. This will eventually kill a bot through Alzheimer's 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:

@@ Line 1: / Line 1: @@
-Waste is a byproduct of [[energy]] consumption.  Waste has yet to be standardized, so some actions produce disproptortionately more waste than others.
+Waste is a byproduct of [[energy]] consumption.  Waste has yet to be standardized, so some actions produce disproportionately 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.
+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:
@@ Line 14: / Line 14: @@
   .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 [[MB Sharing]]). The last, not so well known method is to use -4 .tieloc store to either give or take waste depending 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.
+A portion of the waste will become permanent([[.pwaste]]) even if it has been transferred. 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:

@@ Line 14: / Line 14: @@
   .sharewaste inc
-Causing the bot to give the bot it is tied to 99% of it's waste(see [[multibot]] sharing).
+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.
 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.

@@ Line 14: / Line 14: @@
   .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).
 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.

@@ Line 3: / Line 3: @@
 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 with the value of .waste typically specified in .shootval. Another favorite method is .sharewaste inc causing the bot to give the bot it is tied to 99% of it's waste. 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.
+Waste can be removed through several methods, the most popular of which is:
 A [[Veggy]] is capable of metabolising waste, converting it back into nrg for use.

← Older revision		Revision as of 22:05, 26 December 2005
Line 6:		Line 6:

	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 handy method for eventually unfixing the stuck bot is shown below:		A handy method for eventually unfixing the stuck bot is shown below:

@@ Line 10: / Line 10: @@
   ' will normally unfix bot by restoring .fixpos to zero
   cond
   start
   .fixpos *.fixed mult dec
   stop

← Older revision		Revision as of 07:25, 22 September 2005
Line 6:		Line 6:

	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 handy method for eventually unfixing the stuck bot is shown below:
		+
		+	' will normally unfix bot by restoring .fixpos to zero
		+	cond
		+	start
		+	.fixpos *.fixed mult dec
		+	stop