Step-by-step guide

How to install a local mod in r2modman

Test a local ZIP, DLL, or development build while documenting dependencies, provenance, and updates the package index cannot track.

GuideFor: New r2modman users and players who want repeatable, recoverable mod setups.Updated September 13, 2026
01

Use local import for a defined reason

Local installation is appropriate for a development build, a private test package, or a fix that is not yet published. A stable everyday profile is easier to reproduce when most packages come with version and dependency metadata. Start by cloning the profile so the local binary is isolated.

02

Inspect the package before import

Confirm the target game, loader, archive structure, author or build source, and redistribution license. A DLL with an unfamiliar name is not enough information. Do not drop unknown binaries directly into the game directory or disable security tools to make the import succeed.

03

Record dependencies manually

Local files may not receive automatic dependency resolution, version display, or update notices. Write down the source commit, build date, loader requirement, dependency versions, and rollback file. Install prerequisites before the local package and verify each layer.

04

Verify with a minimal profile

Use Start modded and inspect the loader log for the package name and first exception. Confirm its documented in-game behavior. If it fails, reproduce with only the loader, required dependencies, and local mod before reporting an issue to its author.

05

Share responsibly

A profile code or .r2z may not include local content. If others need the package, provide clear installation notes and only redistribute files when the license permits it. For long-term collaboration, a properly packaged release with metadata is more reliable than sending loose DLLs.

Frequently asked questions

Clear answers before you change anything

Will a local ZIP install its dependencies?

Do not assume it will. Read the package instructions and satisfy its loader and library requirements explicitly.

Does profile export include the local file?

It may not. Test the export on a clean profile and document any separate file required.

How will I know when a local mod updates?

r2modman cannot reliably track an unpublished build. Record its source and check that source manually.

Research note: September 13, 2026 snapshot. Release assets and platform behavior can change; verify important details again before installation.

Recommended path: read this guide → download or create a minimal profile → record the result → expand to the full modpack.