Chosen’s Create: Integrated Modpack Server Setup Guide (Minecraft 1.21.1, NeoForge)

To run a Chosen’s Create: Integrated server, use Minecraft 1.21.1 with NeoForge, download the matching Chosen’s Create Integrated 1.4.3 Server Files.zip release, extract it into a clean directory, complete the first launch and EULA step, configure server.properties, and then give every player the same pack version, game version, and loader. You can host it yourself or use CurseForge’s managed hosting flow if you do not want to maintain the server process and network connection.

Running a modpack with friends? Godlike.Host offers modded Minecraft server hosting with one-click modpacks (CurseForge, FTB, Technic) and free DDoS protection.

What Chosen’s Create: Integrated is

Chosen’s Create: Integrated is a ChosenArchitect modpack built around Create automation. Its progression combines Create with Ars Nouveau, Just Dire Things, Refined Storage 2, and Replication rather than treating those systems as unrelated add-ons. The project listing describes it as a reworked Create journey with those mods integrated into one progression.

#	Preview	Product	Price
1		Minecraft - Bedrock Edition PS4	$42.98	Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

The server must match the pack’s supported platform. For the release covered here, that means Minecraft 1.21.1 and NeoForge. A regular vanilla server, a Forge server, or a different Minecraft version is not an interchangeable substitute.

Supported release and files

The official files listing identifies Chosen’s Create Integrated 1.4.3 Server Files.zip as the current server-pack artifact for Minecraft 1.21.1 and NeoForge. The listing dates that release to March 29, 2026. Version listings and availability can change, so check the official files page immediately before downloading and make sure the server archive matches the client release you intend to use.

#1 Best Overall

Minecraft - Bedrock Edition PS4

• Play and share with friends on console, mobile and Windows 10
• discover community creations in the new in-game store
• access new mini games and game modes through servers

$42.98

Buy on Amazon

Do not mix the 1.4.3 server archive with an older or newer client profile. Even when the Minecraft version remains 1.21.1, a changed modpack release can alter mods, configuration, recipes, or world behavior.

Decide how you will host it

Self-hosting

Self-hosting puts the files and operational decisions on your machine. You control the world directory, backups, configuration, firewall rules, and when the server starts or stops. The trade-off is that you must keep the Java server process running, make the machine reachable to players, and handle updates and recovery yourself.

• Choose this route when you are comfortable managing a server directory and network access.
• Plan for a machine that can remain available for the sessions your group expects.
• Keep a separate backup location; a second copy on the same disk does not protect against disk failure.

Managed hosting

CurseForge documents a managed flow in which you choose the modpack, select a plan and region, enter the server details, and pay through its hosting process. The documented service is powered by Shockbyte and billed through Tebex. This option moves deployment and much of the connectivity work to the provider, but it adds a recurring hosting cost and leaves plan limits, regions, and availability subject to the provider’s current offering.

Check the live plan page for the region, supported Minecraft and NeoForge versions, storage, player limits, cancellation terms, and current price before purchasing. Those details are not fixed by the modpack itself.

Prepare the client profile first

Install the CurseForge app and create or install a Chosen’s Create: Integrated profile. CurseForge profiles bundle the modloader, configuration files, and mods, which is why a profile is safer than assembling individual files by hand.

1. Open CurseForge and select the Minecraft section.
2. Create a new profile or install the Chosen’s Create: Integrated profile from the pack listing.
3. Confirm that the profile reports Minecraft 1.21.1 and NeoForge before launching it.
4. Launch the profile once on the client. This confirms that the local installation is complete before you troubleshoot a remote server.

Every player should use the same release shown in the server archive. Record the exact pack version, Minecraft version, and NeoForge version in your group’s setup message. CurseForge notes that game-version and modloader compatibility determine whether mods and modpacks work together; a client that differs on any of those three points may fail to connect or may load a different set of content.

Download the matching server archive

1. Open the pack’s official files listing.
2. Locate Chosen’s Create Integrated 1.4.3 Server Files.zip.
3. Verify that the file is identified for Minecraft 1.21.1 and NeoForge.
4. Save the ZIP somewhere you can verify before extraction. Do not rename it in a way that hides its version.

The server ZIP is separate from the ordinary client profile. Installing the client profile alone does not create a complete dedicated server directory. Conversely, downloading a server archive for another release can produce confusing missing-mod or registry errors even if the machine itself is configured correctly.

Set up a self-hosted server

1. Create a clean server directory

Make a new directory dedicated to this server. Extract the contents of the downloaded ZIP directly into that directory rather than nesting the archive inside several temporary folders. A clean directory makes it easier to identify the world, configuration, logs, and supplied launcher files, and it reduces the chance that an old pack release will be mixed into the new one.

Do not delete or replace files just because their names are unfamiliar. The archive may include a launcher, libraries, configuration folders, mods, and other support files. Keep the original ZIP until the server has started successfully so that you can compare or re-extract it if necessary.

2. Run the supplied launcher

Start the launcher included in the extracted release. The exact script filename and archive layout are release-specific, so use the launcher that is actually present rather than assuming a particular operating-system filename or command. If your operating system warns about an executable script, verify that it came from the archive you downloaded and allow it to run only after confirming the file location.

The first run normally creates or completes server files and may stop for the Minecraft EULA. Read the EULA prompt and accept it only if you agree to its terms. The server will not be available to players until that requirement is satisfied.

3. Stop after the first successful initialization

Once the initial launch has created its files, stop the server cleanly. Do not edit configuration while the process is still running; a running process can overwrite your changes during shutdown or leave files in an inconsistent state.

If the first run fails, keep the log output. The failure may identify a wrong Java installation, a damaged extraction, a missing dependency, or a mismatch between the launcher and the downloaded release. Re-extracting into a new clean directory is a useful recovery step before changing several settings at once.

4. Edit server.properties

Open server.properties with the server stopped. Set the server name and access settings you want for your group. Review the address and port settings, player-access controls, difficulty, and other options exposed by the file. Use the labels supplied in the generated file rather than copying a configuration from a different Minecraft version.

• Choose a recognizable server name so players can distinguish it from other profiles.
• Set access controls deliberately. A private group should not leave an unrestricted server exposed to the public internet.
• Record any port value you configure; players outside your local network will need the reachable address and port.
• Change one category of settings at a time, then restart and test, so a problem can be traced to a specific edit.

Do not copy client-only settings into this file. The server properties file controls the dedicated server; visual settings and other client preferences remain in each player’s local profile.

5. Start the server again

Run the same supplied launcher after saving server.properties. Watch the console until initialization completes and the server reports that it is ready for connections. The first startup can take longer than later starts while files and world data are created.

Connect locally first, if possible. Confirm that the world loads, the expected Create progression is present, and no mod-loading error appears. Only after that should you give remote players the address and open the server to the wider network.

Make the server reachable to other players

A self-hosted server has two separate requirements: the process must be running, and players must be able to reach the machine over the network. A successful local connection proves only the first requirement.

• On the host machine, allow the Java server process through the operating system firewall when prompted.
• If players are outside your home network, configure the router’s port-forwarding rule for the port shown in server.properties, directing it to the host machine’s local address.
• Give players the correct reachable address and port, not an address that works only inside your home network.
• Test from a different network, such as a phone hotspot, rather than relying only on a second device connected to the same router.

Do not publish the address publicly unless you intend to operate a public server. Restrict access in the server settings and at the network boundary, and remove the forwarding rule if you retire the server.

Keep every client compatible

Compatibility is a three-part match: the pack release, Minecraft version, and NeoForge loader. For this guide, the target is Chosen’s Create: Integrated 1.4.3 on Minecraft 1.21.1 with NeoForge.

Ask players to close the game and update the profile before joining after a server upgrade. Leaving an old instance open can make a correct installation appear broken because the player is still running the previous profile.

Plan resources without inventing a fixed requirement

The official release information identifies the supported version and hosting workflow but does not publish a tested RAM or CPU requirement for a particular player count. There is therefore no responsible pack-specific memory number to copy into a hosting order.

Instead, estimate the workload you actually intend to run:

• Number of simultaneous players and whether they explore separate areas.
• How heavily the group uses Create machinery, automation, storage networks, and other continuously active systems.
• World-generation activity, especially when several players travel in different directions.
• Whether the host machine is doing other work at the same time.

Start with a plan that allows monitoring and expansion, then observe memory use, CPU load, tick delays, and shutdown behavior during a real play session. Increase resources when measured workload requires it rather than treating an unverified number as a guarantee. A provider’s advertised plan size is not the same as a benchmark for this pack.

Operate, back up, and update the world

Use clean shutdowns

Stop the server through its console or supplied control rather than terminating the process abruptly. A clean shutdown gives the server time to write world and player data. If the host crashes, make a backup of the surviving directory before attempting repairs.

Back up more than the world folder

Preserve the world data together with the configuration and pack files that define how it loads. Keep dated backups away from the live directory and periodically verify that one can be copied to a test location. A backup that has never been checked may be incomplete or unusable.

Upgrade deliberately

Before changing releases, stop the server, make a full backup, and record the old pack version. Download the new server artifact and compare its stated Minecraft and NeoForge versions with the clients you plan to use. Test the upgraded copy separately when possible; do not overwrite the only working server directory until the new release has loaded the world successfully.

Use managed hosting instead

CurseForge’s documented managed route is designed for administrators who prefer a provider to handle deployment and connectivity. The general flow is:

1. Select Chosen’s Create: Integrated in the provider’s modpack selector.
2. Choose a hosting plan and region.
3. Enter the server name and other requested details.
4. Confirm the selected Minecraft and NeoForge-compatible release.
5. Pay through the displayed Tebex checkout and wait for the provider to provision the instance.
6. Use the provider’s control panel to start the server, share its connection details, and manage backups or restarts offered by the plan.

Before payment, verify that the selected service supports the exact 1.4.3 release and that its region is suitable for your players. Managed hosting removes much of the firewall and process maintenance, but you still need to keep clients on the matching pack release and maintain your own independent backup if the world matters.

Troubleshooting common setup failures

Final pre-launch checklist

• Minecraft is set to 1.21.1 on the server and every client.
• NeoForge is the loader on the server and every client.
• The server archive is the matching Chosen’s Create Integrated 1.4.3 Server Files.zip release.
• The archive was extracted into a clean, dedicated directory.
• The supplied launcher completed its first run and the EULA was accepted.
• server.properties contains the intended name and access settings.
• The host firewall and, where necessary, router forwarding permit the chosen port.
• A clean backup exists before players begin building.
• Resource usage will be measured with the intended player count instead of assumed from an unverified RAM figure.

Frequently Asked Questions

Can I use the normal CurseForge client profile as the dedicated server?

No. The client profile supplies the player-side loader, mods, and configuration. Download the separate Chosen’s Create Integrated 1.4.3 Server Files.zip archive for the dedicated server.

Are the launcher script names the same on every operating system?

Not necessarily. Use the launcher included in the extracted release and verify its actual filename and contents rather than relying on a name from another pack or tutorial.

Should I upgrade the server as soon as a newer pack file appears?

Only after making a full backup and confirming that the new artifact supports your intended Minecraft and NeoForge versions. Test the upgrade separately before replacing a working installation.

Does managed hosting remove the need to match client versions?

No. Hosting can handle deployment and connectivity, but each player still needs the server’s exact pack release, Minecraft version, and NeoForge loader.

Quick Recap

Bestseller No. 1

Minecraft - Bedrock Edition PS4

Play and share with friends on console, mobile and Windows 10; discover community creations in the new in-game store

$42.98

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.