Skip to content
Hosihikari Framework

Installing the self-hosted carrier

The self-hosted carrier has no parent loader: it preloads the framework into a stock Bedrock Dedicated Server. It is the only carrier that runs without LeviLamina or Endstone.

Requirements

Section titled “Requirements”
  • Linux x64.
  • Bedrock Dedicated Server 1.21.3. The launcher targets that version.
  • The .NET 10 runtime on the machine.
  • lip.

Install

Section titled “Install”

Run this in the server root:

Terminal window
lip install github.com/HosihikariFramework/HostingShim

The suffix-less package is the self-hosted carrier. The package depends on the plugin manager, so lip installs that too, under plugins/hosihikari/.

The install script marks the launcher executable. If lip was run with --ignore-scripts, set it yourself:

Terminal window
chmod +x hosihikari-server

Run

Section titled “Run”

Start the server through the launcher, not through bedrock_server directly:

Terminal window
./hosihikari-server

The launcher changes into the server directory and preloads the carrier, which starts the CLR and the plugin manager before the server's main.

Plugin packages here

Section titled “Plugin packages here”

Every plugin under plugins/ loads and enables before the server starts. There is no runtime enable or disable yet: to stop using a plugin today, move its package out of plugins/ and restart. Plugin management commands — enable, disable, load, unload — are planned on top of the projection's command MCAPI and the plugin manager API; this page will be updated when they ship.

Precompiled assembly packages run here out of the box. Source plugins work too: install the matching loader package (C# or F#) alongside the carrier, exactly as on the parented carriers.

Verify

Section titled “Verify”

The launcher's output and the server log should show the CLR starting, the carrier taking over, and the plugin manager reporting what it found under plugins/. If the launcher exits immediately, its first line says why — usually a missing runtime or a missing bedrock_server. See Recovery.

Where things live

Section titled “Where things live”
Path What
hosihikari-server The launcher; run this instead of bedrock_server.
plugins/hosihikari/ The carrier and the plugin manager.
plugins/<name>/ Plugin packages.
config/hosihikari/<name>.conf Server-side configuration overrides.
data/hosihikari/<name>/ Data the framework hands to each plugin.

Uninstall

Section titled “Uninstall”
Terminal window
lip uninstall github.com/HosihikariFramework/HostingShim