[Feature] Define tunnels without using the API.

[TheDeafCreeper]

Having the ability to define tunnels without needing to use the API, such as with a command or configuration options, would allow people with less development skills to utilize the feature.

Main places I can image you'd want to be able to define tunnels manually would be:

• When you use Command Blocks to teleport.
• If you're using a plugin that allows teleportation with no integration addon.

How I imagine implementation would go would either be a command with a format similar to this: /registertunnel NAME xOrigin yOrigin zOrigin worldName xDest yDest zDest worldName

or a configuration file with entries similar to this (yaml format example):

tunnels:
  name:
    origin:
      x: 0
      y: 0
      z: 0
      world: world
    destination:
      x: 0
      y: 0
      z: 0
      world: world_the_nether

[whimxiqal]

I'll tentatively say that I don't want Tunnels to ever be editable from in-game. It can be easily misused by admins who don't know that it's just for algorithm-purposes and doesn't actually do any sort of transportation for the user, and it just adds command bloat.

For existing plugins that provide teleportation, and isn't natively integrated with Journey (as every plugin ever, at the moment,) then an integration plugin should be made using Journeys API or the plugin should be made to natively support Journey as a tool.

As for command blocks, I think that's a bridge I'll never cross. I think the admin should just download a popular portals plugin instead of teleportation command blocks. Or, they should make a simple plugin (and learn how, if necessary) if that level of control is wanted.