From news-rocq.inria.fr!jussieu.fr!mathserv.mps.ohio-state.edu!howland.erols.net!EU.net!newsfeed.internetmci.com!in1.uu.net!news.new-york.net!news.stormking.com!iltzu@sci.fi Fri Oct 25 14:13:20 1996 Article: 6356 of rec.games.corewar Path: news-rocq.inria.fr!jussieu.fr!mathserv.mps.ohio-state.edu!howland.erols.net!EU.net!newsfeed.internetmci.com!in1.uu.net!news.new-york.net!news.stormking.com!iltzu@sci.fi From: iltzu@sci.fi (Ilmari Karonen) Newsgroups: rec.games.corewar Subject: Re: Sandstorm Q/0.4 Date: 24 Oct 1996 18:24:50 -0400 Organization: Storm King Ind. Inc. Lines: 78 Sender: server@news.stormking.com Distribution: world Message-ID: <24199603.Amiga@sci.fi> Reply-To: iltzu@sci.fi NNTP-Posting-Host: valhalla.stormking.com Originator: corewar-l@stormking.com X-Mailer: Air Mail V2.0 (Unregistered) -- Amiga Mailer by Danny Y. Wong Justin Kao wrote: > >;strategy Justin: I used this name first =) > > Oops... extenuating circumstances--I don't believe I had a warrior on the -94 > hill during Sandstorm's lifetime, at least I don't remember it. Well, IIRC Sandstorm 0.1 alone never made it even to the b-hill for more than a few challences. I used it mostly as a p-component in Together 0.3. So it's really no wonder you never noticed it. > May I guess at your rationale behind the name...(at least this is why I chose > it, which later turned out not to fit my warrior) It is much like a sand storm > in that it throws lots of little stones which may not kill individually, > but with so many coming at such a fast rate..... Well, that did come to my mind, too. Also, the original code was tuned to color the core as fast as possible, to stop scanners from eating my other p-components alive, that is to reduce the visibility. The third reason was that I checked Planar's archive, and all the other good names I could think of were already in use. =) > >b1 mov.i }hit1, >hit2 > > add.f incr, b2 > >b2 mov.i }hit1+step, >hit2+step > > For many things, isn't the b field pointing to a pointer or destination of a > bomb? Then this really wouldn't hurt it much, 'cause the executing code > wouldn't be bombed. Hmm.. never really thought about it. Changing it would ruin my fancy self-bombing system, unfortunately. :( Maybe I could change just one of the MOVs.. Also, changing it to predecrement would allow me to color core a bit faster. Hmm.. =) OABTW, here's a version of a fused imp spiral I've been developing. It's loosely based on Impfinity, and has the nice feature that the fuse is included in the launch, taking no extra space or cycles. ;redcode-94 ;name imptest 0.2 ;version 0.2 ;kill imptest ;author Ilmari Karonen ;strategy try a new kind of imp launch ;history 0.1 - Just a continuous vector-launched imp. ;history 0.2 - Self-priming jmp/add launch. ;date October 23, 1996 ;planar imp ;assert CORESIZE == 8000 org pump impstep equ 7579 ; imp step fuselen equ 190 ; imp size point equ (imp+1-18*(impstep+1)) ; imp start ; *** Imp launch pump spl 0, >prime prime mov.i imp, point-1 add.f #impstep+1, ptr ptr jmp point-impstep-1, {pump-fuselen+3 imp mov.i #impstep, *0 end It launches a 19 point, 190 process imp spiral. The speed of an imp is speed=points/processes, so this one has a speed of 19/190=0.1c, just enough to make it around the core. Kills scanners pretty well.. The launch has a small bug, which leaves a 'flaw' in the front end of the spiral. Fixing it is left as an exercise for the reader. ;) -- Ilmari Karonen