From news-rocq!jussieu.fr!fu-berlin.de!news.netcologne.de!not-for-mail Fri Nov 12 17:57:30 1999 Article: 10968 of rec.games.corewar Path: news-rocq!jussieu.fr!fu-berlin.de!news.netcologne.de!not-for-mail From: "Screamer" Newsgroups: rec.games.corewar Subject: Lurker intrusion? :o) Date: Fri, 12 Nov 1999 15:29:02 +0100 Lines: 43 Distribution: world Message-ID: <80h8bv$gc2$1@news.netcologne.de> NNTP-Posting-Host: dial-ra-nc2-198.netcologne.de X-Trace: news.netcologne.de 942417087 16770 195.14.244.198 (12 Nov 1999 14:31:27 GMT) X-Complaints-To: usenet@news.netcologne.de NNTP-Posting-Date: 12 Nov 1999 14:31:27 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Xref: news-rocq rec.games.corewar:10968 Hi all, I've been lurking (on the mailing list) for quite a while now, and finally decided to write a couple "standard" warriors myself. I have so far no idea exactly how a quickscanner works, and no idea at all about stones other than that they are fast bombers. Are those dealt with in later Corewarrior issues? Or is there anything in some tutorial? I do know however how a silk-style paper works (which was explained in one of the first Corewarrior issues), so guess what - I wrote one, from scratch (it's been a while since I read any CW issue) :-) My problem is, I want a few pointers on how to make this a deadly, and without it becoming too suicidal. The current version works perfectly, and I guess as long as it doesn't go against a good quickscanner, it'll survive quite well. But err, what's the best option to actually *kill* instead of solely avoiding to get killed? Also, I'd like to make it die by itself after doing one or two copies, leaving dead decoys all over the place, therefor hopefully confusing quickscanners. Suggestions? Or isn't this a good idea, and I'd rather have it do something else against qscanners? And is there a two-instruction method for creating the three processes? I couldn't come up with any. And, oh, I know the step size is far from optimal - I just haven't read much on stepsizes, so I just took the first evil number that came to mind . So, here goes: ;redcode ;name Silkysmooth ;author Aristoteles Pagaltzis ;assert 1 start SPL 2 JMP 2 SPL 1 ptr SPL 666, #0 MOV.i >ptr, }-1 JMP -2,