CurseForge · Minecraft mod
Conquered Outposts
Claim pillager outposts with a banner to stop their spawns
Quick answer
Which Conquered Outposts release matches 26.2 Forge?
Conquered Outposts conqueredoutposts-forge-26.2-1.0.0.jar targets 26.2 with Forge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.
Where it goes
Is Conquered Outposts required on the client, server, or both?
The project page does not say whether this file belongs on the client, dedicated server, or both.
The source does not explicitly classify this release as client-only or server-only.
What else does Conquered Outposts conqueredoutposts-forge-26.2-1.0.0.jar need?
conqueredoutposts-forge-26.2-1.0.0.jar on 26.2 Forge. Every mod below is checked against that same setup.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add Conquered Outposts without breaking your instance.
Built for Conquered Outposts conqueredoutposts-forge-26.2-1.0.0.jar on 26.2 Forge. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use conqueredoutposts-forge-26.2-1.0.0.jar. It targets 26.2 with Forge; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
The project page does not say whether this file belongs on the client, dedicated server, or both.
- 04
Pick the file you checked
Use the “Get this file” button beside conqueredoutposts-forge-26.2-1.0.0.jar. It opens that exact file at the source.
About this project
What does Conquered Outposts add?
Conquered Outposts
Take a pillager outpost for yourself.
A pillager outpost keeps spawning pillagers forever, even after you have cleared it. Conquered Outposts lets you claim an outpost by planting your own banner in it. While your banner stands, the outpost stops spawning pillagers and the area behaves like the land around it. Take the banner down and the outpost goes back to normal.
Features
- Claim with a banner. Place any banner, standing or on a wall, in any colour or pattern, inside an outpost. The outpost is claimed at once; pillagers still around do not stop you.
- No more outpost pillagers. A claimed outpost no longer spawns pillagers. The normal mobs of the biome still spawn there, as anywhere else.
- Easy to undo. When the last claim banner of an outpost is gone, the outpost spawns pillagers again.
- Outpost farms are safe. Nothing changes for an outpost nobody has claimed, so pillager farms at unclaimed outposts keep working.
- Saved with the world. Claims survive server restarts.
- Messages. "Outpost claimed" and "Outpost lost" appear above the hotbar of the players inside the outpost. Can be turned off.
- Server-side only. Players join with a plain vanilla client.
How it works
- The claim area is the outpost's whole structure: the watchtower and everything generated with it (cages, tents, logs, targets).
- Ominous Banners never count, even renamed. Banners that come with the outpost, or set with commands such as
/setblock, never count either. A claim is always a player placing a banner. - You can place several claim banners. The outpost stays claimed while at least one remains.
- A claim banner is lost however it disappears: broken, blown up, dropped because its support was removed or pushed by a piston, or replaced with
/setblockor/fill. - Stays vanilla: pillager patrols, raids, mob spawners, the pillagers already living in the outpost and the biome's spawning rules.
Versions
| Minecraft | Loader | Requires | File |
|---|---|---|---|
| 26.3 | NeoForge 26.3.0.0-beta+ (stable 26.3.0.76+) | Java 25 | conqueredoutposts-neoforge-26.3-1.0.0.jar |
| 26.3 | Forge 66.0.0+ | Java 25 | conqueredoutposts-forge-26.3-1.0.0.jar |
| 26.3 | Fabric Loader 0.19.3+ | Fabric API 0.160.6+, Java 25 | conqueredoutposts-fabric-26.3-1.0.0.jar |
| 26.2 | NeoForge 26.2.0.0-beta+ (stable 26.2.0.57+) | Java 25 | conqueredoutposts-neoforge-26.2-1.0.0.jar |
| 26.2 | Forge 65.0.0+ | Java 25 | conqueredoutposts-forge-26.2-1.0.0.jar |
| 26.2 | Fabric Loader 0.18.4+ | Fabric API 0.152.2+, Java 25 | conqueredoutposts-fabric-26.2-1.0.0.jar |
| 26.1 - 26.1.2 | NeoForge 26.1.0.1-beta+ (stable 26.1.2.71+) | Java 25 | conqueredoutposts-neoforge-26.1-26.1.2-1.0.0.jar |
| 26.1 - 26.1.2 | Forge 62.0.0+ (62 = 26.1, 63 = 26.1.1, 64 = 26.1.2) | Java 25 | conqueredoutposts-forge-26.1-26.1.2-1.0.0.jar |
| 26.1 - 26.1.2 | Fabric Loader 0.18.4+ | Fabric API 0.144.1+, Java 25 | conqueredoutposts-fabric-26.1-26.1.2-1.0.0.jar |
| 1.21.11 | NeoForge 21.11.42+ | conqueredoutposts-neoforge-1.21.11-1.0.0.jar |
|
| 1.21.11 | Forge 61.0.1+ | conqueredoutposts-forge-1.21.11-1.0.0.jar |
|
| 1.21.11 | Fabric Loader 0.17.3+ | Fabric API 0.139.5+ | conqueredoutposts-fabric-1.21.11-1.0.0.jar |
| 1.21.1 | NeoForge 21.1.1+ | conqueredoutposts-neoforge-1.21.1-1.0.0.jar |
|
| 1.21.1 | Forge 52.0.0+ | conqueredoutposts-forge-1.21.1-1.0.0.jar |
|
| 1.21 - 1.21.1 | Fabric Loader 0.15.11+ | Fabric API 0.102.0+ | conqueredoutposts-fabric-1.21-1.21.1-1.0.0.jar |
| 1.20.1 | Forge 47.1.0+ (also NeoForge 1.20.1) | conqueredoutposts-forge-1.20.1-1.0.0.jar |
|
| 1.20 - 1.20.1 | Fabric Loader 0.14.21+ | Fabric API 0.83.0+ | conqueredoutposts-fabric-1.20-1.20.1-1.0.0.jar |
The Fabric jar bundles NightConfig (core and toml, LGPL-3.0) to read the TOML config. NeoForge and Forge already ship it.
Client and server
Install the mod on the server only. It adds no items, blocks, entities, commands, network messages or registries, so vanilla clients and modded clients without it can join. On Forge the mod is marked as server-only, so a Forge client without it still shows the server as compatible in the server list. On Fabric, Fabric API is only needed on the server.
Installing it on a client as well does no harm: claims and spawning run on the server, and the messages are plain text. In singleplayer, install it in your own game; the built-in server runs it.
Configuration
config/conqueredoutposts.toml is created with comments on the first server or world start:
structures = ["minecraft:pillager_outpost"]
showMessages = true
structureslists the structures that can be claimed. Add outposts from other mods or datapacks by their structure ID;[]turns claiming off. Existing claims are kept and work again when their structure is listed again.showMessagesshows "Outpost claimed" and "Outpost lost" above the hotbar.- Changes take effect after a server restart, or after closing and reopening a singleplayer world.
- Mistakes do not crash the server: invalid values use the default, unknown structure IDs are skipped, and each problem is logged as a warning.
FAQ
Do players need the mod? No. Only the server needs it.
Can I claim an outpost that was generated before I installed the mod? Yes. Any outpost can be claimed by placing a banner inside it.
Does it stop pillager patrols or raids? No. Patrols, raids and mob spawners stay vanilla. Only the outpost's own pillager spawning stops.
What happens if I remove the mod? The world opens normally and every outpost spawns pillagers again. Your banners stay as ordinary banners. If you install the mod again, claims whose banners are still in place work again.
Does it work with outposts from other mods or datapacks? Yes, if you add them to structures and they spawn their mobs through a structure spawn override like the vanilla outpost. Structures that use spawners or their own spawning code are not affected by a claim.
Does it work with other spawning mods? Mods that replace world spawning with their own code may bypass the claim.
Can I use it in my modpack? Yes, go ahead. The mod is licensed under MIT.
Links
- Source code: https://github.com/emberbocor/conqueredoutposts
- Bug reports and suggestions: https://github.com/emberbocor/conqueredoutposts/issues
When reporting a bug, please include your Minecraft version, loader, mod version and your log file.
Project description from CurseForge.
Pick your setup
Conquered Outposts by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
26.2
3 loader builds26.1.2
3 loader builds26.1.1
3 loader builds26.1
3 loader builds1.21.11
3 loader builds1.21.1
3 loader builds1.21
1 loader build1.20.1
3 loader builds1.20
1 loader buildCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
Conquered Outposts versions and loaders
conqueredoutposts-forge-26.2-1.0.0.jar
17 Nov 2026
Looking for an older file? The official CurseForge project page is in Resources.