[Feature request] AdvancedPortals migrator

[fabianmakila]

Feature request

Feature description
A migrator for migrating portals and destinations from AdvancedPortals to Multiverse-Portals.

How the feature is useful
I have multiple servers with over 50 portals and destinations (same as MV's anchors). Migrating all of those manually by hand would take months to complete. Hence a migrator would be useful for anyone deep in the AdvancedPortals ecosystem like I am. Also since Multiverse-Inventories already has a migrator I feel like this would fit nicely in.

Missing trigger block functionality from portals
The trigger block portal feature in AP is something that I've been utilizing quite a bit. To my knowledge there aren't currently a functionally equivalent counterpart in MVP, so that data would currently need to be dropped when migrating. The way the feature works is that the portal will only teleport player if they are standing inside the specified trigger block.

[benwoo1110]

I definitely see how this can save time for a small subset of users, but I don't think it will take months for just 50-100 portals, probably more like a few days. I will leave this open as a possible feature in the upcoming feature releases. However, the main blockers to this is the awful lack of any formal API documentation by AdvancePortal, and I am not too interested in reverse engineering their source code just to do an importer.

As for the trigger block, I don't think it matters as mv-portals works regardless of the portal fill used (or even just air). If you didn't want a player or group of players to use a portal, it should just simply be done with permissions instead of removing the portal fill.

[fabianmakila]

I totally forgot to check if they even had an API, whoops. Quite honestly I'm surprised that such widely used plugin is missing formal API so the thought didn't cross my mind. Implementing such migrator without proper API sure sounds one big PITA. One more reason for us to migrate lol.

But yeah, I meant 50+ portals per server and I have about 40 servers to migrate so it's gonna take me a good while to complete.

Some insight about how I currently use the triggerblock feature;
I have couple of servers where the hub portals can be "toggled" by using buttons, which are just command blocks that fill the portal with air or water. With the trigger block system it was enough to prevent players from entering the portals and also visually represented if the portal could be entered or not. It's not the prettiest solution, but it worked for that specific use-case.

However I do have a custom replacement in mind for those servers which utilizes dialogs instead of buttons and hooks directly into MVP for controlling the access and visuals. Permissions don't really work for me since the portals need to be togglable by non technical people, and the permission system isn't really designed for such a dynamical use. But as said, this I can work around.