Motor Town Dedicated Server Vortex Extension
Vortex support for the Motor Town: Behind The Wheel DEDICATED SERVER.
Install it in Vortex: Extensions tab, drag this zip onto the drop area, then
restart Vortex. The dedicated server appears as its own managed game.
Routes each kind of mod where it actually belongs:
paks MotorTown\Content\Paks
UE4SS Lua mods MotorTown\Binaries\Win64\ue4ss\Mods
UE4SS loader MotorTown\Binaries\Win64
Blueprint mods MotorTown\Content\Paks\LogicMods
Also registers RunDedicatedServer.bat as a tool, so you can start the server
from Vortex.
This is for the dedicated server, app 2223650. It is not the extension for the
game client.
Changelog for 1.1.0
1.1.0
FIXED - Vortex can find the server.
The extension asked Steam for the game client's app ID, so discovery failed
on a machine with only the dedicated server installed. It asks for the
server's own app now.
FIXED - UE4SS Lua mods went where UE4SS does not look.
They deployed under the Paks folder. They now go to
Binaries\Win64\ue4ss\Mods, and a Lua mod packaged with its own wrapper
folder has that wrapper stripped rather than double-nested.
FIXED - UE4SS itself installs correctly.
A UE4SS release ships a Lua entry point next to its proxy DLL, so it matched
the Lua mod type and landed in the wrong place. The loader type is tested
first now, and keeps the ue4ss tree intact under Binaries\Win64.
NEW - Blueprint (LogicMods) mod type.
Offered in the mod type dropdown rather than guessed. A Blueprint pak and a
content pak are the same kind of file, and guessing wrong deploys a mod that
silently does nothing.
NEW - Run Dedicated Server tool.
RunDedicatedServer.bat is registered, so the server starts from Vortex.
FIXED - Deployment worked only if UE4SS was already installed.
Vortex probes every mod type's destination to decide which deployment
methods it can use, and a missing folder failed that probe for the whole
game rather than just that type. All four destinations are created at setup.
Install it in Vortex: Extensions tab, drag this zip onto the drop area, then
restart Vortex. The dedicated server appears as its own managed game.
Routes each kind of mod where it actually belongs:
paks MotorTown\Content\Paks
UE4SS Lua mods MotorTown\Binaries\Win64\ue4ss\Mods
UE4SS loader MotorTown\Binaries\Win64
Blueprint mods MotorTown\Content\Paks\LogicMods
Also registers RunDedicatedServer.bat as a tool, so you can start the server
from Vortex.
This is for the dedicated server, app 2223650. It is not the extension for the
game client.
Changelog for 1.1.0
1.1.0
FIXED - Vortex can find the server.
The extension asked Steam for the game client's app ID, so discovery failed
on a machine with only the dedicated server installed. It asks for the
server's own app now.
FIXED - UE4SS Lua mods went where UE4SS does not look.
They deployed under the Paks folder. They now go to
Binaries\Win64\ue4ss\Mods, and a Lua mod packaged with its own wrapper
folder has that wrapper stripped rather than double-nested.
FIXED - UE4SS itself installs correctly.
A UE4SS release ships a Lua entry point next to its proxy DLL, so it matched
the Lua mod type and landed in the wrong place. The loader type is tested
first now, and keeps the ue4ss tree intact under Binaries\Win64.
NEW - Blueprint (LogicMods) mod type.
Offered in the mod type dropdown rather than guessed. A Blueprint pak and a
content pak are the same kind of file, and guessing wrong deploys a mod that
silently does nothing.
NEW - Run Dedicated Server tool.
RunDedicatedServer.bat is registered, so the server starts from Vortex.
FIXED - Deployment worked only if UE4SS was already installed.
Vortex probes every mod type's destination to decide which deployment
methods it can use, and a missing folder failed that probe for the whole
game rather than just that type. All four destinations are created at setup.
Download Links
Report a problem
Motor Town Dedicated Server Vortex Extension
Advertisement
Remove ads