[SPIGOT-1946] Gateway PortalType Enum Created: 17/Mar/16 Updated: 03/May/21 |
|
| Status: | Open |
| Project: | Spigot |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor |
| Reporter: | Parker Hawke | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | 1.9, PortalType | ||
| Environment: |
N/A |
||
| Plugin: | N/A |
| Description |
|
In the PortalType Enum, add PortalType.GATEWAY to represent the gateway generated after defeating the Ender Dragon public enum PortalType { /** * This is a Nether portal, made of obsidian. */ NETHER, /** * This is an Ender portal. */ ENDER, // start new /** * This is an End gateway portal */ GATEWAY, // end new /** * This is a custom Plugin portal. */ CUSTOM; } |
| Comments |
| Comment by Doc [ 03/May/21 ] |
|
In current version the PortalType are only used in a Deprecated method.
|
| Comment by Martoph [ 02/May/21 ] |
|
If I'm not mistaken there's no current API that uses PortalType ? |
| Comment by Mmaarten [ 24/Apr/21 ] |
|
both should be added separately as they have different functionality. And there is no way to easily ditinguish the type of portal with the current spigot API |
| Comment by Joshua Price [ 19/Feb/21 ] |
|
I'm working on an implementation of this and I realised that there are two types of gateways—there are the ones at the main island and there's the ones that teleport you back to the main end island. Should I implement them both separately or have just one type representing both? |
| Comment by Joshua Price [ 19/Feb/21 ] |
|
I'll gladly do this if/when I get PR permissions. |