I feel kinda silly asking this, but I'm just so used to Sphere 1.5 that everything in miniSphere is a struggle for me. So here's the thing:
I'm used to just copying my game's folder into Sphere's (1.5) folder, renaming it "startup", deleting, renaming some stuff and it's pretty much good to go. What's the protocol now with miniSphere for this? I searched the forums for a good hour and didn't find anything, and I can't seem to find the solution myself.
Your method should still work, as long as you distribute minisphere.exe and NOT spherun.exe (the latter is for developers and this doesn't honor startup games). It's actually easier than Sphere 1.5 because you don't need any extra DLLs, just the system folder.
Thanks! It works.
Seems kinda obvious - I did try this but it was after I changed the directory structure from the old 1.5 layout into the new layout, and didn't really know what to do next - I then copied the whole game directory into miniSphere, and so the engine didn't recognize it. I should have only copied the "dist" folder and renamed it "startup" (I think... right? That's what I tried now and it works).
Yep, "dist" is everything you need when distributing your game (hence the name).
What also works is packaging it into an spk file and putting that file right alongside minisphere.exe. The engine will just run that instead.
And another way to make it work is to just have the one game in the games/ folder and no other games. That'll just automatically run the only game available.
If I run it into an SPK, and I have a save folder that my game uses to write its save files, will it save files into the SPK or will it create a seperate folder? I wanted to check this myself but creating the SPK takes a really long time, gonna have to keep it overnight. :)
It keeps saves of everything in %USER%\AppData\MiniSphere\GameName, if I'm not mistaken... or at least, something similar on it. (I run Linux, but Fat Cerberus can tell you for sure!)
If you're using the Sphere v2 API, you specify save files explicitly as ~/path/to/filename, so they don't get saved in the game directory anyway (and trying to do that is a sandbox violation). For Sphere v1 API functions, which need to be 1.x-compatible, any writes to the SPK are virtualized to a subdirectory of <mydocs>/miniSphere/.spkCache. The virtualization process is transparent to game code which acts just as if you actually saved the file to the SPK.