Upstream/Vault
1
0
Fork 0
mirror of https://github.com/MilkBowl/Vault.git synced 2024-11-27 04:55:33 +01:00
Code Issues Projects Releases Wiki Activity
Vault of common APIs for Bukkit Plugins
844 Commits 4 Branches 2 Tags 118 MiB
Java 99.9%
Shell 0.1%
86c8e1c80d
Go to file
lSwagLordl 86c8e1c80d Add files via upload
2017-07-22 19:56:04 +02:00
.utility Update do-build.sh 2015-01-03 22:08:10 -08:00
lib Add files via upload 2017-07-22 19:55:22 +02:00
src/net/milkbowl/vault Add files via upload 2017-07-22 19:56:04 +02:00
.gitignore update gitignore 2014-05-08 19:21:58 -07:00
.travis.yml Migrate to use new travis container 2015-08-18 12:32:03 -07:00
build.xml cleanup javadoc generation, we still use the ant task 2014-01-14 14:39:45 -08:00
license.txt probably need to push the library too 2012-02-19 00:24:10 -08:00
plugin.yml add travis.yml, scripts, and settings to get auto-building. 2014-06-24 12:03:24 -07:00
pom.xml missed the publish repository. 2016-08-02 18:02:06 -07:00
README.md Fixed typographical error, changed accomodate to accommodate in README. 2015-09-30 13:21:54 -04:00

README.md

Vault - Abstraction Library for Bukkit - Travis-ci

For Developers:

Please see the VaultAPI page for information on developing with Vault's API. In the past you would use the same artifact as servers installed, but the API has now been split from the main project and is under a different artifact name. Please make sure you accommodate for this change in your build process.

Installing

Installing Vault is as simple as copying the provided "Vault.jar" to your "/plugins" directory and the rest is automatic! If you wish to perform configuration changes, this can be done via a configuration file but should not be necessary in most cases. See the "Advanced Configuration" section for more information.

Why Vault?

I have no preference which library suits your plugin and development efforts best. Really, I thought a central suite (rather...Vault) of solutions was the the proper avenue than focusing on a single category of plugin. That's where the idea for Vault came into play.

So, what features do I think you'll like the most?

  • No need to include my source code in your plugin All of Vault is run in its own plugin, so all you need to do is obtain an instance of it! This simplifies issues with multiple plugins using the same namespaces. Just simply add Vault.jar to your download zip file!
  • Broad range of supported plugins I wanted an abstraction layer not only for Economic plugins but also Permission plugins as well. The future will likely add more, but what types, I have yet to decide, let me know!
  • Choice! That's half the fun of Bukkit, we get to choose what to use! More choice has never hurt developers so here's to choice!

Permissions

  • vault.admin
    • Determines if a player should recieve the update notices

License

Copyright (C) 2011 Morgan Humes morgan@lanaddict.com

Vault is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Vault is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with Vault. If not, see http://www.gnu.org/licenses/.

Building

Vault comes with all libraries needed to build from the current branch and also comes with an Apache Ant build file (build.xml).

Dependencies

Because Vault provides a bridge to other plugins, their binaries will be required to build from. To ease this, they have been included in the lib folder and will be updated from time to time. For plugin developers, it is not necessary to use these libraries when implementing Vault. You will only need to compile against Vault.

Supported Plugins

Vault provides abstraction for the following categories and plugins. If you have your own plugin that you believe should be supported, fork Vault or create a patch with the necessary changes. Additionally you can create an issue on Github and we'll get to it at our convenience.