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

Hi, i confirm yesterday that guest can spawn projectile and npc, bomb/meteorites/and many bullets can cause heavy griefs, and it's possible to spawn npc with those guns, or just op npc.
So did you have a solution about that ?

Cheers.

PS: any news on V2 also ?

 

Well, none of these are it.

SPAWN_ENTITY = 29
ENTITY_CREATE = 42
ENTITY_UPDATE = 43
ENTITY_DESTROY = 44

==

Edit - They cant place blocks, or remove blocks.. they also cant remove objects that are already placed. But they can place down new objects (torches, doors, etc) so if we can just figure out which one handles placing of objects..

 

Yes sadly i believe it's not possible to check against Modded NPCs with major grief guns... The worse part is how even on server restart the save files save the npc and it still griefs everybody, forcing world save file delete.

One of the other things Devs are really non-caring, the server major exploiting, even with npcs config files being server-side, they are still exploitable to replace the server rules with the client modifications, it's amazingly bad & frustrating.

 

Actually people can spawn those because they cant place bloc but can place interactables, so npc spawner, we have to restrict more guest group...

 

Also i promise to translate V2, but actually i'm translating V1, and i cant found the where is the line " * players online:"

Can you tell me where is this line ?

 

Actually people can also spawn those with Tech, editing techs to trigger the npc spawn is one bullet-proof way to spawn your modded npcs into one server (as server will only detect it as tech usage), when it comes to that, i believe one wrapper would need to block all tech from being usable on the X Planet

 

That's in admin_commands_plugin.py

 

Also, beta claims here. Extract to plugins folder and start up StarryPy.
They will set config with max_claims = 5 on first use automatically.

Or here's how it looks in config if you want to pre-set it before first use:

Code:

        "chat_logger": {
            "auto_activate": true
        },
        "claims": {
            "auto_activate": true,
            "max_claims": 5
        },

 

Im curious, how much of a improvement in speed is found in StarryPy3K, i downloaded Python 3.4 and manually compiled it. Im using it in a virtual envrioment through the terminal so i dont over write the 2.7 python butt havent been able to test yet because it's using default values even though i changed the port in its config.. but it might also be because StarryPy is binded on 0.0.0.0 instead of the main IP. Dont know yet, to many people on the server to test at the moment.

I see it uses some other lib's and asynco or something.. i dont have a lot of experience with python im C++, so i was wondering if your able to give any type of reference or percentage based opinion on how much faster you think 3k is?

 

There's a closing paranthesis after "StarBound" in the path. That doesn't look right,

 

Hmm claims seem nice, Starrybound fork had them running, so this will be like /claim one un-claimed planet, /claim list as your claimed planets and /unclaim ?
I have one idea, after we claim one planet, we could integrate /protect on them, on your claimed planet you have permission to add people to your claimed planet that will have permissions to build on it.
Or not integrate, just make the same usage to let those groups and RP players inside one server have their own planet, with their permissions on it!
Good luck with this

 

get a spammy error, maybe because i translate, i have been very carefull to not touch the code and only the text.

Edit: i dont know what cause it, but it's not instant after launch so translation is maybe not what bring the error...

 

Thats how it works. Claim can be used only if planet is not yet protected. It will add your name as the first person in protect list and based on that you can add ppl to protect list with /claim Name. Same goes for unclaim. Note that you cannot remove self unless you use /unclaim to completely unprotect planet. You cannot modify other planets then the ones you claimed (being that youre first in planet protect list).

 

Im curious, how much of a improvement in speed is found in StarryPy3K, i downloaded Python 3.4 and manually compiled it. Im using it in a virtual envrioment through the terminal so i dont over write the 2.7 python butt havent been able to test yet because it's using default values even though i changed the port in its config.. but it might also be because StarryPy is binded on 0.0.0.0 instead of the main IP. Dont know yet, to many people on the server to test at the moment.

I see it uses some other lib's and asynco or something.. i dont have a lot of experience with python im C++, so i was wondering if your able to give any type of reference or percentage based opinion on how much faster you think 3k is?

 

A Question to the StarryPy community, with the StarryPy now in two versions, StarryPy3K in active development by Carrots and StarryPy which seems abandoned by Carrots (at least if I understand the git network correctly, which I might not since I'm a total Git Noob).

Which version should one get?
And more importantly is Teihoo's StarryPy fork the new active "main" fork of old StarryPy?

 

He didn't abandon it, he gave Teihoo owner so he can focus on 3k.

 

Well, everything done in the core of both versions is by Carrots. I merely made some plugins for 1.x version and later on when Carrots was focused only on 2.x I pushed my completed changes to the original 1.x, as it was an improvement of that version, by the means of features and small bug fixes. I plan to fully integrate many of the features from 1.x to 2.x once I get all the functionality I need in 2.x (waiting for Carrots to finish the missing parts). Version 1.4.2 in my fork is now a temporary beta version of 1.x, where I try to implement features from 2.x (like nick names) and for now, am making a feature complete version, that will be used as a feature outline for final 2.x.

Either version you choose should work well to some degree. For example 1.3 can have some problems when player name uses some weird chars, this should be solved with nick names in 1.4. 1.4 and 2.x both have a web plugin built in (but different ones) and there's some more fixes in 1.4 compared to 1.3 (also reverting a deffered function call from 0.01 sec to 1 sec seems to speed up things greatly, but since I want it tested more before pushing big changes, its still in not in main repo). I'm currently mostly working with 1.4.x

 

Good point teihoo. Currently I am always pulling the git Version from here: https://github.com/CarrotsAreMediocre/StarryPy
so this one will also be frequent updated?
Another thing: I used the IRC fix of Kiofspa posted here: http://community.playstarbound.com/...erver-wrapper-written-in-python.67562/page-65. Its working like a charm.

A quick node. If i want to disable commands like fuel or spawn for guests I just changed for the specific .py script the @Permissions to UserLevels.ADMIN instead of GUEST. Is this the right way to do? or does there exist a command list where you can simple change the commands Permssions? If not this would be great thing for the future. Because I simply dont want to enaple some commands that are currently used for guest users on my server.

Thank you

 

Dude you seem to have so many issues, that no one else seems to have often service side and griefers. Who did you make mad?

 

We are lucky to have most of the uncommon, common, and worse issues a server can have, sadly. It may be normal, we usually can get full as 50 players, and had already over 26k Unique Player files since January
Some are linux related about things that did not got fixed (what the patch notes said it was), others are due the fact this is a big server, and that may be also why sometimes it takes around half hour starting the server after a crash due that "recovering file..." thing. We have several pages of code and 4 sysadmins always around to keep the darn server on track, yet some people already said it's my side, and we don't know what we're doing, but i can't deal with issues when it's the sb server process that is not behaving correctly, saddest part was get replies from devs like Tiy "You must run the worse server of the planet". Yet we are never, ever empty and people spam join our server for some reason, so i believe we're good enough!

The biggest hint is, don't try to go for a big server, specially on linux!