Closed guppy42 closed 6 years ago
You need to extract the assets in the server's working directory.
This might be a little bit unclear atm, I'll try to make some better documentation about that.
i have the same issue
Some documentation would be a good idea I think ( also of what the json file server.properties can contain ) .
did a fresh pull and ran it from ~/.local/share/mcpelauncher
extracting to another directory causes crash with undefined symbols - so some docs would still be nice ;)
Server seems to be running base on console output, but It's not visible either as a local game nor does it show any information when I add it as a server by IP.
so some info would be great :)
I documented the server.properties there yesterday: https://github.com/MCMrARM/mcpelauncher-linux/wiki/Dedicated-Server's-server.properties
To have it show on the local world list, add a motd.
should've checked the wiki - was half way through documenting it here based on server.cpp when your message poped up xD
oh well live and learn.
Adding the server.properties also means the server is now discoverable.
I'll add a different issue for the case were there isn't a server.properties
Also, since yesterday, it should be possible to run the server from any directory, and it should fall back to the ~/.local/share/mcpelauncher directory, otherwise if libs/libminecraftpe.so exists, it'll use the current working directory as the source dir instead. Maybe you had an older version of Minecraft extracted in the CWD?
Also, the server now supports extracting (to the CWD), using the extract
option like this: ./server extract mcpe.zip
.
Tested with 1.2.7, 1.2.8, 1.2.9
mcpelauncher works fine with all of them.