Devs, the people who are complaining that the Nightly builds are bad because they may be broken are simply unaware of how software development works. They don't know that source control systems and software distribution platforms can be set up to automatically publish code as it becomes available on the code server. They don't know that the code server isn't an optional thing, and that all software is stores in a central location which everyone draws from. They think this is taking time out from your day to actually publish this, instead of the 30 minutes to set up the automatic transfer (after probably a few hours or days of deliberations about whether or not to go live with the code). I, for one, applaud this. I use linux, so I am very used to unstable distributions. The distro I use is Arch Linux, which is a rolling distribution model with 3 tiers, Stable, Testing, and Source mode. I stay in Stable, but occasionally dip into the Source to build myself the latest version before it is even tested properly, with some mixed results. This helps greatly, but also having these three divisions works to accomodate all types of people (there is a 4th branch, LTS, which only updates every year to a perfectly stable and polished version, but is often missing new features) I suggest that there should be 3 tiers for this game, as well: First, Stable. A version of the game that works well. This is for people who don't like taking risks and want their game to work, period. Second, Unstable. A version of the game that works pretty good, for testing versions of the game that might make it to stable. Basically Release Candidates. Third, Nightly. This is just the raw, maybe broken, maybe works, testing platform that mirrors the actual source code in its current state, compiled nightly. You likely have these branches on your source control server, anyways, and it would take little time to enable the sharing of all of them. For now, I will test out the Nightly, but will likely stay in Unstable until it gets updated, too. If you've planned this already, then awesome. If not, please consider it. And I realize that the actual devs may not see this message. If you work for Chucklefish and feel that you can get a message to someone who would care about this, please forward this to them.
For those of you wondering how to have both copies, all you need to do is go to your steam games folder (Normally located here: C:\Program Files (x86)\Steam\SteamApps\common) Where Starbound was installed to. -Make a copy of your Starbound folder (BEFORE the nightly build, otherwise just go back to the original build first). -Put that copy wherever you want to play the original Starbound from (Example, C:/Games/<Folder Here>/). -Then check yourself for the nightly build. -You now have both copies. Make a shortcut to /Starbound/win32/launcher/launcher.exe Making a copy of the original before I checked the nightly build worked for me.
Thought this mentioned earlier in the thread was how you summon those parts. Am I wrong? please correct me if I am, as I don't intend going nightly just yet to check something like that.... I like the idea of nightly; in the very least to see what has progressed, but I probably will stick with unstable for the time being.
I am making a program to do that for you. It will be cool. Or it won't work. Wait, there's popcorn?!?!
Maybe this will clear the confusion; Your ship starts broken. In the current game files, there are items to repair your broken ship, which are effectively the first 2 ship upgrades. (the parts summon that you mention) These upgrades simply repair you ship so you can use it to travel, they don't add more rooms. If you want to upgrade beyond just fixing it, those items aren't currently in the game we have (at least not that I could find), it's a little trickier. I put a guide for it in the Admin codes collection thread.
I can't tell whether Molly has responded or not. So much activity on this thread. Could someone respond as to whether she has given me an answer? Thanks. EDIT: Guess what! Not only is ALL of the crafting available right away for free, but so are all the techs! The Apex mech has a wonderful shooting noise and the human jeep totally doesn't cause a crash!
How would one use admin commands? Are they currently in the non-nightly version of Starbound or just not implemented yet...?
They were in the older unstable, but were removed. I believe there because of a lack of authentication and permissions. Basically, there was no way to "op" people.
A man of few words. If you elaborate, we may be able to help you. When does it crash? What does it say?
Ok, Molly has not responded to my question about the launcher. It is time to summon her! Beetlejuice! BeetleJuice! Bee... Oh wait. Wrong summoning ritual. Let's try that again. @mollygos Mollygos! Mollygos! Is my launcher going to be authorized, or not? I have a basic version working, I think. I need to do a little testing, but it supports all computers with Starbound on the C drive, and should support those using an alternate drive (are they called spindles?) I still need to make a forum post with detailed instructions, and I need to brush up the warning/disclaimer/instructions window, but most of the stuff will make sense to anyone who is proactive enough to PM me for it. I plan to add a few more features over time. Thanks for the response!
