Server Discussion StarryPy - A plugin driven server wrapper written in Python.

Player.db. I downloaded a small little sqlite software to manage playernames

http://sqlitebrowser.sourceforge.net/

 

Thanks a lot.

 

So a fairly big problem concerning the new perma-death feature of Starbound:

When players die they have to create a new one right? Well their name is locked in the database with their old UUID. It causes the need to manually remove from the database (which is easy enough, but harmful on the players that have to wait).

Perhaps a way to gather if that player is perma-death or not? I don't know if it's possible, but... Even something as simple as a /permadeath the user can type in to unlock their UUID with that name?

 

Thanks, when you say it's need python packager tornado, i use the default windows tutorial update, did i need something to install before your plugin ?
Where did i download it ?

 

Install tornado the same way you installed python packages. Just open command prompt on starrypy folder and pip install tornado

 

Thanks for the help

i getting some grief on the server, i would wait for the 2.0 version, but seem i cant wait anymore.
anyone know if starbound will have protect system by account like minecraft or "Tshock white lotus" for terraria ?

 

Yep that's what I did, but you're now missing the org_name fields for chars, i suppose it could be done on every login if the field is blank, but can you modify table through python code, or more likely SLQAlchemy ,... that looked like an issue, so i did a reset, just to not mess stuff up.

I'll try out the changes.

 

There's already a file called accesscontrol.config where you can add usernames and passwords, but it requires starbound_server restart. But yeah, that will be done eventually

 

ingame /list_players
ingame /delete_player (or del_player not sure)

Edit: I'm not sure, cause in my latest beta, I changed a lot of commands to be more inline with eachother like: /player_list, /player_del, /ban, /ban_list ...

 

Well that not what i mean, username, ip and uuid are easily counterable, the way work minecraft or white lotus, is that you ban the account that is affiliate to the CD Key, so unless the grieffer buy another copy of the game, he is ban for life of your server.
This system help alot identify and ban forever griefers, from you server, and maybe other if you share banlist.

Sound like the ultimate anti-troll ever, and i get no clue if starbound or a wrapper will use it.

 

Hm well, Starbound doesn't supply that kind of information yet... currently you work with UUID and char name (and IP ofc). There will probably be more options in the server itself later on.

 

Im working on complete name change on login, if it finds a realname or alias name, it will modify your char name with trailing underscore for example. You can then change your nick to any free one. Player should send a note to admin, to delete that player from DB, but there's still a question how to know you dont delete an existing player just because someone says its "dead"? I'll look into perma death if a char get some tag or something. Never tried it yet :O

 

Looks good and works. I do make a regex check on names, removing any special chars they put in there. The default regex removes - also, i'll try fix that - doesnt get removed, but its not top priority for now.

 

Since Starbound doesn't use CD-Keys, the SB Client would have to retrieve the players Steam-ID from the Steam launcher and send it to the server. As far as I know that should be quite easy with the Steamworks API. But there are also plans for a DRM-Free version of SB, which would need another kind of unique ID, so I'm afraid this feature won't be coming anytime soon.

 

Who doesnt use steam those days anyway ?
Servers could accept only connexions sending a steam-id.

 

Hi, i succesfully test your wrapper on my computer, i really considering engaging my server on this one now, but i understand that an update is comming soon and it's better that i wait for it if i dont whant to manage my users 2 times ?

 

For now I only made 1 change in DB, but it will require db reset. I'd tell you to use beta version at least to create DB with, but then you'll be missing the org_names ... probably best to wait, or play with new version. Im trying to make ship protect, but on every ship i warp to, get set as my own ... grrr, looking into where it sets it back. I managed to get some login performance up, but there's still some weird stuff going on in packets, i've tried oldest StarryPy i can find, and it does the same ... I need a couple of more days, or i'll just skip ship protect... it gives you a tag you're on a ship at least

Edit: Anyway beta shouldn't really be crippled, I think it works as stable as the released 1.3.2. But maybe some stuff will change. No promises at this point

 

Hey @teihoo i have been around the thread but the info is so, so, spread around tons of pages, how is the new version going? And what are the new features?
Is it recommended to install Starrypy right now, if yes, what version?

 

Is it possible to replace the starrybound wrapper with StarryPy on a Multiplay.co.uk server? This would fix probably all of our server problems.

Edit: correction it is a wrapper mod.

 

From my own testing I say 1.x and 2.x can be safely used. If you have a server with like 20+ players, I honestly don't know since I haven't tested any with a lot of players - roughly up to 5 on my end, and for that it works fine. I'm still running 1.x version myself, and it seems more stable then the starbound server itself, if that matters. 2.x showed better performance, but i'm still lacking features to make it usable for me (like warping ships, bookmarks and few other minor issues). If you like to live on the old edge, I have a fairly newer version than the last on in official repo, but is still work in progress. It adds features and some minor improvements or actually they're fallbacks, to how stuff worked better before. I'll have an update later on today or tomorrow (specially with login cpu spikes, they should be lower or more spread out usage), and I'm banging my head with ship protect, its killing me. Better leave it for a day i think. So its really entirely up to you. Based on what you want most (speed or features) i'd suggest 2.x for speed (but stuff will change for sure, like db changes, so expect reset or import), and for more features go with 1.x (1.3.2 as official, and my beta 1.4.x from my repo). Hope something works for you.