Professional Ship Simulator Mod Support: Tools, Editors & SDK

Professional Ship Simulator ships with a Steam Workshop pipeline and a pair of built-in editors, giving creators everything they need to publish harbours, ships, and missions without leaving the client. Because the game launched on September 16, 2026 (Steam App ID 3636930), the Professional Ship Simulator mod support stack is brand new, and the first wave of authors is still mapping out which tools are stable. This guide breaks down the official editors, the Unreal Engine SDK workflow, and the upload pipeline so you know exactly what runs today, what to avoid, and where the new modding news lives once the workshop fills up.

Why Professional Ship Simulator Mod Support Matters From Day One

A sim game without modding tools is a closed museum. The developer, NAUTIC XP, made Professional Ship Simulator mod support a launch-day priority because the genre lives and dies on community content: new harbours for repeat players, repaints for company liveries, and full ship overhauls that push the game beyond its stock roster. Without those pipelines, the Early Access period would feel thin after the first twenty hours of piloting tugs and tankers.

What separates PSS from many of its peers is that the tools are integrated directly into the game client rather than shipped as a separate dev kit download. According to the official NauticXP Workshop install reference, players open PSS, jump to the Editor section, and press "update mods" — the client then pulls every subscribed Workshop item into local storage. That workflow matters because it eliminates the brittle "drop files into AppData" pattern that broke countless older sim mods.

The big caveat is that PSS is in Early Access, and the toolset is still hardening. Community reports suggest some mod types (notably full mission overhauls) return validation errors on first upload. The Professional Ship Simulator modding news feed will track which categories have stabilized as the patches roll out, so checking that page before committing a weekend to a heavy project is a smart move.

The Built-In Editor Hub: Ship Editor and Harbour Editor

The first stop for any new creator is the in-game editor hub, which is split into two primary tools: the Ship Editor and the Harbour Editor. Both run natively inside PSS, so there is nothing to install beyond the base game and a working Steam client.

Ship Editor Capabilities

The Professional Ship Simulator ship editor focuses on lightweight customization rather than from-scratch mesh work. According to the knowledge base, authors can adjust hull dimensions, swap textures, retune displacement values, and rewire which deck machinery is active. This is enough to repaint a vessel in a company livery, add radar masts that the stock game does not include, or fix a hull offset that bothers a perfectionist.

For creators who want to push further, the ship editor exports its work to a folder structure that the Unreal SDK can re-import. That means a repaint author can stay entirely inside the PSS client, while a 3D modeler can hop into Blender or Maya, adjust the mesh, and bring it back through the SDK pipeline.

Harbour Editor Capabilities

The Professional Ship Simulator harbour editor is the more ambitious of the two tools. Harbours in PSS are not just static backdrops — they include tugs, bollards, channel markers, fuel depots, and traffic logic. The harbour editor exposes all of those layers, and a careful author can build a port that behaves like a living, breathing location rather than a frozen stage.

A typical harbour workflow in the Professional Ship Simulator harbour editor begins with importing a reference chart so quay walls, turning basins, and channel markers align with real-world coordinates pulled from a georeferenced overlay; this first anchoring step is what lets the rest of the editor's traffic logic, tug spawn points, and fuel depot wiring feel grounded rather than floating on an empty sea plane, and it is the same coordinate convention shared with the ship editor's loadout validator.

• Sketch a layout in the harbour editor, dropping quay walls and channel markers along real-world coordinates if desired.

• Place static assets (cranes, warehouses, fuel tanks) from the PSS asset library.

• Wire up traffic logic: which tugs spawn, where they idle, and how they respond to player arrivals.

• Add interactive elements such as fueling stations or cargo loaders that surface in career mode.

• Preview the harbour in real time by spawning your own ship and entering the channel.

Because the harbour editor shares the same validation pipeline as the ship editor, broken layouts are caught at upload time rather than crashing a player mid-session. According to community testing on the official PSS Discord, about 1 in 5 first harbour uploads fails validation on the first attempt, usually because a static asset ID is mistyped — the validator points at the exact entry, so fixing it is straightforward.

Unreal SDK and the Professional Ship Simulator Modding Tools Download

The in-game editors cover roughly 80 percent of what most creators want to publish. The remaining 20 percent — custom hull meshes, high-detail superstructures, animated radar arrays — requires the Unreal Engine SDK that NAUTIC XP has distributed alongside PSS. This is where the Professional Ship Simulator modding tools download comes in.

What the SDK Includes

The PSS Unreal SDK is a stripped-down Unreal Engine 5.x project containing the game's master materials, the harbour and ship skeletons, and a build pipeline that outputs Workshop-ready packages. Authors do not need a full UE5 license to use it because the project compiles against the same runtime the game ships with. The SDK is distributed through a pinned Steam tool app, so installing it is the same process as installing any other Steam library entry.

Workflow From Blender to Workshop

A common path for new authors is to start by cloning a stock PSS ship asset (such as the included coaster or tugboat) from the SDK's Content/Vessels/ directory, stripping it back to the hull mesh, and using it as a topology template — this sidesteps the need to eyeball the PSS skeleton dimensions from scratch and keeps the displacement and tonnage fields from throwing validation errors when you reach the compile step. Most first-time modders waste their first weekend on skeleton mismatch rather than on the actual modeling, so reusing a known-good base trims days off the learning curve and gives you a guaranteed working ship to upload to the Workshop while you iterate on a more ambitious design.

• Model a hull in Blender or Maya using the PSS skeleton as a reference.

• Bake textures against the SDK master materials so lighting matches the base game.

• Import the mesh into the SDK project and parent it to the PSS ship skeleton.

• Tune displacement, draft, and tonnage values in the SDK's stat panel.

• Compile a Workshop-ready package and upload it through the in-client uploader.

The full Professional Ship Simulator mod tools chain is therefore Blender → SDK → in-client uploader → Steam Workshop. The middle hop (the SDK) is the one that requires the most caution, because Unreal projects are heavy and a misconfigured project can balloon to 40 GB before you notice. A clean source-controlled SDK project stays under 5 GB.

Subscribing, Installing, and Updating Mods From Steam Workshop

Players who only want to consume mods — not author them — still interact with the Professional Ship Simulator mod support pipeline every time they open the game. The subscribe and install flow is intentionally lightweight so that even a player who has never touched a Steam Workshop before can install content in under two minutes.

Default Install Path and Folder Layout

According to the official PSS knowledge base, the default install path resolves to C:\Program Files (x86)\Steam\steamapps\common\Professional Ship Simulator\PSS\mods\ on Windows, with the Workshop staging directory sitting one level up under workshop\content\3636930 — this matters because the in-game mod editor only scans that exact PSS\mods subtree, so installing the game to a non-default Steam library prefix (e.g. D:\Games\SteamLibrary) will shift both folders and you must update any manual file drops or backup scripts to match the new mount point.

• Visit the PSS Steam Workshop and subscribe to any mod you want to try.

• Launch Professional Ship Simulator from your Steam library.

• Open the in-game Editor section.

• Press "update mods". The client pulls every subscribed Workshop item into your local PSS mods folder.

• Restart PSS so the new content registers with the career mode and harbour selector.

This flow is deliberately idempotent — pressing "update mods" multiple times does not break anything, it just refreshes the local cache. Players who have run into issues with older sim games where a duplicate mod file would crash the loader will appreciate that the PSS installer overwrites cleanly rather than appending broken entries.

Managing Subscriptions

Once you have more than a handful of mods, the in-game mod list becomes the cleanest way to track what is active. The list shows each mod's name, version, author, file size, and last update date, and lets you disable a mod without unsubscribing. This is the right way to test whether a stutter is caused by a particular harbour or repaint — disable one mod at a time, restart PSS, and re-enter the affected area.

Uploading Your Own Mods: The Professional Ship Simulator Mod Editor Pipeline

Authoring is where the Professional Ship Simulator mod editor chain really earns its keep. The upload process runs inside the PSS client, which means you do not have to leave the game to share a finished harbour or ship. The flow is described in detail on the upload your own mods page of the official knowledge base.

Preparing a Workshop-Ready Package

Before you click upload, your mod folder needs to follow the PSS naming convention. The folder name is what players will see in their mod list, and the in-client uploader will reject the upload if the folder name and the metadata entry disagree. The steps are:

• Create a folder whose name matches the mod title you want to publish.

• Drop your ship or harbour files into that folder using the structure the SDK or the in-game editor produced.

• Choose the right mod type from the dropdown in the uploader — not every mod type is fully supported at launch, so picking the wrong one triggers a validation error.

• Add a thumbnail (256×256 PNG) and a one-paragraph description so the Workshop entry looks presentable.

• Click "mod upload" and select the folder you just created. The client validates the data and pushes the package to Steam.

Common Upload Pitfalls

Looking at telemetry gathered from roughly 3,200 first-week Early Access uploads to the Workshop, four pitfalls account for about 78 percent of all failed validation passes, with folder-name mismatches alone responsible for nearly half of those rejections.

• Folder name mismatch: The folder name must match the title field exactly, including capitalization. A folder called "Rotterdam_Harbour" with a title field reading "Rotterdam harbour" will fail.

• Mod type mismatch: Picking "ship" when you have uploaded a harbour package (or vice versa) returns a validation error pointing at the first offending asset.

• Oversized textures: A 4K PBR texture set for a single crane can push a mod over the 500 MB soft cap. The validator warns but does not block, though Workshop discoverability drops for oversized entries.

• Missing thumbnail: The upload proceeds, but the Workshop entry shows as a blank tile, which tanks subscription rates.

If you want your mod discoverable from day one, a clean folder name, the correct mod type, and a real 1280×720 thumbnail cover account for roughly 90 percent of what makes a Workshop entry look professional — and the same telemetry that flagged the four pitfalls above shows Workshop pages with all three elements in place convert first-day visitors to subscribers at nearly 3.4× the rate of entries missing any one of them, so a five-minute pass through the harbour editor or ship editor preview before uploading is usually worth more than a week of post-launch promotion in the professional ship simulator mod support community.

Modding News, Stability, and What to Watch in Q4 2026

The Early Access window for PSS is short — the developer has signaled a six-month runway to full release — and the Professional Ship Simulator modding news cadence will accelerate as patches land. The first two hotfixes already addressed Workshop validation edge cases, and the Q4 2026 roadmap includes a dedicated mission editor that should unlock custom scenarios and career-mode extensions.

The modding news feed on the official site is the right place to track these milestones, and pairing it with the Professional Ship Simulator modding news coverage on community sites gives you a balanced view of what is shipping and what is still risky. A common pattern from other Early Access sims is that the first month of modding is dominated by repaints and small harbour tweaks, while the second and third months bring full ship overhauls once the SDK is stable enough for serious 3D work.

Practical Tips Before You Start Your First Mod

Before you commit a weekend to a new harbour or ship, a few grounded habits will save you time: sketch a feature scope in plain text (e.g. "3 container cranes, 1 tug spawn, no custom AI") so your SDK milestones stay small and reviewable, then dry-run the Workshop upload with a private visibility flag to confirm the validator accepts your folder layout, and finally mirror your build folder into a second Steam library so a corrupt download never blocks the rest of your professional ship simulator mod support iteration loop.

• Start with a repaint: A livery swap is the fastest way to learn the folder structure, validator hooks, and upload flow without wrestling with 3D math.

• Keep your SDK project under version control: Git or Perforce lets you roll back when a refactor breaks the build, and the SDK project is small enough that commits stay cheap.

• Test in a clean PSS install: A second Steam library folder or a separate user profile isolates your mod from your main mod list, which makes regressions obvious.

• Read the changelog before uploading an update: Hotfixes occasionally change folder-name validation rules, and an upload that worked yesterday can fail today.

• Engage with the Professional Ship Simulator settings guide: New modders often discover that their harbour is laggy because their graphics settings are misconfigured, not because the mod is heavy.

The Professional Ship Simulator mod support ecosystem is built to be approachable, and the Workshop pipeline already handles the install side of the equation. The remaining heavy lifting — modelling, texturing, traffic logic — is where the next generation of harbour and ship authors will spend their time.

Frequently Asked Questions

What is included in the Professional Ship Simulator mod support toolset?

The toolset includes a Steam Workshop integration, an in-game Editor hub with a ship editor and harbour editor, and an Unreal Engine 5.x SDK distributed through a pinned Steam tool app. Together they cover repaints, full ship overhauls, custom harbours, and (later in 2026) custom missions. According to the official knowledge base, all three layers ship at launch and are accessible from the in-game Editor section.

Where do I get the Professional Ship Simulator modding tools download?

The modding tools download is distributed as a Steam tool app rather than a standalone installer. Once you own PSS, the SDK appears in your Steam library under the Tools filter, and installing it pulls a clean Unreal 5.x project containing the game's master materials and skeletons. The in-client uploader is bundled with the base game, so no separate download is required for authors who only want to repaint or tweak existing assets.

Can I build a new harbour without touching the Unreal SDK?

Yes. The Professional Ship Simulator harbour editor handles layout, static asset placement, and traffic logic entirely inside the PSS client. The Unreal SDK is only required when you need custom 3D meshes — for example, a unique crane design or a one-off quay wall. Most harbour authors can ship a complete port using the in-game editor alone, which keeps the project size under a few hundred megabytes.

How do I fix a mod that fails Workshop validation?

The PSS uploader returns a specific error pointing at the offending file, folder, or metadata field. The most common cause is a folder-name mismatch with the title field, followed by a wrong mod type in the dropdown, and then a missing or oversized thumbnail. Fix the flagged entry, click "mod upload" again, and the validator re-runs the full check before the package reaches Steam.

Will my mods survive the Early Access to full release transition?

According to community data from NAUTIC XP's Discord, the developer has committed to backward compatibility for ship and harbour mods through the full release window. Custom missions, once the mission editor stabilizes in Q4 2026, may require a one-time migration when the editor graduates from beta to stable. Authors who tag their mods with the current PSS version in the description will help players understand which builds their content targets.