[03:54] Join: Caelian_ joined #corewars [03:58] MSG: Ping timeout: 252 seconds [08:07] note: sdl-pmars doesnt like my laptop's keyboard [11:25] Join: Core_new_ joined #corewars [13:13] MSG: Ping timeout: 252 seconds [13:36] MSG: Quit: Ex-Chat [14:58] Join: Metcalf joined #corewars [14:59] Hi :-) [15:07] MSG: Ping timeout: 252 seconds [15:07] Join: Metcalf joined #corewars [15:12] MSG: Ping timeout: 252 seconds [15:47] Join: Metcalf joined #corewars [15:52] MSG: Ping timeout: 252 seconds [15:55] Join: raptor joined #corewars [15:55] anyone alive?! [16:43] Join: Core_new_ joined #corewars [16:58] Join: Caelian joined #corewars [16:58] anyone awake? [16:59] * pak21 is awake (but about to leave) [16:59] hi phil [17:28] MSG: Quit: ChatZilla 0.9.79 [Firefox 2.0.0.6/2007072518] [17:42] well, about 10 minutes late [17:42] oh well [17:58] "France is a country you have to drive through to get to Italy" [18:00] Join: fiveop joined #corewars [18:13] Join: daxxar joined #corewars [18:13] hi there [18:14] Hi :-) [18:14] Nick Change: daxxar changed nick to jorgenpt [18:14] how may i be of assistance? [18:16] hi [18:16] Nothing in particular, just curious [18:17] So, is the corewars community dead and buried? ;-) [18:17] in hospital bed and high on pills, but still trying [18:19] main reason is that people are simply not interested in such "program fighting" [18:19] gridwars had members only because HP sponsored hardware [18:20] the programwars of today are done with irc-wars and crappy amateur-zombienetworks [18:21] and what new has virii brought recently? Storm doesnt count since it was "professionally" coded [18:21] end rant [18:23] Storm worm? [18:23] aye [18:24] Anyway, I guess Core wars is a bit .. "done". Most good strategies have been found and implemented. :-) [18:24] And asm has a steep learning curve. ;) [18:25] quite true [18:25] actually, i know redcode quite well, but i am actually crap at "real" coding and i dont know any ASM [18:25] Hehe ;-) [18:25] I know a couple of kinds of asm (but mostly x86) and a bunch of other languages [18:26] (well, i will be having microprocessors next year or two in school) [18:26] x86 asm is easily understood in comparsion to redcode :/ [18:26] Cool, had a bit microprocessors this year [18:27] I read something about "The Scriptarians" on the Core Wars wikipedia, but didn't really like it [18:28] And wasn't even close to the concept of Core Wars. ;P [18:28] "fully 3D enviroment with fantasy graphics" [18:28] cheesus christ what crap [18:28] Don't try it [18:28] It feels very unfinished too :P [18:30] considering lot of people bruteforce-optimize warriors, the last thing you want in corewars is complicated graphics [18:34] but, if you want more opinions, feel free to ask, i feel like ranting again so id better calm down [18:35] maybe ive had too much caffeine today [18:36] Hehe ;P [18:37] Coffee and galliano here [18:39] MSG: Quit: humhum [18:40] Playing scrabble with a couple of friends, enough of a intellectual game for me today. Perhaps toy a bit more with core wars tomorrow. :) [18:46] (actually, storm didnt bring anything new to Virii either, double encryption - done. Antidebug - done. p2p - done. changing signature - done.) [18:50] double encryption? [18:50] it had two layers of encryption on top of each other [18:50] Oh, ok. [18:57] Join: Metcalf joined #corewars [18:58] Hi :-) [18:58] hi Met [18:58] feel free to try to persuade jorgen to join the world of CW [19:00] Hi Mizcu [19:05] after I've eaten :-P [19:05] ;-) [19:18] Have you done any assembly programming jorgenpt? [19:19] Just reading the logs. Which processors apart from 80x86? [19:24] Some AVR 8bit stuff [19:27] Have you looked at some redcode yet? [19:30] I've read the guide at http://vyznev.net/corewar/guide.html [19:31] That's a good place to start, does it make any sense? [19:34] Yeah, it does [19:34] The various modifiers are kinda strange [19:34] Like post-decremenet indirect B [19:35] MSG: Ping timeout: 252 seconds [19:36] modifiers are the thing that messes up every beginner [19:36] Join: Metcalf joined #corewars [19:38] http://corewar.atspace.com/top10.html [19:39] Have you found the beginners hill? [19:39] The best way to learn it to try stuff out, then try to improve it :-) [19:40] Met, i said "presuade", not "assist", there is a slight difference of interpretion [19:46] Where's hte beginners hill? [19:46] the* [19:50] http://sal.math.ualberta.ca/hill.php?key=94b [19:50] simply send your warrior by email to with a header of ;redcode-94b [19:55] So how're the hills recalculated when something is submitted? [19:56] the score shown is the average the warrior scores against each of it's opponents [19:57] a program with battle against each of it's opponents a few hundred times. 3 points for a win, 1 point for a draw [19:57] Then an average is taken, and scaled into the range 0-300 [19:58] 0 = 100% losses, 300 = 100% wins [19:58] 100 = 100% draws (or 33.3% wins, 66.6% losses - or some other combination) [19:59] So that's run instantly when you submit? [19:59] Also, how're memory locations (initial for programs) decided? [19:59] How's "age" decided? [20:00] Each time a new warrior enters the hill, each warrior on there gets +1 age [20:01] The average age should be approx the same as the number of spaces on the hill (normally 20 or 25) [20:01] the running is done, at sal, immediately after submission [20:01] However some warriors are really successful :-) [20:01] on koth, itll take 5-15 minutes [20:02] The most successful warriors ever are at - http://corewar.co.uk/alltime.txt [20:03] Ok. :-) [20:03] What's the difference between beginners hill and the other hillps? [20:03] hills [20:03] technically there is no difference, other than beginner hill has a maxage [20:03] Different settings [20:04] beginner hill = 8000 coresize [20:04] well, beginner hill uses "standard" settings with maxage [20:04] but there's nano hill, coresize 80 - tiny hill, coresize 800 - big hill, coresize 55440 [20:05] What's the max age [20:05] 50 [20:05] ok [20:06] Once you get into the top half of the beginner hill, you should try sending your warrior to the multi-warrior hill [20:06] if you check the b-hill, youll just see that 'hosenscheisser' was dropped because of age, not because of scoring [20:07] "Killed" means? [20:07] on multi-warrior all warriors fight at the same time instead of one-on-one [20:07] killed = stop all of the opponents processes [20:08] they stop when the execute a DAT [20:08] No, I mean "killed" from the hill [20:08] intentionally removed from the hill by sender [20:08] Oh :-) [20:08] or age? [20:08] Back later :-) [20:08] * Metcalf waves [20:08] MSG: Quit: mov.i #1,1 [20:09] jorgen: well, technically "killing" means setting score of a warrior so low that sending anything will cause the "killed" warrior to drop from the hill [20:10] comes from the fact that it is done by sending mail with ;kill warriorname to the hill [20:48] Join: Yey joined #corewars [20:51] hi Neo [20:52] hi Miz [20:53] Nick Change: Yey changed nick to Neogryzor [20:59] *blink* [20:59] i just went for a leak, thought for one minute and realized why a project of mine just failed [21:01] hidden in plain sight [21:01] :) [21:08] _-_-_-_-_-_-_ [21:09] you know the silk-dwarf; when running, the processes go spl spl spl spl | spl mov spl mov spl mov spl mov | spl mov add spl mov add spl mov add [21:11] but if i put a cannonade-stone there, it goes mov mov mov | mov spl mov spl mov spl | mov add spl mov add spl mov add spl [21:12] nothing really gained, and it only uses even more messed up process-loop [21:14] i hate silk-imps, you need non-paraller processes to run a stone effectively, which in part messes up the replication [21:15] not silk-imps, i have a hate-love-relationship with them, silk-dwarfs was meant to write [21:17] there is something you can do [21:17] i tested an idea long ago but didn't develop it much [21:18] launch two parallel papers [21:18] one using mov/add and the other add/mov for bombing [21:18] add.ab #step, paper1step-paper2step? [21:19] the add adds the step for the other paper [21:19] but papers must have same psteps. [21:19] yeah, more or less [21:20] well, that addmov/movadd is "one generation" faster than netpaper-style [21:34] randopunched constants say 106 wilfiz, so needs some more work [21:42] hmm, it bombs quite acceptable early-game, if you dont mind slightly lazy replication [21:42] but i am bit puzzled about end-game [21:46] but nighty-night [21:55] Join: Metcalf joined #corewars [21:55] Hi :) [21:56] MSG: Quit: Trillian (http://www.ceruleanstudios.com [21:56] Hi John :) [21:57] are you using loop Miz, or just replicating? [22:02] Join: OoS joined #corewars [22:03] MSG: Ping timeout: 252 seconds [22:04] Nick Change: OoS changed nick to Metcalf [22:20] MSG: Ping timeout: 252 seconds [22:20] Join: Metcalf joined #corewars [22:28] MSG: Ping timeout: 252 seconds [23:58] MSG: