Revert 61305c3a9d223e337fd20acea4e0c16297df98e5 ... d25bf2362ee82acfe3eecc6bcfaeeb4ea51dd3a6
parent
d25bf2362e
commit
cae703db5a
|
@ -0,0 +1,43 @@
|
|||
Are you [[interested in developing|How can I help#wiki-pullrequest]]? Do you just want your own local copy of Multiverse? Look no further - this page aims to describe how to build any Multiverse plugin from scratch, regardless of your reason.
|
||||
|
||||
---
|
||||
|
||||
## Requirements
|
||||
|
||||
In order to get the Multiverse source and build a plugin, your system must already have the following software:
|
||||
|
||||
<table>
|
||||
<tr><th>Software</th><th>Required</th><th>Recommended</th></tr>
|
||||
<tr><td><a href="http://java.com/">Java</a></td><td>5.0</td><td>6.0</td></tr>
|
||||
<tr><td><a href="http://maven.apache.org/">Maven</a></td><td>2.2</td><td>3.0</td></tr>
|
||||
<tr><td><a href="http://git-scm.com/">Git</a></td><td>1.6</td><td>1.7</td></tr>
|
||||
</table>
|
||||
|
||||
Windows users will likely have to download installers for each from the respective sites; Linux users can likely find these packages in their distribution's package manager. For Mac users, source-based installers (or alternative package managers like [Homebrew](http://mxcl.github.com/homebrew/)) are the preferred method.
|
||||
|
||||
---
|
||||
|
||||
## Git the source
|
||||
|
||||
Once you have all the prerequisites installed, go ahead and fetch the source from GitHub:
|
||||
|
||||
$ git clone git://github.com/Multiverse/Multiverse-Core.git
|
||||
|
||||
(Note that in this command, and from this point on, you can replace `Core` with the name of any other Multiverse plugin - `Portals`, `NetherPortals`, etc. - to build that plugin.)
|
||||
|
||||
Once you have the source cloned, everything should be ready. However, if you want to go back to commits before [443d62580ba24c4f225ffca0067bc914cf7f5a6b](https://github.com/Multiverse/Multiverse-Core/commit/443d62580ba24c4f225ffca0067bc914cf7f5a6b) you'll need to fetch some of the Git submodules that the Multiverse project uses. Move into the cloned directory, then update your submodules:
|
||||
|
||||
$ cd Multiverse-Core
|
||||
$ git submodule update --init --recursive
|
||||
|
||||
After that operation completes, you should have the complete source tree checked out for your preferred Multiverse plugin.
|
||||
|
||||
---
|
||||
|
||||
## Build the plugin
|
||||
|
||||
Once the source is cloned, building is easy. Simply run Maven to fetch all the other dependencies for Multiverse, run the tests, and generate a JAR file with your plugin:
|
||||
|
||||
$ mvn install
|
||||
|
||||
The final plugin will be in the `target` folder. Enjoy!
|
1
FAQ.md
1
FAQ.md
|
@ -126,7 +126,6 @@ This will tell Multiverse to *never* adjust the spawn, even on world reload or s
|
|||
## <a name="modeenforce" href="#wiki-modeenforce">•</a>Mods/OPs/Players keep having their game mode switched!
|
||||
New builds of Multiverse-Core include an extra permission to prevent automatic mode-switching. This permission takes the form:
|
||||
|
||||
I CANT DOWNLOAD THE STABLE BUKKIT PLEASE ADD ANOTHER LINK!!!!!!
|
||||
mv.bypass.gamemode.WORLD_NAME
|
||||
|
||||
With this new permission, server owners can pick particular users to ignore some (or all) of the game mode settings on each world when teleporting between them. For example, a player with `mv.bypass.gamemode.*` could be an admin, keeping their creative mode setting even in survival worlds. Just set the right permissions in your preferred plugin and you're good to go.
|
Loading…
Reference in New Issue