SteamWar/Paper
13
0
Fork 0
geforkt von Mirrors/Paper
Code Issues Pull-Requests 1 Projekte Releases Wiki Aktivität
537 Commits 4 Branches 1 Tag 296 MiB
Java 99.1%
Shell 0.9%
07c98ea2a4
Datei suchen
stevenh 07c98ea2a4 Added methods to support RemoteBukkit 
This means all commands even "default" server commands work within the command structure
returning output to the command sender

Updated default kick command to be compatible with kick + msg used by remote tools that work with hMod
2011-03-12 18:31:44 +00:00
src/main/java Added methods to support RemoteBukkit 2011-03-12 18:31:44 +00:00
.gitignore Modified .gitignore to remove Mac filesystem dust (/.DS_Store) 2011-02-05 21:43:43 +08:00
LGPL.txt We're LGPL. 2011-01-02 10:58:11 +01:00
LICENCE.txt We're LGPL. 2011-01-02 10:58:11 +01:00
pom.xml Kill stupid encoding warnings finally 2011-03-12 15:04:42 +01:00
README.md Added pull request conventions that should be followed if you want your pull request accepted. 2011-02-18 17:17:00 -05:00

README.md

CraftBukkit

A Bukkit (Minecraft Server API) implementation

Compilation

We use maven to handle our dependencies.

  • Install Maven 3
  • Check out and install Bukkit
    • Note: this is not needed as the repository we use has Bukkit too, but you might have a newer one (with your own changes :D)
  • Check out this repo and: mvn clean package

Coding and Pull Request Conventions

  • We generally follow the Sun/Oracle coding standards.
  • No tabs; use 4 spaces instead.
  • No trailing whitespaces.
  • No 80 column limit or 'weird' midstatement newlines.
  • The number of commits in a pull request should be kept to a minimum (squish them into one most of the time - use common sense!).
  • No merges should be included in pull requests unless the pull request's purpose is a merge.
  • Pull requests should be tested (does it compile? AND does it work?) before submission.

If you make changes or add net.minecraft.server classes it is mandatory to:

  • Get the files from the mc-dev repo - make sure you have the last version!
  • Mark your changes with:
    • 1 line; add a trailing: // CraftBukkit [- Optional reason]
    • 2+ lines; add
      • Before: // CraftBukkit start [- Optional comment]
      • After: // CraftBukkit end
  • Keep the diffs to a minimum (really important)

Follow the above conventions if you want your pull requests accepted.