History of LunarTwins

Robo Home | Changes | Preferences | AllPages

	Revision 77 . . May 9, 2008 22:04 EST by Rednaxela [Scan sharing thoughts]
	Revision 76 . . May 9, 2008 19:56 EST by Voidious [comment on scan sharing]
	Revision 75 . . May 9, 2008 18:36 EST by Rednaxela [Scan sharing difficulties]
	Revision 74 . . May 9, 2008 14:37 EST by ABC [what's keeping you from releasing bots to the rumble(s)?]
	Revision 73 . . May 9, 2008 0:19 EST by Rednaxela [Er, Whoops... Fixed results with latest Shadow]
	Revision 72 . . May 9, 2008 0:02 EST by Rednaxela [Sure! Here it is using the latest Shadow]
	Revision 71 . . May 8, 2008 23:35 EST by ABC [impressive]
	Revision 70 . . May 8, 2008 22:00 EST by Rednaxela [LunarTwins 1.2 vs ShadowTwins]
	Revision 69 . . April 22, 2008 7:15 EST by Rednaxela [Patternmatching]
	Revision 68 . . April 20, 2008 4:26 EST by Rednaxela [LunarTwins 1.2]
	Revision 67 . . (edit) March 11, 2008 2:38 EST by Rednaxela [fix typo]

Difference (from prior major revision) (no other diffs)

Added: 269a270,271

Hmm that is interesting. Well, converting back to a SRE isn't really what my issue is. My issue is more to do with making my code able to handle receiving the 1-tick-old shared data, and ignore it when it already got that scan itself last tick, etc. It wouldn't be so so bad if my code wasn't making some assumptions that either location is either brand new or completely out of date. About usefulness of it: Well, some of my plans of how to best adapt LunarTwins tactics to a 5v5 setting, do require all of my robots to have the identical knowledge of enemy locations according to the scans last tick in order to cooperate as I intend ;) -- Rednaxela