Commits
md_5 authored e2699636407
| 1 1 | /** |
| 2 2 | * The root package of the Bukkit API, contains generalized API classes. |
| 3 - | * |
| 4 - | * Note: While the Bukkit API makes every effort to ensure stability, this is |
| 5 - | * not guaranteed, especially across major versions. In particular the following |
| 6 - | * is a (incomplete) list of things that are <b>not</b> API. |
| 7 - | * <ul> |
| 8 - | * <li>Implementing interfaces. The Bukkit API is designed to only be |
| 9 - | * implemented by server software. Unless a class/interface is obviously |
| 10 - | * designed for extension (eg {@link org.bukkit.scheduler.BukkitRunnable}), or |
| 11 - | * explicitly marked as such, it should not be implemented by plugins. Although |
| 12 - | * this can sometimes work, it is not guaranteed to do so and resulting bugs |
| 13 - | * will be disregarded.</li> |
| 14 - | * <li>Constructing inbuilt events. Although backwards compatibility is |
| 15 - | * attempted where possible, it is sometimes not possible to add new fields to |
| 16 - | * events without breaking existing constructors. To ensure that the API |
| 17 - | * continues to evolve, event constructors are therefore not plugin API.</li> |
| 18 - | * <li>Implementation classes. Concrete implementation classes packaged with |
| 19 - | * Bukkit (eg those beginning with Simple) are not API. You should access them |
| 20 - | * via their interfaces instead.</li> |
| 21 - | * </ul> |
| 22 3 | */ |
| 23 4 | package org.bukkit; |