Multiverse-SignPortals and Multiverse-NetherPortals are incompatible.

[ArtisticTuxedo]

Information

• Server version: This server is running Paper version git-Paper-478 (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: 32875b4)
  You are running the latest version
  Previous version: git-Paper-470 (MC: 1.19.4)

• Full output of /mv version -p: https://paste.gg/p/anonymous/720ffbc5f1454aefb05c1c1069e19fc3

• Server log: https://gist.github.com/ArtisticTuxedo/0dba35029ff1ca345ee29224687d77bd

Details

I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

Description
Portal-style sign portals do not work when the sub-module Multiverse-NetherPortals is also installed.

Steps to reproduce

1. Create a world with /mv create {NAME} {ENV}
2. Create a nether portal in the current world.
3. Place a sign on the portal frame.
4. Write on sign:

 [mv]
{NAME}

• [mv] should turn green.

5. Step into the portal.
6. [mv] turns blue and the portal doesn't execute the proper behavior:

• If a nether world is linked to the current world through /mvnp link {end|nether} [FROM_WORLD] {TO_WORLD}, it will take you to the world that has been linked through the command, no matter what you typed into the sign.
• If no nether world is linked to the current world, it will not take you anywhere.

Expected behavior
The sign portal should override Multiverse-NetherPortals' linking between worlds so that both submodules can work seamlessly.

[CountFive]

Can confirm. Running Core/Portals/NetherPortals/SignPortals on Magma. Experience is the same... "[mv]" turns blue but the Nether Portal continues to, well, be a Nether Portal.

Standalone signs continue to work.