" %}
### Using your own command line arguments
RetroBat allows for using your own command line arguments with the emulator.
To do so, create a .txt file and fill one argument per line:
Save the file with the ".uzdoom" or ".gzdoom" extension and place it in the `roms\doom` folder.
### Running mods
The method above also allows you also to start modded games.
To do so, precise which game the mod will use (the mian iwad file), and which mod you want to start (pwad games), with the full path to the different files.\
\
An exemple, using "10 sectors" mod :\
\
\
\
then, starting the games using the file `"10sector.gzdoom"` will start the according mod.
{% hint style="info" %}
To cumulate multiple mods, just add lines to the file with the paths to the other mods to launch.
{% endhint %}
### File organization (PRBoom)
PrBoom can load wad, iwad, and pwad files.
WAD and IWAD files are "`Internal Where's All the Data`" files, meaning they are used to run the game.
PWAD files are patches, they need the main game WAD/IWAD file to run.
Hereunder is the recommendation for the organization of your prboom folder:
└── roms\
└── doom\
├── doom\
│ └── doom.wad
└── doom 2\
│ └── doom2.wad
└── Doom Ultimate\
│ └── doomu.wad
If you are going to use pwad files, they will have to be placed in a subfolder inside the main wad game folder:
└── roms\
└── doom\
├── doom\
│ └── doom.wad
│ └── Episode 5 - Sigil\
│ └── SIGIL.pwad
└── Doom 2\
└── doom2.wad
└── Goldeneye\
└── goldeneye.pwad
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.retrobat.org/systems-and-emulators/supported-game-systems/others/doom.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
