Rain World Modding

Workshop release

4 min read

Release a Workshop item from a clean copy of the package that contains the same files subscribers should receive. Keep the authoring directory separate so source files, compiler output, logs, and local test data do not enter the upload by accident.

Build 22785462 contains an in-game Workshop route. Indexed methods on global::RainWorldSteamManager include ValidateModApplicableForWorkshopUpload, ValidateWorkshopModForProblems, InitCreate, CreateWorkshopMod, InitUpload, UploadWorkshopMod, ShowLegalAgreement, and ShowWorkshopDetails. These symbols establish the route’s presence. Their bodies and user interface sequence were not inspected, and no item was created or uploaded during verification.

Prepare the release folder

Use this checklist before opening the game’s supported Workshop interface:

  1. Build against the recorded references and copy the package files into a separate release folder.
  2. Parse modinfo.json and confirm its identity, version, description, and requirements. See Mod manifests.
  3. Check that every DLL and asset belongs to the release and is permitted for redistribution. Do not include game or dependency assemblies by default.
  4. Inspect root, v1.11.8, and newest placement using Asset resolution. Save a file list or hashes for the exact package.
  5. Review the preview, Workshop text, release version, and dependency list before submission.

Test the copied folder before submission. A successful build does not show that the package is complete, that Remix finds its dependencies, or that an asset sits at the path its consumer resolves.

Create or update the item

Use Rain World’s supported Workshop interface for the release. Do not turn the indexed method names into direct SteamUGC calls from a mod.

Valve documents the platform lifecycle behind Workshop tools. Creation produces a PublishedFileId_t, which the authoring tool must retain for future updates. An update begins with ISteamUGC::StartItemUpdate, associates fields such as title, description, visibility, tags, content folder, and preview, then submits them through ISteamUGC::SubmitItemUpdate. SubmitItemUpdateResult_t reports the result. Valve also documents a legal agreement state that may require action before publication.

For an author using Rain World’s interface, that lifecycle translates into four checks:

  1. Choose create only for a new item. Use the retained published item ID for later updates.
  2. Review the selected package, preview, title, description, visibility, and tags before submitting.
  3. Read the returned result and any agreement prompt. Submission starting is not confirmation that it succeeded.
  4. Open the resulting Workshop details and confirm that the item identity, visible metadata, and release version match the intended update.

Valve states that a submitted update has no cancellation method after submission begins. Finish the folder and metadata review first.

Test the subscribed copy

Valve describes a Workshop item as a folder of files. The Steam client updates existing installed items before game launch when needed, while a new subscription may download in the background after launch. This does not promise when a particular client receives an update.

After Steam reports installation, test the installed Workshop copy independently of the authoring folder. Confirm that Rain World lists the expected mod ID, its declared dependencies are present, and the release behavior works with only supported prerequisites enabled. Record the Steam build, mod version, published item ID, package hashes, and the result message. Debugging and performance provides a reproducible report format.

Remove credentials, Steam session data, account names, personal paths, and save data from public logs and release notes. When third-party material is involved, check the owner’s current license and distribution terms for the files included. This page does not decide whether a particular use is permitted.

Verification boundary

The Rain World evidence is an index of installed symbols plus the subscribed-item path in global::ModManager.RefreshModsLists(RainWorld). Verification did not inspect Workshop validation rules, perform an upload, accept an agreement, or observe an installed update.

Sources

Graph View

Backlinks