public class Core
-extends org.bukkit.plugin.java.JavaPlugin
-| Modifier and Type | -Field and Description | -
|---|---|
static Core |
-instance
-plugin instance
- |
-
static java.util.HashMap<de.joethei.core.api.CustomPlayer,java.lang.String> |
-nicks
-nick names of players
- |
-
| Modifier and Type | -Method and Description | -
|---|---|
static Core |
-getInstance() |
-
static void |
-log(java.util.logging.Level level,
- java.lang.String string) |
-
void |
-onDisable() |
-
void |
-onEnable() |
-
static de.joethei.core.api.MySQL |
-returnSQL() |
-
getCommand, getConfig, getDatabase, getDatabaseClasses, getDataFolder, getDefaultWorldGenerator, getDescription, getLogger, getPlugin, getPluginLoader, getProvidingPlugin, getResource, getServer, isEnabled, isInitialized, isNaggable, onCommand, onLoad, onTabComplete, reloadConfig, saveConfig, saveDefaultConfig, saveResource, setNaggable, toStringequals, getName, hashCodegetClass, notify, notifyAll, wait, wait, waitpublic static Core instance-
public static java.util.HashMap<de.joethei.core.api.CustomPlayer,java.lang.String> nicks-
public static Core getInstance()-
public static de.joethei.core.api.MySQL returnSQL()-
public static void log(java.util.logging.Level level, - java.lang.String string)-
level - Log levelstring - Stringpublic void onEnable()-
onEnable in interface org.bukkit.plugin.PluginonEnable in class org.bukkit.plugin.java.JavaPluginpublic void onDisable()-
onDisable in interface org.bukkit.plugin.PluginonDisable in class org.bukkit.plugin.java.JavaPlugin| Modifier and Type | -Field and Description | -
|---|---|
static Core |
-Core.instance
-plugin instance
- |
-
| Modifier and Type | -Method and Description | -
|---|---|
static Core |
-Core.getInstance() |
-
| Class | -Description | -
|---|---|
| Core | -
- main class
- |
-
| Class and Description | -
|---|
| Core
- main class
- |
-
Each package has a page that contains a list of its classes and interfaces, with a summary for each. This page can contain six categories:
-Each class, interface, nested class and nested interface has its own separate page. Each of these pages has three sections consisting of a class/interface description, summary tables, and detailed member descriptions:
-Each summary entry contains the first sentence from the detailed description for that item. The summary entries are alphabetical, while the detailed descriptions are in the order they appear in the source code. This preserves the logical groupings established by the programmer.
-Each annotation type has its own separate page with the following sections:
-Each enum has its own separate page with the following sections:
-Each documented package, class and interface has its own Use page. This page describes what packages, classes, methods, constructors and fields use any part of the given class or package. Given a class or interface A, its Use page includes subclasses of A, fields declared as A, methods that return A, and methods and constructors with parameters of type A. You can access this page by first going to the package, class or interface, then clicking on the "Use" link in the navigation bar.
-There is a Class Hierarchy page for all packages, plus a hierarchy for each package. Each hierarchy page contains a list of classes and a list of interfaces. The classes are organized by inheritance structure starting with java.lang.Object. The interfaces do not inherit from java.lang.Object.
The Deprecated API page lists all of the API that have been deprecated. A deprecated API is not recommended for use, generally due to improvements, and a replacement API is usually given. Deprecated APIs may be removed in future implementations.
-The Index contains an alphabetic list of all classes, interfaces, constructors, methods, and fields.
-These links take you to the next or previous class, interface, package, or related page.
-These links show and hide the HTML frames. All pages are available with or without frames.
-The All Classes link shows all classes and interfaces except non-static nested types.
-Each serializable or externalizable class has a description of its serialization fields and methods. This information is of interest to re-implementors, not to developers using the API. While there is no link in the navigation bar, you can get to this information by going to any serialized class and clicking "Serialized Form" in the "See also" section of the class description.
-The Constant Field Values page lists the static final fields and their values.
-