Core War
11–20 of 53 posts
Re: Core War
#12Earlier quoted context omitted.
Does it really? https://www.corewar.io/app/editor/src
Yes, it works. However, the site is .. odd. I'm not sure what triggers it, but if I visit the page from a link on the site, it works, but if I visit that link from your link, it doesn't. Except now, now they both work. Some odd caching artifact? Not sure.
Re: Core War
#13Earlier quoted context omitted.
Does it really? https://www.corewar.io/app/editor/src
Yes, it works. However, the site is .. odd. I'm not sure what triggers it, but if I visit the page from a link on the site, it works, but if I visit that link from your link, it doesn't. Except now, now they both work. Some odd caching artifact? Not sure.
Re: Core War
#14I remember having a few good afternoons of fun with Core War as a teenager back in the day (I probably found an implementation on a shareware/freeware CD). But while that made me understand the tradeoffs of some of the common strategies mentioned on this wiki page pretty well, getting into the (often entirely uncommented) complex red code of some of the winners wasn't something I was too keen on doing without at least some description.
Re: Core War
#15Take last year's winners. Translate. Profit.
Re: Core War
#16The first question on my mind : is it feasible to translate redcode to regular assembly? Take last year's winners. Translate. Profit.
Re: Core War
#17Re: Core War
#18Re: Core War
#19Re: Core War
#20The first question on my mind : is it feasible to translate redcode to regular assembly? Take last year's winners. Translate. Profit.
What do you mean, "profit" how? Regular assembly works in a very different environment, and the code is much less constrained (and more low level). Even if your goal is to just crash/overwrite some other code in the same address space, you don't really need to employ any of the core war strategies, and the code you target also won't "fight back".