> For the complete documentation index, see [llms.txt](https://alham-rizvi.gitbook.io/alhamrizvi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alham-rizvi.gitbook.io/alhamrizvi/picoctf-writeups/picoctf/reverse-engineering/ready-gladiator-0.md).

# Ready Gladiator 0

In this challenge, we were given a remote service on picoCTF that accepts a Redcode program (Corewar).

Initially, we submitted a basic warrior:

```
mov 0, 1
```

This instruction continuously copies itself and behaves like a standard “imp” program, but it didn’t help us win the challenge.

After understanding the rules of Corewar, we realized that the goal was to make the opponent lose all rounds. Instead of trying to attack, we modified the instruction:

```
dat 0, 1
```

The `dat` instruction immediately terminates the process when executed. By doing this, our warrior instantly dies every round.

This may seem counterintuitive, but the challenge logic was designed such that losing all rounds triggers the success condition.

After submitting the modified code using:

```
nc saturn.picoctf.net 50002 < imp.red
```

We got the result:

* Warrior 1 wins: 0
* Warrior 2 wins: 100

This satisfied the challenge condition, and the flag was revealed.

#### Flag

```
picoCTF{h3r0_t0_z3r0_4m1r1gh7_e476d4cf}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://alham-rizvi.gitbook.io/alhamrizvi/picoctf-writeups/picoctf/reverse-engineering/ready-gladiator-0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.