> For the complete documentation index, see [llms.txt](https://docs.shrinefox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shrinefox.com/flowscript/atlusscriptcompiler/run-via-commandline.md).

# Run via Commandline

This method is the traditional way to use the compiler.

{% hint style="success" %}
For an even easier time, see how to [**Run via GUI**](/flowscript/atlusscriptcompiler/run-via-gui.md) (graphical user interface).\
If using that method, you can safely skip this page and the upcoming [**Compile**](/flowscript/atlusscriptcompiler/run-via-commandline/compile.md) and [**Decompile**](/flowscript/atlusscriptcompiler/run-via-commandline/decompile.md) sections.
{% endhint %}

## Usage

### Command Prompt

If you tried to run [**AtlusScriptCompiler**](/flowscript/atlusscriptcompiler.md) like a typical `.EXE`, the program would appear to quickly open and close without doing anything. That's because *commandline* programs must be run from the Windows Command Prompt**,** which we will shortened as "CMD" from here on out.

1. Press `Windows Key + R` and type `cmd`.
2. Press Enter.
3. Drag `AtlusScriptCompiler.exe` onto the CMD window,\
   OR\
   Type the full path to the program in the CMD. Wrap it in quotes in case any folder names contain spaces.
4. Press `Enter`.

Your CMD window should look like this:

```
Microsoft Windows [Version 10.0.22000.120]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Username>"C:\Path\To\AtlusScriptCompiler.exe"
```

At this point, the program should just spit out a list of **arguments** to use.

### Arguments

**Arguments** are the commands that *commandline* programs take as user input. \
You can type them after path to the program you're executing to tell it what to do. 

For instance, to [Decompile](/flowscript/atlusscriptcompiler/run-via-commandline/decompile.md) a Persona 5 `.BF` script, you'd type:

```
C:\Users\Username>"C:\Path\To\AtlusScriptCompiler.exe" "C:\Path\To\input.bf" -Decompile -Library P5 -Encoding P5 -Out "C:\Path\To\output.flow"
```

{% hint style="success" %}
By now, you know that AtlusScriptCompiler can [compile](/flowscript/atlusscriptcompiler/run-via-commandline/compile.md) `.FLOW` and `.MSG` files, and [decompile](/flowscript/atlusscriptcompiler/run-via-commandline/decompile.md) `.BF` and `.BMD` files. You're also acquainted with how to start the program. \
\
If not, start from [**Intro to Scripting**](/master.md).
{% endhint %}

To learn what each argument means, and which to use in different scenarios, keep reading.

{% content-ref url="/pages/-MgwkH0bTnsDEeeLeijr" %}
[Decompile](/flowscript/atlusscriptcompiler/run-via-commandline/decompile.md)
{% endcontent-ref %}


---

# 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://docs.shrinefox.com/flowscript/atlusscriptcompiler/run-via-commandline.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.