Dec 9 - Nightly launcher is broken

http://playstarbound.com/dec-9-nightly-launcher-is-broken-2/

I'm having to manually make this post because of server stupidity.

 

Good thing "Nightly" branch wasn't advertised as stable! Thanks for the heads up.

 

That link... it's... it's the most elegant and finely crafted link I've ever seen. I think I will take a screencap of it and save it to my desktop so I can cherish its elegance for as long as my computer works.

 

@OmnipotentEntity You guys may not realize this, but you might actually be losing money. It has do to with the direct executable rather than launching through steam. I would rather not post the method as people could just exploit it. If you know the method, disregard this message. If you don't know the method, then is there a way we could talk in private?

 

Steam is evil.

 

If this is about there being no DRM protection on the executable, and being able quickly and easily make copies or run multiple instances at the same time, then I don't really care, and I actually consider that to be a positive feature.

If there's something else, please send me a PM.

 

A sensible idea.

 

As a personal hotfix -while you guys and gals wait to hear back from valve- I fixed my own launcher by adding a COPY of the sbboot.config file to the launcher directory with corrected configuration:

Code:

  "assetSources" : [
    "../../assets/packed.pak",
    "../../assets/user"
  ],
  "modSource" : "../../mods",
  "storageDirectory" : "../..",

And since there are now 2 sbboot.config files if I mess up and hit a executable directly -instead of the launcher- everything works fine.

edited: to add the preamble (in italics) I thought I wrote down, but must have only imagined I rote down. Braining is hard today.

 

Nice to see a developer who dislikes DRM for a change. The only people that DRM really screws over are legitimate paying customers after all. Pirates are always going to find a way around DRM outside of absolute server-side only games like MMO type stuff.

 

Not sure about what's happening since everything seems rather technical for my understanding (Not native on english) but here is my two cents:

What about using a launcher just as the one on Mount&Blade series?, steam calls for the launcher and once in the launcher we can choose between nightly build or stable build. Mount&blade uses it to launch the Native version or other mods.

 

We're pushing out around a gig of updates every week. We'd make a whole mess of people annoyed with us if we did that.

 

Should we just launch directly anyway from now on? Would that help us avoid (some) problems in the future?

 

May have already been caught, but in OSX, the path to the assets and so on in sbboot.config is incorrect. This makes even launching directly fail.

After a clean install, the assets path for example was "../../../assets/packed.pak" when it should be "../assets/packed.pak" Making this change, and the same change to the other paths, fixed the issue.

Edit: The unpacker, server and such also aren't very happy on OSX. Their paths to the frameworks are no longer valid.

 

Thanks for the heads up.

 

i never actually use the launcher anyway =x i created a start bar shortcut directly to the game to make things easier lol

 

So, I tried launching from the .exe, and it's showing the same error message for me. Is there something else I'm doing wrong?

 

Doesn't impact me since I launch it manually so I can start the game on it's own X display with no window manager and without steam gimping things (on Linux).

I'll pass word along to friends and family though.

 

I find that renaming the starbound.config file to starbound.config.bad also works

At least until you try to play :/