How to host a Prominence II server
Create a Prominence II Hasturian Era server, match the Fabric client and server release, update with backups, and diagnose login, Create, version, and memory failures.
Use the Prominence II server hosting page. It opens with Hasturian Era, Fabric, and the starting RAM already selected.
| Modpack | Prominence™ II: Hasturian Era |
|---|---|
| Modpack source | CurseForge #466901 |
| Version | 4.0.5 |
| Minecraft / mod loader | 1.20.1 / Fabric |
| Starting RAM | 8 GB — Estimated by berrybyte |
| Details checked | September 16, 2026 |
Prominence II 4.0 introduced major campaign and content changes. Keep the complete server pack, client profile, and player progression on the same release.
Create the Prominence II server
Open the dedicated page
Go to Prominence II server hosting. The exact Hasturian Era project should already be selected.
Choose a plan and region
Start with the RAM recommendation shown above for a small group. Use the larger plan for a busier campaign.
Complete checkout
Keep Prominence II attached. berrybyte installs the matching Minecraft and Fabric versions.
Wait for first boot
Watch Console until the campaign world finishes loading before anyone joins.
Install the matching client profile
Install Hasturian Era
Use the official Prominence II: Hasturian Era project in CurseForge or Modrinth.
Match the complete release
Select the exact release shown on the server. Do not combine files from 3.9.x and 4.0.x.
Launch once
Let Fabric finish loading and reach the main menu before opening Multiplayer.
Join the campaign
Copy Overview → Server address and add it from the matching Prominence II profile. Include the port. If the server appears online but rejects one player, compare that player's full profile and release first.
Update Prominence II safely
Back up progression
Create a full backup before changing campaign, talent, quest, or world data.
Stop the server
Wait for the final save to complete.
Install the complete release
Use Overview → Modpack → Change rather than manually updating Fabric mods one by one.
Update all clients
Move every player to the same release, start the server, and watch Console before joining.
Fix common Prominence II server problems
A player disconnects during login. Match the complete profile first. Public pack issues have recorded Prominent Talents errors during player login; keep the crash report before restoring or updating.
Create machinery causes a ticking exception. Pack issue reports have documented Create fluid and recipe interactions. Restore the backup before removing blocks or mods, then update as a complete release.
Client-only rendering files are on the server. Restore the matching server package. Do not upload an entire client instance over a dedicated server.
The campaign runs out of memory. Move toward the extra RAM option when several players explore, fight bosses, or load separate areas at once.
Still stuck? Open a support ticket with
latest.log, the crash report, and the exact Prominence II release.
Next steps
Frequently asked questions
How much RAM does a Prominence II server need?
Use the starting and extra RAM options in the server details below. They are berrybyte estimates for this pack.
Which Prominence II edition is this?
Prominence II Hasturian Era. Check the server details below for the current version, Minecraft version, and Fabric setup.
Do players need the same Prominence II version?
Yes. Every player should use the same complete release as the server. Do not mix 3.9.x and 4.0.x profiles.
Why does Prominence II crash when a player joins?
Match the complete pack first. The pack's public issue tracker has recorded talent-tree login errors after mismatched or modified installs.
Should I back up before updating Prominence II?
Yes. Back up the world and player progression before changing the pack, then update the server and all clients together.