[09:57] Join: fiveop joined #corewars [14:59] Join: John joined #corewars [14:59] Hi :-) [15:01] h [15:02] Hi Mizcu [15:16] so, C -compiler finds no errors yet our sort of Java-helpprogram for homework on 'net thinks my code sucks. [15:19] :-/ [15:20] ugh, found the reason [15:33] Join: Fizmo joined #corewars [15:33] hi [15:33] that is not fun what happenes on 94draft [15:33] ..... [15:34] anyway [15:36] my head i going to cave in [15:37] Hi Fizmo [15:37] I don't think he's a newby, the warriors are choosen too well [15:37] most likely from Koen [15:38] anyway if Mr. Hugh J ass is happy with that [15:42] Join: Fizmo_ joined #corewars [15:44] i assure you, i want to kill the people who make these C-"home"works for us [15:44] MSG: Ping timeout: 240 seconds [15:44] Nick Change: Fizmo_ changed nick to Fizmo [15:45] Now, i know that a teacher is not going to nitpick about missing space, or missing \n from end of the last output, but this "teaching software" is fucking nitpicker [15:46] why am i now pissed off? because work requires to output "1 2 3 4 5 6 7 8 9\n" [15:46] which is not the same as "1 2 3 4 5 6 7 8 9 \n" [15:48] isn't it? [15:49] * John waves [15:50] because in second case i can treat all the letters the same, and after one line has been done, i just throw \n and go on to next [15:50] but now i have to loop 8 times and then treat 9 as special case because it doesnt have the space after [15:50] letters, numbers, grmbl [15:50] MSG: Quit: mov.i #1,1 [15:52] MSG: Ping timeout: 240 seconds [15:57] ohh, I see [15:59] well, i got it fixed and now it gives an error that shouldnt exist [15:59] oh well, ill take a break [16:01] Join: johnkw joined #corewars [16:05] Join: Fizmo_ joined #corewars [16:05] MSG: Client Quit [16:07] MSG: Ping timeout: 240 seconds [16:55] :) [16:57] Mizcu: I see that you are having fun with C :) [17:07] Join: Core_old joined #corewars [17:29] MSG: Ping timeout: 240 seconds [18:12] Join: Core_old joined #corewars [19:36] Join: A-law joined #corewars [19:48] Hi A-law :) [19:48] hey there :) [19:52] just idling a bit to see what's new on koth ^^ [19:58] Some newbie seems to think that using handshaking warriors to take over the '94-draft-hill is a good idea :( [20:00] what means handshaking in this context? do they recognize each other? [20:01] you can use P-Space to communicate between different warriors [20:02] if you send several warriors to a hill with P-space you can make sure take all your other warriors die against the warrior that you want to make koth [20:02] you can even take over a complete hill with that [20:02] the '94xm-hill is filled with such warriors [20:03] and breaking that handshake is a little bit difficult [20:03] oh, but that's only possible on a multiwarrior hill, right? [20:03] no, you can make that on every hill with p-space [20:04] thought p-space is private [20:04] It was a nice idea, but using it no longer proves anything :( [20:04] Yes, it is private, but if you give your warriors all the same PIN the will use the same p-space [20:05] *they [20:06] oh, that's new to me .. thought it would only work in a multiwarrior environment, where it makes sense ^^ [20:07] just send two of your own warriors with the same PIN and that's it ;) [20:09] so all of the standard 94' draft hills allow PIN? [20:09] every except the 94nop-hill [20:10] but on nano it is of no use [20:10] *speechless* [20:11] 5 instructions aren't just enough to use it properly [20:11] what about brute-forcing PINs? [20:11] not that it makes any sense ^^ [20:12] well ... you only need to send about 8000 mails to get the PINS of all warriors on the hill [20:13] but knowing them doesn't mean you can beat them :) [20:17] hehe true [20:20] why isn't the PIN command invalidated then? [20:22] huh? [20:23] i meant why are there hills still using PIN? can't be to hard to disable it [20:23] too* [20:24] meh [20:24] there is nothing wrong with P-space, you can use it for other purposes [20:25] i don't mean the p-space per-se but only p-space identification. [20:26] you mean to prevent handshaking? [20:27] partly. is there any other use than communicating with other warriors? [20:27] no [20:28] doesn't make sense to me in a non-multiwarrior scenario [20:28] that's why [20:28] to have p-space? [20:29] no, communication with other warriors then oneself through p-space [20:30] the original idea was to make it possible to keep track of how often you've won/lost and to changed your strategy upon the results [20:30] handshaking wasn't planned exist [20:31] at least not in that way (I think) [20:32] http://www.koth.org/planar/corewarrior/071.txt [20:33] if you look at the results for the '94 hill then, you'll see it wiped by handshaking warriors [20:34] http://www.koth.org/planar/corewarrior/020.txt contains a description of how handshaking works [20:34] hmmm [20:35] i thought if i don't use PIN i still can keep track of how often i've won/lost etc. [20:36] how? you can send information from one round to the next without p-space [20:36] how would you do that? [20:36] erm [20:37] you *can't* [20:37] maybe I should actually read what I've written ;) [20:38] ^^ i meant with a REALLY private p-space that should be possible and from what i've read if you don't use the PIN opcode your p-space is really private [20:38] yes, that's right [20:39] so disabling the PIN pseudo opcode would prevent any trouble caused by communicating warriors, no? [20:40] I think so [20:40] i don't see any other purpose of that opcode [20:41] imo it makes only sense to discriminate teams on a xm hill [20:42] MSG: Ping timeout: 240 seconds [20:44] brb [20:44] :) [22:03] Join: John joined #corewars [22:03] Hi :-) [22:03] hi john ^^ [22:03] Hi A-Law [22:03] Just a quick visit [22:05] okiedo, i won't be long online anymore too .. just getting ready for counting fluffy sheepies ^^ [22:07] :-) [22:08] suddenly something interesting happens in this channel ..... not :) [22:56] MSG: Quit: *p00f* [23:02] * John waves [23:02] MSG: Quit: mov.i #1,1 [23:58] MSG: Quit: Lost terminal