About Restrictions on Artificial Tiles
From Factorio Mod PortalBETA A realism mod that adds some logical restrictions to "artificial" tiles (stone paths, concrete, etc) on what they can be placed under/on (trees, resources, cliffs, worms, etc). Configurable. Includes 100% removal of decoratives functionality ("Clean Concrete").
Main Features / Description =============
This is a mod for adding a level of realism to placement of "artificial" tiles, which in this mod are tiles like stone path, concrete, refined concrete, and the hazard variants. It will also include various other mod added tiles, such as ones that have any of the words "road", "asphalt", "gravel", or "floor" in their names. Landfill is explicitly excluded.
These "artificial" tiles will not be placeable on/under trees (except dead), cliffs, biter nests, worms, miners & pumpjacks, resources, or rocks. Trees, biter nests, and worms have an additional (small, like less than a tile) radius around them to prevent placing of the tiles too close. The reason for this is because of the tile transitions. The tiles this mod is classifying as artificial actually overlap some with their neighboring tiles, so without this extra radius, they would, visually, look no different than if this mod didn't even affect them. Canonically, I'm also looking at it as the trees have roots, the nests have those tendril looking things growing out the sides, and the worms have these holes that are a bit bigger than their bodies.
These same entities from above likewise cannot be placed on/under any tiles classified as "artificial" with the following exceptions:
- In an effort to prevent using artificial tiles as a hard stop/defense against biter spread, but still give it an element of that realism, biter nests and worms can spawn on artificial tiles, but have a chance at failure. The failure chance is based on the entity (small worms have the worst chance; behemoths have the best; nests are in the middle) and the average of the walking speed modifier on all tiles within their area of influence (the small radius mentioned above). The idea here being that the biters need to "break through" the artificial tiles to the ground beneath to create the nests/worms, and the nests/worms break apart any other tiles in their way as they grow/emerge. I use the walking speed modifier on the tiles because it's the best stat I have access to on the tiles (that I can think of) to determine "hardness" without creating a hard-coded table that would require updating for every mod that creates a new tile that isn't already covered.
- The other exception here are rocks: you can place rocks (where enabled by other mods like Dectorio or in /editor) as decoratives on the tiles.
Mod Interaction & Use on Existing Saves ============= (Mod support is in another section further down.)
In otherwise vanilla gameplay on brand new maps, this mod should have no issues.
Interactions with other mods, however, has the potential of not going as planned (but not game/save breaking). Mods have the ability to create and destroy entities at will (ignoring build restrictions), but the default behavior of the commands used is to not raise an event telling other mods that this has been done. As such, mods that, say, create trees as part of a tree growth/spreading mod, or create biter nests/worms in place of vanilla generation, have the potential of ignoring these new restrictions, placing these entities on the artificial tiles, and not alerting this mod to what they did.
Aside from other mods, introducing this mod into an existing save will not make now invalid combinations (like concrete on resources) automatically resolve themselves.
The "fix" for this lead me to include a "scan" functionality that will look for and correct these. On game save load where this mod is introduced into an existing save or any startup settings have changed that affect the list of entities or tiles affected, and periodically afterwards, it will run a scan of all game surfaces a few chunks at a time (but only 1 scan at a time) and correct anything it finds. This does mean that on existing saves it can take a bit to scan through and correct everything.
It defaults to destroying any artificial tiles rather than the entity in any cases of conflict (so, sorry, not a free nest/worm/cliff remover), with the exception of trees, which it will mine and spill their results onto the ground around where the tree was. Rocks are just ignored as there's no real way to differentiate between a rock that was there first and one that was placed after for decoration (or whatever).
It's also possible, either through when the entity is created in the data stage or the name the mod author gives their entity/tile, for this mod to just miss identify the entity/tile and either apply restrictions to it when it shouldn't, or doesn't when it should. (Modders, please check out the Modding Support section below for how to correct this from your end.)
Settings
Startup
The startup settings are mostly centered around individually controlling the entity types that will conflict with artificial tiles:
- Trees
- Cliffs
- Biter Nests
- Biter Worms
- Miners (& pumpjacks)
- Resources
- Rocks
- There's also an option to disable the "Clean Concrete" feature
Map
There are also a few Map settings that you can use to control the scan functionality (and remember: mod map settings can be changed at ___any___ time, not just at map creation):
- Enable/disable the periodic scan function (a scan will still occur on save game load if it's the first time this mod is being used with it or if any startup settings change that affects the list of entities or tiles it works with)
- Periodic scan frequency (defaults to 10 minutes; only 1 scan will run at a time, so if the timer runs out and the previous scan is ongoing, it will wait until it completes before starting another)
Highlights
From source dataFootprint
Rated a light load on a server.
License
Published under GPL-3.0.
Last update
Its author last shipped an update 4 yr ago.
Restrictions on Artificial Tiles on Nxeon
From our catalogue- One-click install
- Supported on Nxeon Factorio servers. We download it from Factorio Mod Portal, place it, and restart the server.
- Server side
- Required on the server
- Server load
- light
- Smallest plan we suggest
- Factorio — 2 GB (2 GB RAM). This follows our own load rating above, not a benchmark.
- Latest build
- 0.8.4, released 2023-04-05
Recent builds
| Build | Released | Game versions | Loaders |
|---|---|---|---|
| 0.8.4 | 2023-04-05 | 1.1 | n/a |
| 0.8.3 | 2023-03-18 | 1.1 | n/a |
| 0.8.2 | 2023-03-04 | 1.1 | n/a |
| 0.8.1 | 2023-03-04 | 1.1 | n/a |
| 0.8.0 | 2023-03-04 | 1.1 | n/a |
Run Restrictions on Artificial Tiles on a Factorio server
Pick a server or deploy a new one above; it is installed in one click.
What kind of mod it is
From the catalogWorld generation
Changes or adds to how new terrain, biomes and structures are created.
Runs on your server
From source side supportFactorio Mod Portal lists Restrictions on Artificial Tiles as required on the server. Check its Factorio Mod Portal page to see whether players need it too.
Compatibility
- Game
- Factorio
- Runs on
- Serverrequired on the server
Verified at the source
- ✓Factorio Mod PortalOfficial listing, checked 2026-10-16Open ↗
- ✓AuthorFuryoftheStars, as published on Factorio Mod Portal
- ✓LicenseGPL-3.0Free

