Rust Procedural vs Custom Maps: Maintenance Trade-Offs
Compare Rust procedural and custom maps by generation inputs, file ownership, download upkeep and update checks before choosing your next world.
You will need
- A Rust PC group choosing a future world
- A procedural candidate or custom map source to evaluate
- One person able to own map updates and download details
Rust procedural maps are generated from recorded inputs, while custom maps add an authored file and its ongoing support obligations. Choose the world type whose setup, updates and recovery responsibilities your group can keep current, then name an owner for each one.
If your group also wants someone else to administer the Rust PC server, Game Hosting offers a game panel with map-related settings and three free backup slots. Those features help manage the server; your group still needs to check a custom map’s permission, exact compatibility and public download source.
Choose the map type your group can maintain#
Start with what the group wants to decide. A procedural world is shaped by values such as size and seed, with documented options for some generation details. A custom world begins as an authored .map file. Both can be a good fit; the work changes with the choice.
| Your priority | Procedural map | Custom map |
|---|---|---|
| Choose a broad layout | Compare generated candidates from recorded inputs | Choose an authored layout and review its source |
| Recreate the decision | Save size, seed, map type and Rust build | Preserve the exact file, author details and compatible build |
| Change details | Use documented generation options when they fit | Ask the author about edits, dependencies and support |
| Keep players connected | Review the generated world after relevant updates | Maintain a public map URL and review the artifact after updates |
Use this as a responsibility comparison, not a promise that one map type loads faster, runs better or stays compatible longer. A procedural input record makes the setup easier to identify. A custom artifact gives the group a specific authored layout to manage.
Record what creates each world#
Rust procedural generation uses map size, seed and map type. Facepunch documents +server.worldsize, +server.seed and +server.level in its server setup guidance. Its map data reference explains that the generated .map is stored as an artifact. Save the inputs with the Rust build and any first-generation customization your server uses.
Facepunch also documents optional procedural settings for details such as biome shares, roads and prefab inclusion in its procedural generation reference. That means “procedural” does not mean every layout detail is fixed or unavailable for configuration. Check the current generation workflow before relying on a setting; these options apply when the map is first generated.
A custom map follows a different source trail. It is a pregenerated .map artifact, and Facepunch’s custom map hosting guide documents +server.levelurl for loading it. The group should keep a copy of the exact file and record who created it, what Rust build it targets, and what permission or dependencies accompany it.
Neither a seed alone nor a map filename is a complete compatibility record. Future Rust updates can change generation or map expectations. We did not generate or validate a candidate for this guide, so treat the record as a way to make the decision reviewable, then inspect your chosen world after relevant changes.
Name who owns each moving part#
Before wipe planning starts, write one person’s name beside each responsibility. Shared ownership can work, but the group needs to know who acts when a map source, author or URL changes.
| Responsibility | Procedural world | Custom world |
|---|---|---|
| Source record | Keep size, seed, map type, build and any generation options together | Keep the original .map file, author, terms, build and dependencies together |
| Map changes | Decide who approves new inputs and checks the generated result | Decide who contacts the author and obtains an updated artifact |
| Rust update review | Review whether the recorded generation still meets the group’s needs | Review author notes, artifact compatibility and required dependencies |
| Player download | Usually no custom map URL to maintain | Name the person who checks the public URL and download instructions |
| Recovery decision | Keep the world and configuration recovery plan current | Keep map and save recovery responsibilities distinct |
For server settings that need to survive restarts, use the Rust configuration worksheet to record which configuration source controls each value. A screenshot of a setting or a stored seed does not prove that the desired world can be recovered from the files your group actually keeps.
Plan custom map downloads and revisions#
A custom map adds a download responsibility. Facepunch says players fetch it from a public URL, and that address needs to remain reachable. A link that opens a login page, requires a click-through or points at a local file does not meet that requirement. Its custom map guide describes the direct-download behavior to check.
Before you invite the group, assign someone to check the selected artifact in a clean browser session and follow the current Facepunch instructions for the PC client. Record the URL owner, renewal or expiry conditions, map version and date of the check. This article does not validate a specific map or download service. For a provider-focused review of file access, see the custom map hosting checklist.
Custom map revisions need their own review. Facepunch warns that Rust may use a cached map and that a revised map should receive a new unique name. A server also does not necessarily download a replacement on every start. Record the new artifact and its URL explicitly; have the responsible person check the changed map with the intended Rust build before players depend on it.
Map and save data have different jobs. Facepunch’s server file guide describes .map as terrain and monuments, while .sav stores entities and player/world data. A file with the right name does not prove the pair can be restored. Keep exact file changes and rollback steps within a tested migration procedure.
Keep that distinction in your checklist when you compare responsibilities. A procedural decision still has a generated map artifact and a save to protect. A custom map gives the group another durable source to keep and a public delivery path to monitor. Neither source by itself documents the current running identity, the save that players expect, or whether an earlier version can be restored cleanly. Write the current map and save names into the recovery plan, then leave detailed replacement and rollback commands to a tested migration procedure.
A custom-map author is another contact, not a substitute for an owner in your group. Before selecting a file, ask how the author announces Rust-build changes, where fixes are published, whether redistribution is allowed, and whether the map depends on plugins or extra files. Save the answers beside the artifact and identify what the group will do if the author stops maintaining it. A procedural map also needs a decision owner: someone should retain the selected inputs, generation options and review notes rather than relying on memory after the next wipe.
Review either choice after a Rust update#
Use the same questions after a major game change, but gather different evidence for each world type:
- Identify the current world. Record the Rust build and active server identity. For a procedural map, compare the running world with the saved size, seed and map type. For a custom map, confirm the exact artifact and source URL.
- Review the changes that matter. Check current Facepunch notes for generation, terrain or map-loading changes. For a custom map, also check the author’s compatibility notes and support status.
- Inspect the candidate you intend to keep. Use your group’s actual PC server and client workflow. Confirm that the world fits your needs and that any required map download works from a clean session. This is a check for your artifact, not a universal compatibility claim.
- Keep a recovery decision. Record the person who can restore the prior map and save combination, and the point at which the group will postpone the change. Avoid replacing world files until the recovery path is understood.
If no one can confirm a custom map’s author terms, build or public URL, choose another candidate or delay the change. For procedural maps, retain the inputs and repeat the review after updates; do not assume a familiar seed guarantees a familiar world indefinitely. A practical schedule ties the review to an event instead of an arbitrary promise that every map behaves the same:
| Review trigger | Procedural record | Custom-map record |
|---|---|---|
| Before a new wipe | Confirm the intended size, seed, type and build | Confirm the artifact version, author terms, dependencies and URL |
| After a Rust update | Review relevant generation notes and inspect the candidate | Review the author’s compatibility notes and inspect the selected artifact |
| When a map file changes | Keep the new generated world decision with its inputs | Use a distinct revision name and repeat the reader-side download check |
| When the owner changes | Hand over inputs and the last acceptance notes | Hand over the artifact, terms, author contact and URL account |
This record prevents a common handoff failure: one person remembers why the group chose a world, but no one else can find its source or decide whether a replacement is safe. Put the record where the next administrator can reach it before wipe day.
Choose the option with a named owner#
Use this short worksheet with your group before setting a wipe date:
| Decision | Record |
|---|---|
| World type | Procedural or custom, and why it fits the group |
| Source | Size/seed/type/build, or artifact/author/terms/build |
| Ongoing work | Generation review, author contact, dependencies, URL and update checks |
| Responsible person | Name one owner and a backup contact |
| Acceptance point | What the owner will inspect before players join |
| Fallback | Which known-good world or schedule change the group can use |
Choose procedural when the group is comfortable owning generation inputs and reviewing the result after relevant updates. Choose custom when the authored layout matters enough that someone will preserve the file, author information, dependencies and public download. The reliable choice is the one your group can identify, review and recover with the people and access it actually has.
Quick answers
Does a procedural seed recreate the same map forever?
A seed is one of the generation inputs, alongside size and map type. Keep those values and the Rust build with your decision, then review the world after relevant updates; the inputs alone do not promise identical results across future builds.
Does the Rust server host also provide a custom map download?
Not necessarily. Facepunch says a custom map is downloaded from a public URL, so confirm who owns that URL, how long it remains available and how players can fetch the file.
Should a custom map replace the save file?
No. Facepunch distinguishes the map artifact from saved entities and player data. Treat a change as a world and recovery decision, and follow a tested migration plan before replacing files.