What are user scripts?

User scripts will be executed similar to bash or console commands. You can run any compiler and / or emulator in the same way you would do when calling these tools from the console or a batch file.

You can define several actions that should be executed. Use multiple lines in your script to define multiple actions.

Adding new scripts

To add a new script, simply change the script name (in the related text field). Once you changed the script name, the apply-button's text will change to Add script. Edit the script in the text area below and add the script by clicking on the button.

If you press the New Script button, all fields will be cleared and you can enter script name and script lines.

Updating existing scripts

To change or update an existing script, simply select the script from the dropdown list, but do not change the script name (in the related text field). Edit the script in the text area below and save the changes by clicking on the button Update script.

Placeholders

To specifiy directories or input and output files, there are following constants that should be used:

Note 1: In some cases you may have to add the "open" command to the command line (e.g., on OS X, starting Vice will throw an access denied error without the open-parameter). See examples below.

Note 2: If you specify full pathes to your compiler or emulator and the path contains whitechars (spaces), you need to set the path in quotes (see examples below). Placeholders like SOURCEFILE or OUTFILE, however, will be automatically quoted if necessary. You don't need to quote the placeholders.

Note 3: To make use of the START placeholder, you have to specify the start address in a comment line with following syntax:
<comment sign> start=<start address>, for instance:
// start=$c000 (for Kick Assembler)
; start=12288 (for ACME)

Drag & Drop

You can drag & drop executables from compilers, crunchers and emulators from the explorer (or file browser) window onto the script text field. Relaunch64 will then automatically generate a proper scriptline, including recommended parameter settings (in case the compiler, cruncher or emulator is recognized and supported).

Examples

Using KickAss and Vice on OS X

java -jar /<path to kickass>/KickAss.jar SOURCEFILE
open /Applications/Vice/x64.app OUTFILE

ACME and Vice, when ACME- and VICE-Path are in PATH-Environment

acme -v4 SOURCEFILE
x64 OUTFILE

ACME and Vice, when ACME-Path is in PATH-Environment (Vice is not)

acme --outfile OUTFILE --format cbm SOURCEFILE
"C:\Users\Luedeke\Documents\C64\WinVICE 2.4\x64.exe" OUTFILE

Using KickAss and Vice on Windows

java -jar C:\Users\Luedeke\Documents\C64\KickAss\KickAss.jar SOURCEFILE
C:\Users\Luedeke\Documents\C64\WinVICE-2.4\x64.exe OUTFILE

Using ACME, Exomizer and Vice, with white space in path

"C:\Users\Luedeke\Documents\C64\sontige tools\acme 0.9\acme.exe" --outfile OUTFILE --format cbm SOURCEFILE
C:\Users\Luedeke\Documents\C64\Exomizer\exomizer.exe sfx basic UNCOMPFILE -o COMPFILE
C:\Users\Luedeke\Documents\C64\WinVICE-2.4\x64.exe COMPFILE