OpenSource/PaperMC
OpenSource/PaperMC
1
0
Fork 0
mirror of https://github.com/PaperMC/Paper.git synced 2025-01-20 07:34:48 +01:00
Code Issues Projects Releases Packages Wiki Activity
PaperMC/paper-api
History
Bukkit/Spigot 531a69463a Added the SPAWN_CHANGE event, which occurs when a world's spawn is changed. 
This event includes the world who's spawn changed and its previous spawn location.

To listen for this event:
  PluginManager pm = getServer().getPluginManager();
  YourWorldListener worldListener = new YourWorldListener(this);
  pm.registerEvent(Event.Type.SPAWN_CHANGE, worldListener, Priority.Normal, this);

To use this event:
  public class YourWorldListener extends WorldListener {
      @Override
      public void onSpawnChange(SpawnChangeEvent event) {
          World world = event.getWorld();
          Location previousLocation = event.getPreviousLocation();
      }
  }

By: William Bowers <william.bowers@gmail.com>
2011-03-29 01:59:00 -07:00
..
src/main/java/org/bukkit Added the SPAWN_CHANGE event, which occurs when a world's spawn is changed. 2011-03-29 01:59:00 -07:00
.gitignore Added /.DS_Store (Mac filesystem dust) to .gitignore (https://github.com/Bukkit/Bukkit/issues/#issue/46) 2011-01-23 04:19:03 +08:00
LICENCE.txt We're GPL. 2011-01-02 10:57:42 +01:00
pom.xml Implemented ebeans 2011-04-01 16:04:43 +01:00
README.md Updated README.md 2011-03-25 23:22:00 +01:00

README.md

Bukkit

A Minecraft Server API.

Website: http://bukkit.org
Bugs/Suggestions: http://leaky.bukkit.org

Compilation

We use maven to handle our dependencies.

  • Install Maven 3
  • Check out this repo and: mvn clean install

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 midstatement newlines.
  • Proper javadoc for each method added/changed to describe what it does.
  • 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.

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