Skip to content
This repository has been archived by the owner on Aug 13, 2018. It is now read-only.

Latest commit

 

History

History
91 lines (53 loc) · 3.63 KB

README.md

File metadata and controls

91 lines (53 loc) · 3.63 KB

Corewar

This is a group project: 4 people.

Our team: opavliuk, tkiselev, ysamchuk, tkuhar.

Project of UNIT Factory (école 42)

What is Corewar?

• Corewar is a very peculiar game. It’s about bringing “players” together around a “virtual machine”, which will load some “champions” who will fight against one another with the support of “processes”, with the objective being for these champions to stay “alive”.

• The processes are executed sequentially within the same virtual machine and memory space. They can therefore, among other things, write and rewrite on top of each others so to corrupt one another, force the others to execute instructions that can damage them, try to rewrite on the go the coding equivalent of a Côtes du Rhône 1982 (that is one delicious French wine!), etc...

• The game ends when all the processes are dead. The winner is the last player reported to be “alive”.

Wikipedia ("Core War"): https://en.wikipedia.org/wiki/Core_War

Breakdown of the project’s objectives

This project can be broken down into three distinctive parts:

The assembler: this is the program that will compile your champions and translate them from the language you will write them in (assembly language) into “Bytecode”.Bytecode is a machine code, which will be directly interpreted by the virtual machine.

The virtual machine: It’s the “arena” in which your champions will be executed. It offers various functions, all of which will be useful for the battle of the champions. Obviously, the virtual machine should allow for numerous simultaneous processes; we are asking you for a gladiator fight, not a one-man show simulator.

The champion: This one is a special case. Later, in the championship, you will need to render a super powerful champion, who will scare the staff team to death. However, rendering this kind of champion is serious work. And since, for now, we are mostly interested in your capacity to create Corewar’s other programs (i.e. the assembler and virtual machine), your current champion will only need to prove to us that you can write bits and pieces of Corewar ASM. This means that the champion you should render for this project only needs to scare the bejesus out of a neurasthenic hedgehog.

Our Bonuses:

We made some cool bonuses:

Disassembler: our assembler has flag '-b' which retranslates back your champions from Bytecode into assembly language.

Info about champion: our assember has flag '-a' also, which reads champions assembly file and shows you all information about champions (name, comment, commands: opcode, codage, bytes).

Network Game Mode: our corewar has flags '-s' (server) and '-c' (client)! '-s' flag allows you to create a server and other clients (from another computer, on the local network, which have the IP address of the server), through '-c' flag, can send their best champions and watch the battle on their computers.

Usages



Visualizer