65 lines
3.7 KiB
Markdown
65 lines
3.7 KiB
Markdown
|
|
|
|
[](https://discord.gg/fAJ3xJg)
|
|
[](https://github.com/sekwah41/Advanced-Portals/graphs/contributors)
|
|
[](https://github.com/sekwah41/Advanced-Portals/issues)
|
|
[](https://github.com/sekwah41/Advanced-Portals/pulls)
|
|
[](https://github.com/sekwah41/Advanced-Portals/network/members)
|
|
[](https://github.com/sekwah41/Advanced-Portals/stargazers)
|
|
[](https://github.com/sekwah41/Advanced-Portals/blob/master/LICENSE.md)
|
|
|
|
Advanced Portals 
|
|
==============
|
|
An advanced portals plugin for bukkit made by sekwah41 designed to have a wide range of features which are easy to use. It adds a bunch of commands to create and edit portals and destinations. This plugin not only enable normal teleportation but also cross server teleportation for networks using bungee.
|
|
|
|
# Recode
|
|
We are currently slowly working on a complete re-code of the plugin with a full API.
|
|
For now maintaining the current 1.13+ spigot versions is our main priority.
|
|
|
|
# Help
|
|
[Command Documentation & Guides](https://www.guilded.gg/Sekwah/groups/MDqAZyrD/channels/72ffdaa3-9273-4722-bf47-b75408b371af/docs/1807463914)
|
|
|
|
[List Of Commands](https://github.com/sekwah41/Advanced-Portals/wiki/Commands)
|
|
|
|
[Spigot Page](https://www.spigotmc.org/resources/advanced-portals.14356/)
|
|
|
|
[Bukkit Page](http://dev.bukkit.org/bukkit-plugins/advanced-portals/)
|
|
|
|
# Usage Data
|
|
Usage stats can be found here https://bstats.org/plugin/bukkit/AdvancedPortals
|
|
|
|
# API
|
|
|
|
The api isn't implemented in this version, sorry for any inconvenience. Check the recode tree for possibly a working recode at some point.
|
|
|
|
# Contributing
|
|
|
|
Don't worry about updating the file numbers in `bungee.yml`, `plugin.yml` and `AdvancedPortalsPlugin.java`.
|
|
They will be updated automatically before builds.
|
|
|
|
Please ensure that your commits are in the following style for PR's
|
|
|
|
https://www.conventionalcommits.org/en/v1.0.0/
|
|
|
|
Accepted tags mostly follow the Angular style and are meant to only loosely be followed.
|
|
When commits close an issue refer in the commit description in the following style (Refs #1, #2, #3)
|
|
## Types available
|
|
* **build**: Changes that affect the build system or external dependencies
|
|
* **ci**: Changes to our CI configuration files and scripts
|
|
* **docs**: Documentation only changes
|
|
* **feat**: A new feature
|
|
* **fix**: A bug fix
|
|
* **perf**: A code change that improves performance
|
|
* **refactor**: A code change that neither fixes a bug nor adds a feature
|
|
* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
|
|
<!---
|
|
We don't currently do tests. But in case.
|
|
* **test**: Adding missing tests or correcting existing tests
|
|
-->
|
|
|
|
## Scopes available
|
|
Scopes are only needed if relating to specific features just to make them easier to find.
|
|
_I'll expand the list as I work more on the project._
|
|
* **proxy** (Proxy specific features and issues)
|
|
|