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

Well, I'm currently adding it to plugin_storage anyway
Also, about the /title_reset, I just made it because some people might not understand that you just have to write nothing to reset their title

 

Yeah thats cool. There was a debate about unifying more commands into less just not to have that many. But its ok with extra command also.

 

I'll wait till you finish, after that there's 2 options for us. 1) clean up your fork, make new one and make clean commit, then submit a pull request. 2) i can manually import what you did and credit you in the commit.

If you go with 1) pls don't add donators for now, i can easily integrate them later or make a separate branch. I like them, only thing im not sure if they should have "item" command, rather I'd give them some preset commands for the donators, to show off their value. But this part is realy heavily community based per server, so I assume a lot of tinkering will be done on different servers. I'm thinking of a good way though.

Edit: Anyway I really appreciate your time and effort. Thank you for the contribution!

 

Well, I actually just added the donators for using on the spacefox server. I'd make two ranks for that donator (no real extra features) and if I have to, premium (sometimes called VIP but meh).
I'll try to make a clean version later this evening. I'll append testing to that branch's name and make another, clear and not messy fork from your version. Right now, I test the server on a linux virtualbox but my github is set up on windows, even if I often use the webinterface for edits, and I'm too lazy to make either git on linux or python on windows working, that's why there's one commit for every stupid mistake right now.

I'll have a structure like
Main(forked from you) from which I'll fork a donator version and a version for testing inside which I'll have more branches with stuff like the plugin_storage(which currently doesn't really work).

I recommend to not use any of the commits for now, as I'd rather use plugin_storage than a new column for the title.

 

OK it's been a couple of weeks since last major changes in 1.4x-dev branch. I think I can pull into the main repository and make it the latest stable release. If anyone has some special notes I should look into before that, please let me know. If anyone still uses 1.3.2 and decides to upgrade now, please give me feedback how it works for you compared to 1.3.2 or 1.2.3 versions. And as always, keep backups of all working versions - player databases are backwards compatible, only thing you might note when upgradin from 1.3.2 is that locations of some bookmarks and poi's JSON files has changed from plugin folder to config folder.

Hopefully I'll push it up in the next 24 hrs, just to keep things a bit more alive if nothing else. For sure its a very nice feature rich version for smaller servers, I'm hoping it can handle something more too, but can't say it will.

 

Some would say "those old school guys..." but I still use SVN locally and then just push to git what I want lol ... still im handy with SVN and its what I need, and git is rly cool too, but I kinda lack the interest to learn it properly, so i just try to not mess it up to much. But before you commit to github, you should rly learn to "rebase" its a very nice technique for cleaning up commits. Just google it or read this, think its fairly short and to the point

 

I normally don't use any repo at all, that works too :S

 

Well........ i don't like to be a smartass... but version control? nothing? that's a pain! try out tortoise svn at least, you'll love version control...

 

I have SVN installed but bleh, all that is just not my thing. For programming, I'm happy if on my linux I have nano (no, not vi(m)) and gcc/g++, I don't need alot :>

 

Tha'ts pretty badass rly i'll not bother you with my underskinned GUIed habbits anymore )) but you might be just the person to help, if we decide for a C rewrite at some point.

 

I'm currently using version 1.3.2 and there were some issues I've been dealing with and was wondering if they were fixed in the 1.4.x branch or are being worked on.

One of the issues is that if somebody is at the level to use a command, they can use that command on anyone, even higher levels like the owner. For example if I give a player admin level then they gain access to the ban command, then they can ban me the owner by name. If I give a player moderator level and they gain access to kick, they can kick me and any admins or mods, or demote us. The different permission levels should not be able to run commands that affect their same level or higher.

I'm also having problems with starrypy recognizing names that have spaces like ,First Second. Putting the name into quotes only works about half the time, and if it can't find the player by name, then I can't do anything if they need to be removed from the server. You can't use /warp /whois /kick /ban with their name, you can only lookup their IP in the logs and ban them that way, but this is a very roundabout way. I had to solve the problem temporarily by adding another set of admin commands that let me do things with uuid instead of name, like /whois_uuid and /kick_uuid etc.

 

Permissions: For example promote will check the players rank, but kick or ban will not - banning also works on ip's so should check if you're trying to ban owner or admin IP also. I'll try to add those checks for these commands.

All the commands that take parameters after the name will normally require name to by typed in quotes - exception are commands that only take name (this was done randomly either with extract_name - which always requires quotes and sometimes it just grabs everything (i should have redone this, but i still haven't, and I also like omitting quotes where i can, so we'll see) if you have any particular command that's giving you trouble, let me know i'll look that one first). There's a special problem with chars that have space in the end, usually you dont see it and you dont type it, therefor it cant be found. Version 1.4x has nicknames, which should remedy the situation at least a little bit. You can also manage users via web_gui.

Banning by UUID is redundant, since only 1 char name is allowed and his uuid is locked with that name. I didn't see a special point in banning uuid. Duplicate original names on server, make a lot more problems, so that's not allowed.

uuid is in general a very long string that's hard to type - i would avoid managing uuid directly, as there are other identifiers bound to it in the current versions. Might not be the best, but will do the trick.

 

I totally agree that using uuid in commands is way too tedious, it was just a quick fix I coded in because I'm new to python and that seemed like the easiest solution for me at the time, instead of changing how it dealt with names.

The commands that I've been having the most problems with are the ones like /warp and /promote not recognizing the name and so I can't interact with that player like I can others, mainly why I added a /promote_uuid so I could at least do that.

 

I think both of these commands should use extract_name function which requires quotes. Its possible the second name in /warp from to doesn't use extract_name but ill have to check later (not at comp atm).

Do not use quotes if there's no spaces. You can try 1.4.3 version just put it in separate folder not to mess up your working version.

 

@teihoo Hey some reason trying to do

pypm install sqlite3

Does not seem to work anymore this package does not exist anymore.

 

I think that one is actually already included, so trying to install it is redundant, all my servers already had it...

 

Well I just installed windows 8 and was getting everything again so I needed to reinstall python and what not. So what I was saying is that the sqlite3 package from active python no longer exists. As I did a search for it it was noted as missing.

But you said its included with your rep or included in the installation of python?

 

Ohh sry, seems that's already in python 2.7 and up. The DB upgrade works, and its only used for that, so you should be good to go without installing sqlite3 separately.

 

i really look forwards more groups and easy possibility to switch commands between them, and title too.

 

A little question:
Is there a way to set a Planet to PVP?
Using /pvp will mark you pvp as a player but what if I want a Alpha Planet to be marked as a PVP planet?
Is there a way to do that or to add this in the future? We are currently creating a little PVP arena on a alpha planet and it would be great to mark this planet complete pvp as to hope that players will use /pvp command on their own.

Thank you

BTW: I will update from 1.3.2 to your version teihoo this week. Really looking forward to it,