Install a modpack: not available yet

No browser and no installer

There is no CurseForge or Modrinth browser and no one-click installer. Those are later installer targets, not APIs in the current catalog. There is no modpack upload endpoint either: the files RPC is the only write path.

Minecraft Java is the pack with declared modpack support. When the pack type is Fabric or Forge, the panel points at the mods directory, and Bedrock is a separate pack with server properties only. Declaring that directory is not the same as installing a pack into it.

Why a modpack does not go through Files

Files takes one file per upload and caps each file at 256 KB (262,144 bytes). A modpack is hundreds of jars and configs, and most jars are several megabytes, so the upload is refused long before the pack is complete.

There is no folder upload, no multi-select, no SFTP or rsync endpoint, and no object-storage bucket on the instance. World-scale transfer is not available yet, and a modpack is world-scale: it is not a handful of small config edits.

What you can do today

Edit a single small config, replace a whitelist, or upload one file the pack names, as long as each file is 256 KB or less. That is a real write path, and it is the whole of it.

A full modpack needs a transfer path that does not exist yet. Support cannot stage files for you either: there is no admin upload, no importer, and no node-side fetch. Do not plan a modded launch on Foxcore until one of those ships.

1. Read the modpack’s server download page and note its loader and Minecraft version.
2. Check the size of every file you would need to upload. Anything above 256 KB cannot go through Files.
3. Upload only the small files you genuinely need, one at a time.
4. Start the instance and open Console. Read the first error, not the last line of a crash loop.
5. If the pack needs more than that, keep it on a host that can accept the files.

Reading a failed start

Read Console for the first exception. A missing dependency, a wrong loader, a mismatched Minecraft version, or a config that points at an absent world are all visible there. An empty console is waiting for frames, not a silent success.

If the process starts and then dies under load, check the memory cap before adding more mods. A large pack on a 4 GB size will struggle regardless of the node.