Added --fused command line argument, to simulate fusing.
Pardon my ignorance, but is there anyone to explain in simple terms to me what is "fusing" ?
And on the top of that, what are the benefits of such a feature ?
I believe fusing is when you fuse a .love file into the LÖVE executable.
From the Wiki on Game Distribution:
Windows
To create your game executable under windows use the command line to run
copy /b love.exe+SuperGame.love SuperGame.exe
Alternatively you can create a .bat (e.g. create_game_exe.bat) file with the contents
copy /b love.exe+%1 "%~n1.exe"
and then you can simply drag your SuperGame.love file onto the .bat file and it will create the file SuperGame.love.exe which you could then use for distribution.
IIRC the save dir is created outside of /love/. There may be other things, but I'm not sure. Maybe it also shows the release error screen instead of the default one?
IIRC the save dir is created outside of /love/. There may be other things, but I'm not sure. Maybe it also shows the release error screen instead of the default one?
That's what t.release is for.
PM me on here or elsewhere if you'd like to discuss porting your game to Nintendo Switch via mazette! personal page and a raycaster
Fused mode normally happens when the game is fused to the love executable. In 0.9.0 you can also start a love game by launching it with the '--fused' command-line option to simulate fusing.
Fused games create their save folders directly in the appdata folder, rather than in appdata/LOVE/. They're also able to load Lua .dll/.so files via require when the files are inside the game's save directory.
In 0.8.0, I think the changes which happen when the game is fused are only applied if release mode (t.release=true in love.conf) is also enabled. In 0.9.0 this is no longer the case because release mode is removed.
In 0.9.0, if a game is in fused mode you can also use love.filesystem.mount in a special way to have read-only access to files which are in the same directory as the game's .love file (which will usually be the same location as the executable, in Windows at least.)