mirror of
https://github.com/open-goal/jak-project.git
synced 2024-10-20 11:26:18 -04:00
a0a85eb60a
- You can define a `startup.gc` in your user folder, each line will be executed on startup (deprecates the usefulness of some cli flags) - You can define a `repl-config.json` file to override REPL settings. Long-term this is a better approach than a bunch of CLI flags as well - Via this, you can override the amount of time the repl will attempt to listen for the target - At the same time, I think i may have found why on Windows it can sometimes take forever to timeout when the game dies, will dig into this later - Added some keybinds for common operations, shown here https://user-images.githubusercontent.com/13153231/202890278-1ff2bb06-dddf-4bde-9178-aa0883799167.mp4 > builds the game, connects to it, attaches a debugger and continues, launches it, gets the backtrace, stops the target -- all with only keybinds. If you want these keybinds to work inside VSCode's integrated terminal, you need to add the following to your settings file ```json "terminal.integrated.commandsToSkipShell": [ "-workbench.action.quickOpen", "-workbench.action.quickOpenView" ] ``` |
||
|---|---|---|
| .. | ||
| jak1_jp | ||
| jak1_ntsc_black_label | ||
| jak1_pal | ||
| jak1_sced | ||
| jak2 | ||
| jak3 | ||
| all-types-demo.gc | ||
| all-types.gc | ||
| jak1_jp.jsonc | ||
| jak1_ntsc_black_label.jsonc | ||
| jak1_pal.jsonc | ||
| jak1_sced.jsonc | ||
| jak1_us2.jsonc | ||
| jak2_ntsc_v1.jsonc | ||
| jak3_ntsc.jsonc | ||