In and Out - Revision history

Jarbon: Removed circular links

2008-07-06T23:02:36Z

Removed circular links

Jarbon: Edited to include that there are now 10 in and out sysvars as the article had previously only made reference to 5.

2008-07-06T22:58:06Z

Edited to include that there are now 10 in and out sysvars as the article had previously only made reference to 5.

Chickenlord at 03:05, 2 March 2008

2008-03-02T03:05:58Z

Elite at 19:11, 13 February 2006

2006-02-13T19:11:05Z

66.91.141.218 at 06:24, 27 September 2005

2005-09-27T06:24:15Z

66.91.141.218 at 06:24, 27 September 2005

2005-09-27T06:24:03Z

66.91.141.218 at 06:21, 27 September 2005

2005-09-27T06:21:06Z

66.91.141.218 at 06:18, 27 September 2005

2005-09-27T06:18:39Z

New page

This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or out2 can be read by any robot viewing the bot, with the value arriving at out1 or out2 respectivly.

A problem similar to the one facing bots using [[Memloc and Memval |memloc/memval]] for identification is that with the simple code:

*.in1 .out1 store

An enemy bot can seem like family. Of course with randomly([[rnd]]) changing their value via [[inc/dec]] an enemy bot will waste [[Energy]] storing these.

← Older revision		Revision as of 23:02, 6 July 2008
Line 1:		Line 1:
−	This refers to the 10 [[in]] and [[out]] sysvar locations. The number stored at [[.out1]], [[.out2]] or another out can be read by any robot viewing the bot, with the value arriving at [[.in1]], [[.in2]] or another in respectively. These were in the past used for identification, and more recently in unique bot species not intended for battle.	+	This refers to the 10 [[in]] and [[out]] sysvar locations. The number stored at .out1, .out2 or another out can be read by any robot viewing the bot, with the value arriving at .in1, .in2 or another in respectively. These were in the past used for identification, and more recently in unique bot species not intended for battle.

	ID'ing non family with in/out:		ID'ing non family with in/out:

← Older revision		Revision as of 22:58, 6 July 2008
Line 1:		Line 1:
−	This refers to the [[~~.in1~~]], [[~~.in2~~]]~~, [[~~.~~in3]], [[.in4]], [[.in5]]~~ [[.out1]], [[.out2]]~~, [[.out3]], [[.out4]], [[.out5]] sysvar locations. The number stored at out1, out2~~ or another [[out]] can be read by any robot viewing the bot, with the value arriving at in1, in2 or another [[in]] respectively. These were in the past used for identification, and more recently in unique bot species not intended for battle.	+	This refers to the 10 [[in]] and [[out]] sysvar locations. The number stored at [[.out1]], [[.out2]] or another out can be read by any robot viewing the bot, with the value arriving at [[.in1]], [[.in2]] or another in respectively. These were in the past used for identification, and more recently in unique bot species not intended for battle.

	ID'ing non family with in/out:		ID'ing non family with in/out:

← Older revision		Revision as of 03:05, 2 March 2008
Line 10:		Line 10:

	An enemy bot can seem like family. Of course with randomly([[rnd]]) changing their value via [[inc/dec]] an enemy bot will waste [[Energy]] storing these.		An enemy bot can seem like family. Of course with randomly([[rnd]]) changing their value via [[inc/dec]] an enemy bot will waste [[Energy]] storing these.
		+
		+	But, you can ID bots by talking to them:
		+
		+	' if you see something, ask "Can I eat you?"
		+	cond
		+	*.eye5 0 >
		+	start
		+	1 .out1 store
		+	stop
		+
		+	' If they don't say No,
		+	' eat em
		+	cond
		+	*.eye5 0 >
		+	*.out1 1 =
		+	*.in2 2 !=
		+	start
		+	-1 .shoot store
		+	stop
		+
		+	' If Someone asks to eat you,
		+	' just say "No"
		+	cond
		+	*.eye5 0 >
		+	*.in1 1 =
		+	start
		+	2 .out2 store
		+	stop
		+
		+
		+	This DNA tells the bot: see something, put out1 1. If that thing doesn't put out 2, then eat it. And when something says 1, say 2.

	[[Robot DNA]]		[[Robot DNA]]

← Older revision		Revision as of 19:11, 13 February 2006
Line 1:		Line 1:
−	This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or ~~out2~~ can be read by any robot viewing the bot, with the value arriving at ~~out1~~ or ~~out2 respectivly~~. These were in the past used for identification, and more recently in unique bot species not intended for battle.	+	This refers to the [[.in1]], [[.in2]], [[.in3]], [[.in4]], [[.in5]] [[.out1]], [[.out2]], [[.out3]], [[.out4]], [[.out5]] sysvar locations. The number stored at out1, out2 or another [[out]] can be read by any robot viewing the bot, with the value arriving at in1, in2 or another [[in]] respectively. These were in the past used for identification, and more recently in unique bot species not intended for battle.

	ID'ing non family with in/out:		ID'ing non family with in/out:

← Older revision		Revision as of 06:24, 27 September 2005
Line 10:		Line 10:

	An enemy bot can seem like family. Of course with randomly([[rnd]]) changing their value via [[inc/dec]] an enemy bot will waste [[Energy]] storing these.		An enemy bot can seem like family. Of course with randomly([[rnd]]) changing their value via [[inc/dec]] an enemy bot will waste [[Energy]] storing these.
		+
		+	[[Robot DNA]]

← Older revision		Revision as of 06:21, 27 September 2005
Line 1:		Line 1:
−	This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or out2 can be read by any robot viewing the bot, with the value arriving at out1 or out2 respectivly.	+	This refers to the in1, in2, out1, out2 sysvar locations. The number stored at out1 or out2 can be read by any robot viewing the bot, with the value arriving at out1 or out2 respectivly. These were in the past used for identification, and more recently in unique bot species not intended for battle.

	A problem similar to the one facing bots using [[Memloc and Memval \|memloc/memval]] for identification is that with the simple code:		A problem similar to the one facing bots using [[Memloc and Memval \|memloc/memval]] for identification is that with the simple code: