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

Now this is just saying "Planet is already protected"

What in the world has changed? I can't add users again?

 

Yeah I thought about that a lot actually. Now that there's more commands, it makes sense, but i'd have to chnage quite some stuff so it would parse out commands after initial command, so there's some work to be done. I will get to it evetually - and exactly bookmarks are the most confusing ... i also want to make the commands as short as possible, for less typing needs. I'll prepare some sort of transcript for commands (which one should change to what), we'll unify them here then I'll implement them.

Edit: My first step without a bigger rework on commands, was unifying them under mostly same roof - like /poi /poi_set /poi_del - so yeah next step is /poi [set | del] (name)

 

OK first off all. If ppl can connect to your 21024 then this is bad - means you're server is most likey wide open, or the starbound_server has upnp set to true and it configures your firewall/router. You should by all means close all ports on the server, that you do not use!
Password is pulled from starbound config or from accesscontrol.config i believe.

That is link to my my forked repository, that holds beta version 1.4.2, official repo is currently on v1.3.2

 

Any idea on why /protect username is just causing the wrapper to shout at me that the planet is already protected? It worked fine the other day when I tried it and I haven't changed anything since, so it's quite baffling.

 

Hm. Maybe youre trying to add nonexistant user? But then it should say that... is it name with spaces?

 

Are you on Steam? I need to talk to you .

 

@SweFox brought up an issue when players can open the container and then apparently thei UI freezes (this is only when using global Planetary Protection (/protect_all). It doesnt freeze, it just doesn't let them do anything from that point on - not even close the inventory, or drop what they're holding in their hand. So it looks and feels like a freeze, but chat still works.

To fix this, remove:
"SWAP_IN_CONTAINER",
"OPEN_CONTAINER",
"CLOSE_CONTAINER",

Edit: (added all 3 lines here, for easier reference)

from your config.json while the StarryPy is stopped. Players will be able to get stuff from containers now, so make sure you keep doors locked (with wires if you're using automatic doors) to protected chests. I don't know how much grief this would allow, so if you want the guests completely blocked, instead of removing that line from config, add another next to it, to prevent opening chests or anything:
"ENTITY_INTERACT",

Edit: On second thought, why not remove OPEN and CLOSE CONTAINER aswell, its basically a client feedback mechanish, that container was opened or closed as it seems - remove these lines aswell, unless you decide to use ENTITY_INTERACT, then don't remove these lines:
"OPEN_CONTAINER",
"CLOSE_CONTAINER",

 

What if i wanted them to be able to pickup loot from what mobs drop or say they mistakenly press q on their sword or something and cant pick it up then it despawns? Could I allow them to pickup items off the ground but not let them into chests

 

Well I don't yet know what all is possible since I didn't play that much with it... at first was just block all, then we got rid of "can't do nothing" ... but to get everything working as we would all expect, someone needs to play with it and try adding/removing different packets, that sound reasonable enough to do the trick. So you find packet names in packet_types.py

Code:

class Packets(IntEnum):
    PROTOCOL_VERSION = 0
    CONNECT_RESPONSE = 1
    SERVER_DISCONNECT = 2
    HANDSHAKE_CHALLENGE = 3
    CHAT_RECEIVED = 4
    UNIVERSE_TIME_UPDATE = 5
    CELESTIALRESPONSE = 6
    CLIENT_CONNECT = 7
    CLIENT_DISCONNECT = 8
...

And you add the ones you think should do something correct along the line to config and restarty starrypy:

Code:

            "bad_packets": [
                "CONNECT_WIRE",
                "DISCONNECT_ALL_WIRES",
                "DAMAGE_TILE",
                "DAMAGE_TILE_GROUP",
                "REQUEST_DROP",
                "MODIFY_TILE_LIST"

I will do this soon probably, I just can do it all at the same time If you make a perfect selection, I'll use it!

 

i use windows server 2008, so all port are close instead of 21025, 21026, 21027 that i open, so you tell me that i have to disable upnp from config ?

Also what about a permission list to complete this awesome command list ?

 

"upnpPortForwarding" : false,
in starbound.config

What permission list?

 

No and no. I tried it with an offline user and then an online one... Same result.

 

For example :
What group can build ? Can use projectiles ? Can bypass protection of planets ? can spawn npc ? etc...

i'm asking that because like you display it, it's seem that you only gain commands when being promote on groups...

 

I've tried searching the thread... web_gui chat doesn't seem to work for me. I cannot see the chat and I cannot send chat from the panel either.

Any assistance?

webgui.log shows nothing

Code:

        "web_gui": {
            "auto_activate": true,
            "cookie_token": "removed",
            "log_path": "webgui.log",
            "log_path_access": "webgui_access.log",
            "ownerpassword": "mypassword",
            "port": 8083,
            "remember_cookie_token": true,
            "restart_script": "",
            "serverurl": "localhost"
        }

 

Are there any errors in your server.log or your browser's javascript console?
Do you access the WebGUI via http://localhost:8083 ?

 

I still can't add anybody to protection list.

Type /protect name won't work, even after multiple restarts. Actually, typing /protect /ANYTHING/, even if it's like help or something doesn't do anything. It's like it won't parse anything after protect.

 

Also I already told the fox of this fix. xD

 

2014-02-21 23:00:09,634 - starrypy.plugin_manager.route - ERROR - Deferred function failure. [Failure instance: Traceback: <type 'exceptions.TypeError'>: exception() got an unexpected keyword argument 'exc_info'
/usr/local/lib/python2.7/dist-packages/twisted/internet/base.py:1201:mainLoop
/usr/local/lib/python2.7/dist-packages/twisted/internet/base.py:824:runUntilCurrent
/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py82:callback
/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:490:_startRunCallbacks
--- <exception caught here> ---
/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py:577:_runCallbacks
/usr/local/lib/python2.7/dist-packages/twisted/internet/task.py:832:<lambda>
/home/steam/Steam/SteamApps/common/Starbound/StarryPy/plugin_manager.py:175:do
]


Yeah woah wtf is this... I had just ran a fine restart beforehand but now I'm getting this. This is bad.

 

I've explained commands by level here:
http://community.playstarbound.com/...-written-in-python.67562/page-65#post-1876250
And as a guest you already get quite a few commands, for more, you need admin aproval. Custom planet protection can be seen with /protect_list if you're admin.

There's no special protection groups or anything, you're either allowed or not to - if you're guest and the server is using global planetary protection, then you wont be able to build on any planet really. If you're registered (or guest and there is no planet protection) you will be able to build on any planet that is not customly protected via /protect command. You can build on that planet, if you're added to allowed list /protect your_name check with /protect_list

 

i haven't checked in for a while and you suggested me to look through the different logs (which i did) and there we no errors in the web_gui (iirc nothing was even written inside there). me and higgins are practically running things the same and have had similar problems previously. i'm going to just go for 1.4 and start over clean with all the StarryPy stuff and see what happens i'll let you know tomorrow if i have time to git 1.4 up and running