- Essentials 这个主要的jar文件包括了觉得部分内容，你几乎能在这里发现所有的API，所有的源代码，以及链接Essentials套件的代码.
- EssentialsChat in two packages, 'core' and 'extra'. The core package comes with the parts of essentials people usually use, and take little extra configuration, plugins in the extra package take a little more setting up, and it's recommended that you don't blindly install them unless you know what they do.
- EssentialsSpawn covers basic player spawning, this plugin lets you define the place people return to on death, as well as the place people initially end up when joining the server. The position can be changed ingame by a player with the correct permissions, and can be configured for everyone or per group.
- EssentialsAntiBuild is a build permissions system, this permission allows you to restrict who can build, or who can place/break what blocks. Useful for preventing players from placing lava, for example.
- EssentialsProtect is a basic world protection system, this module allows you to configure basic rules for the server to abide by, such as preventing creepers from destroying buildings, and preventing fire spread, controlling which mobs are allowed to spawn.
Other Essentials modules (which all require the main essentials.jar): EssentialsXMPP, EssentialsGeoIP
- EssentialsXMPP acts as a bridge between the server and the Jabber chat network, this plugin allows player chat to cross from services like GTalk and Facebook into the game, and can also be used to monitor the server for errors.
- EssentialsGeoIP provides Geographical IP lookup, that is the module can tell you roughly the location of where a player is logging in from, based on public IP databases.
Standalone modules: EssentialsGroupManager (GroupManager formerly developed by AnjoCaido)
- EssentialsGroupManager creates permissions system, this is used to create user groups for which players are part, this allows for ranks such as 'builder', 'mod', and 'admin'.
Essentials strives to be compatible with other plugins, with any major conflicts solved almost immediately, if the team was informed of a problem. Essentials command structure was designed to allow other plugins to override Essentials. The mantra being that Essentials should be your server bedrock, and on top of which you build your server, replacing parts of Essentials with other plugins as your needs require.
If for some reason you find that Essentials is overriding the command of your favourite plugin, you can always remove the bind from the plugin.yml file located in the essentials.jar, this will tell essentials to not even to try to bind to this command. This option should only be tried as a last resort if other avenues fail.