kvimber / mcstation Goto Github PK

By default the properties file binds to 'localhost' This binds to the loopback address and not its outward facing IP. Meaning any outside client connects are unable to establish a connection. At the very least there should be a log message mentioned when binding to localhost.

This is for the issue where the server jar file stops finishing the startup process.

You (Kendrick) said that you saw this on Windows. I tried to reproduce it last night, and couldn't on Linux.

Test on Windows and if the problem is there, we'll take a look further into what's going down.

Current Problem:

• If you start up the server, and run the start method, the server jar should start up and load the level to completion
• It was seen that this wasn't the case, that it didn't finish building the world in a clean state (with no world in existence already)

I've setup the MCServer.run_test_setup method that should kick everything off, and start up the server. It should make reproducing this problem easy, as it waits for a full four seconds after startup to check for logs (and then dumps all logs since last startup) so you should be able to easily see if the system gets setup all the way. You can just comment out the run_server method call if you'd like to be able to debug further, or if four seconds isn't enough to generate a world on your system.

• system needs a good way to create a user, and enter their information to the pass.txt file
• needs to hook up with mc_security's build_user_line function, which puts together the correct pass.txt file line format given the user's user name and password

There should be some form of validation performed so that not just any client could run commands on someones server.

When a MCServer object is created it would be nice if there was some error checking. Verifying java is on the path and the server jar can be found, etc. Then when the startup command is issued we also need some way of verifying the process got kicked off. I've already started writing some of this, we can discuss it further tomorrow.

• currently the install doesn't add a pass file
• instead of having a default user, we want server to check on startup if the passfile exists
  • if not, then it prompts the user to create their first user
  • if so, then it just continues on and starts up the server

A message could be displayed if the "stop" command is issued while players are logged on.

The user could build custom packs to give a collection of items with one command.

There should be install packages to simplify setup and installation for Ubuntu/Windows platforms. Also a tar of just the basic source.

Client Install fails to start because there is no server folder to cd into.

currently MCStation doesn't start the Minecraft server when started, you have to login to a client and start it

we want the server to automatically start Minecraft

Flesh out the help system to give a list of commands and descriptions.

• this can be done by defining each dictionary entry one at a time, rather than all at once.
• We'll just have to comment to make sure that ones that are needed for another have to be defined before them (you'll know one that depends on another because it'll look up another in its definition)

The client could have the ability to tie into the Minecraft user name. This would shortcut any commands to that users name unless specifically giving a user.

Using the client, no MCServer commands get run. The server parses it for the / but any other commands get ignored.

• Currently, since properties files are defined in a python dictionary, you can't re-read them when the system is running, you have to bounce the whole thing.
• We want to have it so that a user can reset a system setting, and then just tell the system they want the properties re-loaded, and it should run with it.
• We can do this by actually loading the properties from a text file into a properties dictionary, and then just calling the same method that loads them when an admin wants them reloaded