For those who desire a bit of security, can you add a hash & salt option, so that salted hashes are used instead? I seem to recall that you already embed the openssl libraries, so hopefully this request is small. Naturally, for people who have no idea what password hashes are or who simply don't care, you can leave plaintext as an option.[DOUBLEPOST=1424332316][/DOUBLEPOST] And to make sure you haven't goofed up the formatting by missing a comma or something, use this tool: http://jsonlint.com/
Yeah, same here, gotta work Planning to mess with the config files during the weekend, but if you happen to find that one file that matters before: awesome! Yes, I did make sure the server is updated, guess I'll just have to try around a little more. Ebenfalls viel Glück!
Having issues trying to figure this out. It throws an error every time. I am tech savy but no coder. Basic cmds an stuff. But never notepad items. this is what I am entering "serverUsers" : { "Chris" : { "admin" : true, "password" : "123456" } }, "Blake" : { "admin" : true, "password" : "123456" } }, "allowAnonymousConnections" : false, "allowAdminCommands" : true, "allowAdminCommandsFromAnyone" : false, "bannedIPs" : [ ], "bannedUuids" : [ ],
You have one curly bracket too many - serverUsers opens and closes with one, and contains entries that open and close with one. Said entries are comma-delimited. This should work:
This sucks when the sync script doesn't support the new admin boolean values and'll require refactoring. I wish that'd been left in it's own hash. Alas.
Unfortunately this did not work. I guess i will just have to spend some time figuring this out over the weekend. Thank you though!
The replies in this forum post are proof that requiring users to edit config files and format them properly is as bad of an idea today as it was in 1999. Usability and ease of use should be paramount! Anything else is half-baked. Not everyone wanting to run a server will be a capable power-user. A good rule of thumb is, "can i make this work without reading any instructions"? If the answer is "no", then it's not easy enough.
Really? I'm sorry to hear that. Are you changing the correct file in /giraffe_storage/starbound.config?
As a streamer it would be nice if the password field in game was hidden. At the moment every time I need to connect to the server I have to blank out the entire screen. The sort of thing where it's replaced with ****** would be nice.
Replaced with what? Sorry, couldn't resist. . I do agree with you, I tried out twitching the other day (and immediately got stage fright...), and realized I would have given away my password IF I had had any viewers.
SO I FIGURED IT OUT. This portion of code "allowAnonymousConnections" : false, "allowAdminCommands" : true, "allowAdminCommandsFromAnyone" : false, Goes at the very top. So I have figured out what is throwing the error. When I place the "aallowadmincommands" after serverusers inline with the rest of the code it throws the error. I can add the user string, red is what throws the error. "serverUsers" : { "Blake" : { "admin" : true, "password" : "123456" }, "Chris" : { "admin" : true, "password" : "123456" } }, "allowAnonymousConnections" : false, "allowAdminCommands" : true, "allowAdminCommandsFromAnyone" : false, "sfxVol" : 100, "speechBubbles" : true, "title.connectionString" : "10.0.0.14", "upnpPortForwarding" : true, "vsync" : true, "windowTitle" : "Starbound - Beta", "windowedResolution" : [ 1000, 600 ], "zoomLevel" : 2 } [DOUBLEPOST=1424635137][/DOUBLEPOST]
I play Starbound on a server running on my own computer at times, so my wife and I can play together and share a home world. Well my wife put hours of work into a world bulldozing it for the sake of easy building and it FREAKING RESET ITSELF. All the bloody work she did appears to be completely gone, and this happened once before before the 1.0 update. Where do I report this total bullcrap/ask how to fix it? Edit - In the mean time I showed her how to spawn the Super Fishaxe, so she is enjoying that.
well, i'm still having a problem with this... i put in the information correctly like the example above; and it booted right up. well i went in and tried to /admin to make myself admin and it didn't let me. so i changed the "allowAdminCommandsFromAnyone" to true. went back in, same affect. i have the admin commands set to true and the anonymous connections set to false, yet random people can still join and i cant do admin commands. can anyone help me here?
For the love of God.. can someone just post a working config file with the proper syntax? All of these posts claiming "I got it to work" don't work.