Load Order

Use DML to manage activation and record the intended TTW order, then preserve New Vegas's timestamp-based plugin order.

Current DML version: v0.6.0-beta

This release has no dedicated TTW game type. Use a Fallout: New Vegas game type with a separate Pocket Wastelands profile. DML writes plugin files into profile storage, but it does not create DML_output, copy files into GameNative, or change plugin timestamps.

Four things that are easy to confuse

plugins.txt

Controls activation. DML writes only enabled plugin filenames, one per line, with no * prefix for TTW/New Vegas.

loadorder.txt

Records DML's full plugin list in app order, including disabled entries. Keep it as a reference, but do not treat it as the mechanism that orders TTW in-game.

Plugin timestamps

TTW uses New Vegas's system: ESM and ESP files are ordered by modification timestamp. Earlier timestamps load earlier; later timestamps load later.

Mod priority

Controls which mod wins loose-file conflicts. It is separate from plugin activation and plugin order.

Use LOOT as a check

LOOT can identify missing masters, warnings, dirty plugins, and order suggestions. For TTW, compare any result against the current TTW requirements and the known base shape below.

Run LOOT in a Windows environment that can see the same TTW plugins.
Read warnings before applying a sort.
Confirm that the official New Vegas masters, Fallout 3 masters, preorder packs, TaleOfTwoWastelands.esm, and YUPTTW.esm remain in the required shape.
Apply the intended order through the ESM and ESP modification timestamps in the actual Data folder GameNative will use.
If the files were prepared on PC, verify their timestamps again after copying them to Android and after later DML deployments.
Use DML's order view and loadorder.txt as a readable reference for the intended order.

DML does not apply TTW timestamps yet

Moving a plugin inside DML v0.6.0-beta changes DML's saved list and the generated loadorder.txt. It does not change the ESM or ESP file timestamp in Data. Copying loadorder.txt into GameNative therefore does not, by itself, change the real in-game order.

If you cannot inspect or preserve timestamps in the shared-storage Data folder used by GameNative, this guide cannot guarantee the exact TTW plugin order. Keep the plugin list conservative and verify the game carefully.

Write the current plugin files in DML

Open DML.
Select the Fallout: New Vegas game type and the Pocket Wastelands profile.
Deploy the current mod state.
Open the plugin list and enable only the TTW plugins that are actually installed.
Arrange the DML list to match the intended order below.
Tap Write Plugin Files.
Read DML's operation log and note the exact paths it reports for plugins.txt and loadorder.txt.

Starter loadorder.txt

This file is a readable record of the intended base TTW order. The same order still needs to be reflected by the plugin timestamps in Data.

FalloutNV.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
Fallout3.esm
Anchorage.esm
ThePitt.esm
BrokenSteel.esm
PointLookout.esm
Zeta.esm
CaravanPack.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
TaleOfTwoWastelands.esm
YUPTTW.esm

Starter plugins.txt

This is the activation list. TTW/New Vegas uses plain filenames here: no Fallout 4-style * prefixes. Keep only plugins that are installed and meant to be enabled.

FalloutNV.esm
DeadMoney.esm
HonestHearts.esm
OldWorldBlues.esm
LonesomeRoad.esm
GunRunnersArsenal.esm
Fallout3.esm
Anchorage.esm
ThePitt.esm
BrokenSteel.esm
PointLookout.esm
Zeta.esm
CaravanPack.esm
ClassicPack.esm
MercenaryPack.esm
TribalPack.esm
TaleOfTwoWastelands.esm
YUPTTW.esm

Copy the files into GameNative

Use the source paths printed in DML's operation log. The usual external profile-storage area is under Android/data/com.shonkware.droidmodloader/files/state/profiles/.
Use ZArchiver or another file manager that can request access through Android's system folder picker.
Copy both files to a temporary shared folder, such as Download/DML Plugin Transfer/.
Inside GameNative, copy both files to C:/users/xuser/AppData/Local/FalloutNV/. Use the corresponding user folder if your container does not use xuser.
Replace the old copies and launch TTW. plugins.txt controls activation; loadorder.txt remains a reference, while the ESM and ESP timestamps in Data control the actual TTW order.

The equivalent Windows location is:

%LOCALAPPDATA%/FalloutNV/

Troubleshooting

TTW launches as plain New Vegas: confirm the Pocket Wastelands profile is active and that plugins.txt contains TaleOfTwoWastelands.esm and YUPTTW.esm.
Plugins do not activate: confirm the correct plugins.txt is in GameNative's AppData/Local/FalloutNV folder and contains plain filenames without * prefixes.
The order is wrong: inspect the ESM and ESP modification timestamps in Data. Copying loadorder.txt alone does not set them.
DML wrote no files: confirm a saved plugin list exists, then tap Write Plugin Files and read the operation log.
The source path is inaccessible: grant your file manager access to the required Android/data folder through the Android system picker. Follow DML's logged path if it differs from the usual path.
There is no DML_output folder: that is expected in v0.6.0-beta. Use a temporary transfer folder you create yourself.
DML deploys to the wrong place: when asked for the Data Folder, select the TTW/New Vegas <Game Folder>/Data folder. If DML separately asks for the Game Root Folder, select the parent containing FalloutNV.exe and Data. Do not swap the two targets.