By default, any worldspace, or child worldspace whose parent worldspace, that is not part of the "PVHValidWorldspaces" formlist will have severely reduced functionality. The Vertibird can still be summoned to these worldspaces, and a custom home base can be set/flown to, but apart from that no other locations can be selected from the flight control terminal.

In order to add custom support, start with both your plugin and the Player Vertibird.esm file as a master.

Any worldspaces need to be added to the "PVHValidWorldspaces" formlist, which can be done via the following function, note this needs to be ran every time the game is restarted:

ListAddForm PVHValidWorldspaces WorldSpaceID

From there, a new copy of the flight control terminal needs to be made, "PVHTerminal" can be copied as a starting reference point.  To set up a new landing location through the terminal, you need three things; a landing marker, an exit marker, and a numerical ID of your own choice.

Both the landing marker itself, "PVHMarkerLanding", and exit marker, "xMarkerHeading" need to be placed in the world somewhere. Make sure both are Persistent References and give both a unique Reference Editor ID.

The final needed thing is the unique numerical ID to assign to the destination. These are assigned via the terminal result script as specified below, and they only need to be unique per worldspace for the most part, as their only purpose is to prevent you from flying to the same spot you are already at. Try to avoid overlap with the base ones I have chosen for the Mojave though, they can be viewed in "PVHGeneralQuestScript"

After the markers are placed, in the Terminal you can assign each option to reference a particular marker by using the following code in the Item Result Script:

PVHGeneralQuest.Destination = ID ;This is the unique number identifier you choose for this zone.
PVHGeneralQuest.rDestination = LandingMarkerRef ;This is where the Vertibird model moves to.
PVHGeneralQuest.rDestinationExit = LandingMarkerExitRef ;This is where the player exits.
PVHGeneralQuest.iLongFlight = # ;This is explained further down.
PVHGeneralQuest.rFunctionToCall = FunctionEditorID ;This function is called when flight starts.


In the conditions field for this entry, create a new condition, and set it to:

GetQuestVariable PVHGeneralQuest Location != ID ;Replace ID with the same number you chose above.


If everything is set up correctly, after choosing this option and pressing the "Take Off" button, the Vertibird will begin traveling, and will land at the specified destination in 30 seconds.

If at any point the variable PVHGeneralQuest.iLongFlight is set to any non-zero value, the flight will instead fade to black and pass the "iLongFlight" variable as hours in game time before landing at the new destination. Upon landing it will be reset to 0. I personally use this for flying between main/DLC worldspaces, but it can used however you see fit.

If the PVHGeneralQuest.rFunctionToCall reference is set, upon flight starting it will call whatever function is specified and then zero itself out. I personally use this to enable/disable radio stations and a few vanilla tracking quests upon flying from a base game location to a DLC zone or vice-versa, but you may use it for whatever you wish. Just be sure to zero it out if the player changes destination!

Once this is set up, place the base terminal you made somewhere in the game world, be it dummy cell, or even in the Vertibird's own interior cell alongside the other terminals that are off to the side, make it a Persistent Reference and initially disable it. Give it a Reference Editor ID of "PVHTerminalWorldspaceEditorIDREF", so PVHTerminal + Worldspace Editor ID + Ref, for example, the base New Vegas Mojave terminal is "PVHTerminalWastelandNVREF", and Zion is "PVHTerminalNVDLC02ZionCanyonREF".

From there, any time you enter the Vertibird or otherwise change worldspaces, it will update the shown location listings when you access the flight control terminal.

However, if you wish for the Vertibird to be unable to be summoned in your worldspace to begin with, simply add the offending worldspace to the "PVHInvalidWorldspaces" formlist, and again this needs to be ran every time the game is restarted:

ListAddForm PVHInvalidWorldspaces WorldSpaceID

This can be used on child worldspaces as well to exclude only them, while the main worldspace is fine. For example, NVDLC03Higgs is forbidden while NVDLC03BigMt is perfectly fine.

I apologies if this explanation is confusing, I have tried to make it as in-depth as possible, but feel free to ask for assistance if needed.