An advanced portals plugin for bukkit
Go to file
Sekwah 06722986be
chore(release): 0.6.0
2021-05-19 20:33:41 +01:00
.github/workflows chore(release): 0.5.14-0 2021-05-12 02:47:47 +01:00
docs chore(release): 0.6.0 2021-05-19 20:33:41 +01:00
gradle/wrapper add bungeecord portal teleport destination 2020-01-20 19:55:18 +09:00
src/main chore(release): 0.6.0 2021-05-19 20:33:41 +01:00
.gitignore Switched to gradle actions 2021-03-23 01:36:34 +00:00
.versionrc.js ci: Updating uploads 2021-05-19 00:48:41 +01:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-11-28 22:50:21 +00:00
DragAndDropStarter.bat Fixed bungee issues and protection 2020-06-18 03:37:06 +01:00
LICENSE.md Updated license 2019-09-07 23:53:17 +01:00
README.md docs: Updated README.md 2021-05-14 11:44:04 +01:00
build.gradle ci: FIxed changelog location 2021-05-19 20:31:56 +01:00
gradle.properties Updated build info and some other workflows 2021-04-05 14:47:34 +01:00
gradlew chmod 2021-03-23 01:35:23 +00:00
gradlew.bat Cleaned up gradle files 2019-12-30 15:18:14 +00:00

README.md

Advanced Portals

Discord

Advanced Portals GitHub Workflow Status

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

List Of Commands

Spigot Page

Bukkit Page

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

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)

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)