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

/whois for a player
/whoiam for yourself

Cheers.

 

Haha true!!! I'm such a noob -.-

 

@teihoo I am not sure if this was covered but what is the defualt level a player had to be in order to claim a planet?

Edit: I found out. Is there a way to add another user level to this say VIP to use more then the guest can

 

Currently all claim commands are set for everyone (GUEST and above): @permissions(UserLevels.GUEST)
If you want to change it to registered, just change all those into: @permissions(UserLevels.REGISTERED)

 

Well what I want is for guests to beable to claim 1 or 2 and if higher or above they can claim 5 or more.
so could I add a line like

Code:

if
@permissions(UserLevels.GUEST)
then
self.max_claims = 2
else
self.max_claims = 5

Or

Add something like

Code:

self.max_claims_guests = 2

then for guests change

Code:

if int(my_storage['claims']) >= self.max_claims:
            my_storage['claims'] = self.max_claims

to

Code:

if int(my_storage['claims']) >= self.max_claims_guests:
            my_storage['claims'] = self.max_claims_guests

Then I would need to make additional sections for Registered users

 

Yeah that might be a good idea to have 2 values for max_claims. I'll see how I can make it as simple as possible.

 

Ok cool. I should get into coding so I can contribute. For the most part I can do anything that I set my mind to

 

Hm, has this project been abandoned?

 

Carrot has been gone for a very long time but Teihoo took over development so you shall not worry, there's a working version .

 

Think you should simplify it, just add additional max_claims_guest parameter to config (hard set it to 1 or 2 if its not defined), then add an if that will do something like this: if self.protocol.player.access_level < UserLevels.REGISTERED (this will trigger when player is a guest).

If user is not guest, then just do everything like its already done. Think that will be the easiest way.

 

Not completely. Original author is missing, but a few ppl are still struggling to keep this one alive. Beta here: https://github.com/teihoo/StarryPy_Teihoo

 

Updated commands guide with claims (only text, didnt change pics ) and also reference for those who missed it:
StarryPy ingame commands (for beta 1.4.3)

 

How is the performance on big servers on 1.4x then?
Oddness.

 

I really cant say. How many ppl can you run on a plain starbound server?

 

50
I may try but if it lags madly, there is no other proxy, i shall cry.

 

You can try, but it will use some resources though, on my end (with few players) usually the lag comes from starbound server before lagging out on starry py. I never rly tinkered with the core, except reverting that deffered function call back delay to what it was before enraged fix in development branch. Anyway biggest stress is obviously protection check.

Edit: There were some talks on IRC, maybe we should do a re-write from scratch and just go with C. That would be the perfect solution then. But not an easy task.

 

I made a simple title function, it's on my github (https://github.com/iChris-cl/StarryPy_Teihoo_plus) in case you want it, commits might be a little bit confusing though (edited it online, ever file changed is a commit, then every dumb mistake again)

 

That's very nice thank you Now I have an idea you can play with. Actually title_reset is redundant if you just make /title (player name) without any title specified, it will reset it - one command less.

Also with subfunctions - that are not called by player commands like /title you do not need to specify rank before it, since its called as a subfunction of something that already has set permission - like
@permissions(UserLevels.MODERATOR)
def unban_by_name(self, data):

Actually @permissions(UserLevels.MODERATOR) is already defined for /unban command which calls unban_by_name if it needs to, not by a player directly.

Other than that, you made some changes with permissions and added donator group (which I'm not too kin to put in main branch, but could make a branch for it thought). Or maybe its something that should be put in (more ranks?).

 

Oh, well, about the functions, I just put blindly the permissions in front of the functions, was lazy. Also, for the title, I used a new column in the sqlite, which probably requires a player.db wipe when switching to this version. I might try adding it into plugin_storage

 

There's already a function for migrating DB if you put it there, traxo made it for my original names addition, you can simply modify it to check for your title column. https://github.com/teihoo/StarryPy_Teihoo/commit/9b5138764ca616fb75fdb09453adad48b00c7bff