diff options
| -rw-r--r-- | GETTING-STARTED.md | 38 |
1 files changed, 12 insertions, 26 deletions
diff --git a/GETTING-STARTED.md b/GETTING-STARTED.md index 0364c9596..6bc4b4e5e 100644 --- a/GETTING-STARTED.md +++ b/GETTING-STARTED.md @@ -7,7 +7,7 @@ If you don't play Minecraft or don't have a great knowledge of the basic systems I'd say that the important topics are: -* Differnt types of blocks and how they act. +* Different types of blocks and how they act. * Mobs, what they do and how. * Redstone, pistons, and automation. * Farming. @@ -18,7 +18,7 @@ Useful Resources * [Minecraft Wiki](http://minecraft.gamepedia.com/Minecraft_Wiki) * [Minecraft Protocol Wiki](http://wiki.vg) - * [Lua API Documentation](http://mc-server.xoft.cz/LuaAPI) + * [Lua API Documentation](http://api-docs.cuberite.org) * [VS2013 Community Edition Download](https://www.visualstudio.com/products/visual-studio-community-vs) Setting up a Dev Environment @@ -63,15 +63,15 @@ The Cuberite repo has recently been rearranged for better code separation and ot It's split into logical areas for blocks, the protocol handling and other things. * `lib` This holds all the 3rd party libraries for Cuberite. You basically don't need to touch these, and we're thinking of switching them into submodules soon. - * `MCServer` - This folder isn't greatly named, but it contains the default plugins and environment to actually run the server. You'll find the executable (named `MCServer`) here and in the `plugins` subdir the default plugins. The config files are also stored here. Config files with `.example.ini` on the end are generated by the server or source control and should be left alone, instead you should copy them to a file without the `example` in the name which will be prioritised over the generated ones. + * `Server` + This contains the default plugins and environment to actually run the server. You'll find the executable (named `Cuberite`) here and in the `plugins` directory the default plugins. The config files are also stored here. Config files with `.example.ini` on the end are generated by the server or source control and should be left alone, instead you should copy them to a file without the `example` in the name which will be prioritised over the generated ones. -Code Styles ------------------- +Code Style +---------- -Mainly follow the code styles in [CONTRIBUTING.md](https://github.com/cuberite/cuberite/blob/master/CONTRIBUTING.md), which is definitely an important read. +You should follow the code style guidelines in [CONTRIBUTING.md](https://github.com/cuberite/cuberite/blob/master/CONTRIBUTING.md), as well as other C++ best practices. -Note that there is a script file, $/src/CheckBasicStyle.lua, that can check some common violations of the coding style. You should run this file to check your code regularly. This script is run during the integration builds and if it fails, the build will fail. Note that you need Lua installed in order to run this script. +Note that there is a script file, $/src/CheckBasicStyle.lua, that can check some common violations of the coding style. You should run this file to check your code regularly. This script is run during the integration builds and if it fails, the build will fail. Note that you need Lua installed in order to run this script. It is recommended to set this up as a pre-commit hook and doing so is covered in CONTRIBUTING.md. How to Build @@ -94,29 +94,15 @@ You need to first generate a solution file by executing `cmake .` on the command How to Run ---------- -The server can be run (on *nix) by a simple `./MCServer` in the `MCServer` directory. On first run it will generate the world and start a server on the default port (configurable in `settings.ini`) so you can connect in minecraft via `localhost`. Note that if you build a debug version, the executable will be names `MCServer_debug` instead +The server can be run (on *nix) by a simple `./Cuberite` in the `Cuberite` directory. On first run it will generate the world and start a server on the default port (configurable in `settings.ini`) so you can connect in minecraft via `localhost`. Note that if you build a debug version, the executable will be names `Cuberite_debug` instead Where to Get Started ------------------------------- -There are a few fairly easy issues for you to get started with, as well as some more difficult but interesting ones. - -**Easy**: - - * #140 - * #493 - * #577 - * #381 - * #752 - * Clean up some of the compiler warnings. (Check [Travis CI](http://travis-ci.org/cuberite/cuberite) for a list of them.) With clang, there are over 10000 lines of warnings to clean up. - -**More Difficult**: - - * #133 - * #134 - * #215 +Issues that should be easy to get started with are tagged as [easy](https://github.com/cuberite/cuberite/issues?q=is%3Aopen+is%3Aissue+label%3Aeasy) in GitHub issues. Other good places to get started are: -You may also want to write some plugins. They are written in lua, with excellent API documentation available via [APIDump](http://api-docs.cuberite.org). The [Core](https://github.com/mc-server/Core) plugin should also help quite a bit here. + * Cleaning up some of the compiler warnings. (Check [Travis CI](http://travis-ci.org/cuberite/cuberite) for a list of them.) With clang, there are over 10000 lines of warnings to clean up. + * Writing some plugins: They are written in lua, with excellent API documentation available via [APIDump](http://api-docs.cuberite.org). The [Core](https://github.com/cuberite/Core) plugin should also help quite a bit here. Special Things --------------------- |