Why convert LOBSTER to LPAK?
An .lpak (Lobster Program Archive) lets you ship a Lobster program as just the executable plus one pak file, with all assets packed together. It keeps distribution simple by collapsing every data file you flagged into a single archive.
How to convert LOBSTER to LPAK
Lobster (--pak) OPEN-SOURCE
Run lobster --pak mygame.lobster to generate default.lpak in the same folder. This version omits runnable code and pairs with an executable built via --cpp.
Lobster (--rpak) OPEN-SOURCE
Run lobster --rpak mygame.lobster to build default.lpak that also includes runnable code, which is what you want when running in JIT mode.
About these formats
A .lobster file holds source code written in the Lobster programming language, a statically typed language with Python-like indentation created by Wouter van Oortmerssen and aimed mainly at…
Open .LOBSTER details →A .LPAK file is a data file used by specific software.
Open .LPAK details →Quality & what to watch
- The output is always named
default.lpakand lands next to the source file, so rename it yourself if you need a different name. - Only files you marked with the
pakfilekeyword (plus code) are included - arbitrary assets aren't packed automatically. --pakand--rpakdon't run the program; they only produce the pak, so pick--rpakif the pak itself must be runnable.
Frequently asked questions
What is the difference between --pak and --rpak?
--rpak includes runnable code in the pak (for JIT runs), while --pak leaves it out for use with a --cpp-built executable.Can I choose the output file name?
default.lpak beside the .lobster file, so rename it afterward if needed.What goes inside the .lpak?
--rpak) and any data files you specified with the pakfile keyword, bundled into one archive.Does building a pak also run my program?
--pak and --rpak generate the pakfile and stop without executing the program.