|
|
@ -26,6 +26,16 @@ Here's a quick list of what they are and what they do. |
|
|
|
|
|
|
|
> Makes a console appear with log information at startup. |
|
|
|
> |
|
|
|
> Optionally, an explicit process ID can be specified to start the game with an external console. This allows it to be |
|
|
|
> launched via Steam without being interrupted by its "Allow game launch?" if launched directly from the `.exe`. |
|
|
|
> |
|
|
|
> Example for Beat Saber using PowerShell: |
|
|
|
> |
|
|
|
> ``` |
|
|
|
> .\steam.exe -applaunch 620980 --verbose $PID |
|
|
|
> ``` |
|
|
|
> |
|
|
|
> Do note that this isn't going to work from an elevated terminal. |
|
|
|
|
|
|
|
- `--debug` |
|
|
|
|
|
|
@ -35,15 +45,13 @@ Here's a quick list of what they are and what they do. |
|
|
|
> This option also forces BSIPA to show all debug messages in the console, as well as where they were called. |
|
|
|
> |
|
|
|
> This overrides the config settings `Debug.ShowDebug` and `Debug.ShowCallSource`. |
|
|
|
> |
|
|
|
|
|
|
|
- `--trace` |
|
|
|
|
|
|
|
|
|
|
|
> Enables trace level messages. By default, they do not ever enter the message queue, and thus cost almost nothing. |
|
|
|
> When this or the config option is used, they are added and logged with the same rules as Debug messages. |
|
|
|
> |
|
|
|
> This overrides the config setting `Debug.ShowTrace`. |
|
|
|
> |
|
|
|
|
|
|
|
- `--mono-debug` |
|
|
|
|
|
|
@ -53,7 +61,6 @@ Here's a quick list of what they are and what they do. |
|
|
|
> debugger server running on port 10000 on `localhost`. |
|
|
|
> |
|
|
|
> Implies `--debug`. |
|
|
|
> |
|
|
|
|
|
|
|
- `--server` |
|
|
|
|
|
|
@ -62,7 +69,6 @@ Here's a quick list of what they are and what they do. |
|
|
|
> When paired with `--mono-debug`, this option makes the Mono soft debugger act in server mode. It begins listening on |
|
|
|
> port 10000 on any address, and will pause startup (with no window) until a debugger is connected. I recommend using |
|
|
|
> SDB, but that is a command line debugger and a lot of people don't care for those. |
|
|
|
> |
|
|
|
|
|
|
|
- `--no-yeet` |
|
|
|
|
|
|
@ -73,7 +79,6 @@ Here's a quick list of what they are and what they do. |
|
|
|
> behaviour is disabled. |
|
|
|
> |
|
|
|
> Overrides the config setting `YeetMods`. |
|
|
|
> |
|
|
|
|
|
|
|
- `--condense-logs` |
|
|
|
|
|
|
@ -85,11 +90,11 @@ Here's a quick list of what they are and what they do. |
|
|
|
> Overrides the config setting `Debug.CondenseModLogs`. |
|
|
|
|
|
|
|
- `--plugin-logs` |
|
|
|
|
|
|
|
|
|
|
|
> Causes each plugins' log messages to be written to files in their own folder for ease of debugging. |
|
|
|
> |
|
|
|
> This was the default through 4.1.6, however is now disabled by default. |
|
|
|
> |
|
|
|
> Overrides the config setting `Debug.CreateModLogs`. |
|
|
|
|
|
|
|
|
|
|
|
*** |