Put any Rust monument exactly where you want it
Force a monument onto a map that would never roll it. Pin it to a spot, set its rotation, and let the generator build the world around it — roads, rails, rivers and every other monument laid out by Rust’s own worldgen, not pasted on afterward.
Why this is different from dropping a prefab in an editor
The usual way to get a monument onto a map is to open the finished map in an editor and paste it in. That works, and then you own every consequence: the ring road still runs where the old layout put it, the rail line ends in the side of your new monument, a river cuts through it, whatever it landed on is still there, and the terrain underneath is whatever shape the seed left. Fixing that by hand is the real work, and it is why most “custom” maps have a monument sitting in a visibly wrong place.
Unlike RustEdit, placement here is quick and easy: no learning curve and nothing to install. Pick the monument, drop a pin, generate.
Forced placement here happens during generation. The world is generated again with your monument as part of the input, so the generator routes the roads, rails, rivers and powerlines around it and positions every other monument with it already on the map. What comes out is a normal vanilla-shaped world that happens to contain the monument you asked for.
What you can place
Any of these 27 monuments, including ones a given world size would normally be too small to roll:
Launch SiteAirfieldMilitary TunnelsPower PlantTrain YardWater Treatment PlantGiant Excavator PitJunkyardMissile SiloOutpostBandit CampApartment ComplexRadtownArctic Research BaseDesert Military BaseSatellite DishSphere Tank (Dome)Sulfur QuarryStone QuarryHQM QuarryRanchLarge BarnSmall HarborLarge HarborFerry TerminalFishing VillageLighthouse
Pin, rotate, terraform
| Force | Guarantee a monument appears at all, and let the generator choose where it goes. |
|---|---|
| Pin | Choose the spot yourself. The generator smooths a natural pad at the pin and builds the monument on it, shoring around rivers and lakes instead of paving them flat. Harbors, fishing villages and lighthouses are different: they need the sea, so they get no pad and go to the nearest spot on the shoreline where they fit. Up to 12 pinned monuments on one map, one pin each. |
| Rotate | Set the yaw, snapped to 15°. |
You are told the truth about where it landed
Terrain does not always cooperate, and a tool that quietly moves your monument and says nothing is worse than one that fails loudly. A pin that cannot work turns red in the editor before you generate, with the reason, and one that may not work turns amber. After generation every pin is measured against the finished map:
| On the pin | The monument landed within 50 m of your pin (half the footprint for the very largest monuments). |
|---|---|
| Off the pin | It is on the map, but somewhere else — reported with the distance in metres and the reason (a river or another monument in the way, a coastal monument pinned inland, a pin too near the edge) so you can move the pin and regenerate. |
| Not on the map | It could not be seated at all. You are told, rather than being left to find out on wipe day. |
| Unverified | The finished map could not be checked. You are told that, rather than given a guess. |
A live preview runs while the map generates, so you watch the terrain, biomes, monuments, roads and rivers appear and see each pin resolve as it happens.
What it is good for
- Small maps with big monuments. Put Launch Site or the Excavator on a 3000m world that would never roll one, so a small server still has an end-game destination.
- Designing the fight. Place the monuments you want contested where you want them contested, instead of re-rolling seeds until the layout is roughly acceptable.
- Event and arena maps. Set a known layout deliberately rather than describing it and hoping the seed agrees.
- Keeping a map across a wipe. Re-generate the same intent on a fresh seed instead of hand-porting an edited map.
How to use it
- Generate a map at the seed and world size you want.
- Open monument placement from the map and drop a pin for each monument you want forced.
- Set a rotation if the monument needs to face a particular way, and move any pin the editor shows in red.
- Generate. The world is built again with your placements, and each pin comes back reported as on the pin, or how far off and why.
- Copy the level URL into
server.levelurland restart. It is an ordinary Rust map file — no plugins, no client mods.
Monument placement is a Premium feature. Generating plain maps at any seed and size stays free.
Frequently asked questions
- Can you put a specific monument on a Rust map?
- Yes. Rust Map Maker can force any of 27 major monuments onto a generated map, including monuments the world size would normally be too small to roll. You can also pin a monument to a chosen spot on the map and set its rotation.
- Is forced monument placement the same as editing the map afterwards?
- No. It is part of the generation, not a step after it. The world is generated again with your monument included, so the real generator lays the roads, rails, rivers, powerlines and every other monument out around it. Dropping a monument into a finished map in an editor leaves the roads and rails cut for the old layout and the terrain unshaped beneath it.
- Does the terrain have to be flat where I pin a monument?
- No. Every pin smooths a natural pad at the spot before the monument is placed, so it seats on a slope or a ridge that would otherwise reject it. The pad shores around rivers and lakes rather than paving over them, and it is what lets you set a rotation. Harbors, fishing villages and lighthouses are the exception: they belong on the coast, so they get no pad and are built at the nearest spot on the shoreline where they fit. Pin them right on the water's edge.
- How do I know the monument actually landed where I asked?
- Pins that cannot work turn red in the editor before you generate, with the reason: in the ocean, too close to the edge, a harbor or lighthouse pinned away from the shore; pins that may not work turn amber. After generation every pin is measured on the finished map. One that landed on the pin is reported as such; one that did not is reported with how far off it landed in metres and why, so you are never told a placement worked when it did not.
- Do forced monuments break the map for a live server?
- No. The output is an ordinary Rust world file with a normal vanilla shape, so it loads with server.levelurl like any other map and needs no plugins or client-side mods.