{"url":"https://levimc.org/mods/github.com/HosihikariFramework/HostingShim/","id":"github.com/HosihikariFramework/HostingShim","name":"星光","description":"把 CLR 托管进 BDS，并把插件管理交给星光框架核心","owner":"HosihikariFramework","logo":"https://levimc.org/mods/icons/e36f5126960a1bd7-288.webp","repository":"https://github.com/HosihikariFramework/HostingShim","issues":"https://github.com/HosihikariFramework/HostingShim/issues","releases":"https://github.com/HosihikariFramework/HostingShim/releases","stars":0,"downloads":699,"updated":"2026-11-12T07:26:32Z","published":"2026-10-17T04:49:25Z","created":"2026-10-16T09:24:02Z","license":"LGPL-3.0","side":["server","client"],"platform":["linux-x64","win-x64"],"gameVersions":["1.26.51"],"tags":["platform:levilamina","platform:linux","platform:endstone","type:mod"],"latest":{"variant":"","version":"1.1.0","install":"lip install github.com/HosihikariFramework/HostingShim@1.1.0"},"readmes":[{"file":"README.md","lang":"en","text":"# HostingShim\n\n[English](README.md) | [简体中文](README.zh_hans.md)\n\nThe **native layer** of the Hosihikari framework, named **HostingShim** (the CLR hosting shim): it\nhosts the CLR inside the BDS process and then hands control to the core,\n[`PluginManager`](https://github.com/HosihikariFramework/PluginManager).\n\nIt does four things: locate hostfxr, initialise the runtime from the core's `runtimeconfig.json`,\nload the core assembly, and fetch the managed entry point. Everything else — discovery,\ndependencies, isolation, lifecycle — happens on the managed side. It does not project carrier\nAPIs; that side is **BindingShim**, produced outside this repository (ADR-0021).\n\n## What is in this repository\n\n| | |\n|---|---|\n| `common/` | The startup sequence — **carrier-independent**; every carrier target compiles this same code |\n| `carriers/` | The carrier targets: `levilamina/` (xmake), `endstone/` (CMake, Windows and Linux), and `selfhosted-linux/` (CMake) |\n| `verify/` | Programs and scaffolding that prove the native → managed hop |\n\nnethost headers and libraries are **fetched by version from NuGet**, never committed — both the\ncarriers and `verify/` download their own copy at build time.\n\n## Running it\n\n### Carrier: LeviLamina\n\n```\ncarriers\\levilamina\\build.bat\ncarriers\\levilamina\\deploy.bat <server root>\n```\n\n`build.bat` finds vcvars through `vswhere` and puts clang-cl on the path. On networks that need a\nproxy, set `https_proxy` first — the script leaves that to the caller. The artifact and its manifest\nare placed in `bin/hosihikari/` by the upstream `@levibuildscript/modpacker` rule; `deploy.bat` then\ncopies them, the managed core and `nethost.dll` into `plugins/hosihikari/`.\n\nA full live pass — start the server, drive `show`/`disable`/`enable`/`unload`/`load`, then check the\nlog:\n\n```\npowershell -File carriers\\levilamina\\smoke.ps1 -ServerRoot <server root>\n```\n\nIt first runs the managed assertion host (which also produces the plugin packages), so a sibling\n`PluginManager` checkout is required. It needs a server with LeviLamina already\ninstalled, and it **will not kill somebody else's server** — if one is already running it stops\nwith an error.\n\nThe Endstone carrier has its own live pass. It starts the server through the Endstone CLI, which\ninjects the runtime into the vanilla `bedrock_server.exe`; the CLI and Node must be available:\n\n```\npowershell -File carriers\\endstone\\smoke.ps1 -ServerRoot <Endstone server root>\n```\n\nIt stages the loader package and two Node plugins, drives `plugins` / `endstone:disable` /\n`endstone:enable` / `stop`, and checks the plugin files, the crash fault and the carrier's removal\nwarning. The CLI is looked up at `%TEMP%\\endstone-venv\\Scripts\\endstone.exe`, then `ENDSTONE_EXE`,\nthen PATH.\n\nA shorter carrier-only pass runs against an already installed lip package, without staging\nloaders or plugins:\n\n```\npowershell -File carriers\\endstone\\smoke-live.ps1 -ServerRoot <server root>\nbash carriers/endstone/smoke.sh <server root>\n```\n\nThe Linux script uses `ENDSTONE_EXE` or `endstone` on PATH. Both assert that the CLR comes up, the\ncarrier takes over, the parent enables it, and the server stops cleanly.\n\n### Carrier: Endstone\n\nWindows:\n\n```\ncarriers\\endstone\\build.bat\ncarriers\\endstone\\deploy.bat <folder containing bedrock_server.exe>\nendstone -s <folder containing bedrock_server.exe>\n```\n\nLinux:\n\n```\nbash carriers/endstone/build.sh\nbash carriers/endstone/deploy.sh <folder containing bedrock_server>\nendstone -s <folder containing bedrock_server>\n```\n\n`build.sh` needs CMake and a C++20 compiler; the SDK and nlohmann/json are shallow-cloned by CMake,\nand nethost is fetched from nuget.org. `deploy.sh` copies the plugin, `libnethost.so` and the\nmanaged core; the plugin is linked with `$ORIGIN`, so `libnethost.so` sits beside it.\n\nThree structural differences from the LeviLamina carrier, all dictated by the parent:\n\n- **Plugins are loaded by file**, so the carrier itself is a single `plugins/hosihikari.dll` (or\n  `plugins/hosihikari.so`); the managed core still lives in `plugins/hosihikari/` (the data folder\n  the parent assigns by plugin name). Our packages are directories, so the loader overrides\n  `loadPlugins`.\n- **The nethost library must be resolvable**: on Windows `nethost.dll` sits next to\n  `bedrock_server.exe`, because Endstone loads plugins with a plain `LoadLibrary` and resolves\n  dependencies from the application directory. On Linux `libnethost.so` sits next to the plugin and\n  is found through `$ORIGIN`. The LeviLamina carrier has no such problem because that parent adds\n  the mod directory to `PATH`.\n- **Plugin names are normalised**: Endstone accepts `^[a-z0-9_]+$` and forbids a leading `endstone`,\n  so `Bar` appears to the parent as `bar` while the managed side still tracks it by its manifest\n  name.\n\n### Carrier: self-hosted Linux\n\n```\nbash carriers/selfhosted-linux/build.sh\nbash carriers/selfhosted-linux/deploy.sh <folder containing bedrock_server>\n./hosihikari-server\n```\n\n`hosihikari-server` preloads `plugins/hosihikari/libhosihikari.so` with `LD_PRELOAD`. The shim\nintercepts `__libc_start_main`, starts the CLR and the core before BDS' `main`, and the core scans\n`plugins/` itself (ADR-0005 / 0013 / 0018). The launcher `cd`s to the server folder, so the core's\nrelative paths land on the right server root; it needs the .NET 10 runtime installed.\n\nThe self-hosted target is BDS 1.21.3: the container itself is BDS-version-agnostic, but the\ncapability surface (星光) stops there (ADR-0001).\n\nSelf-hosted plugins are precompiled assembly packages; there is no runtime enable/disable\n(ADR-0020). A carrier-only live pass:\n\n```\nbash carriers/selfhosted-linux/smoke.sh <folder containing bedrock_server>\n```\n\n### Native seam (carrier-independent)\n\n```\ncmake -S verify -B build -G \"Visual Studio 18 2026\" -A x64\ncmake --build build --config Release\n./build/Release/host-glue.exe <managed output directory>\n```\n\nIt walks the startup sequence and calls the managed entry point, reporting each of the four steps.\nBuild the managed side first with `dotnet build src/Hosihikari.PluginManager.csproj -c Release`.\n\n`verify/host-dll/` and `verify/injector/` are the same thing inside a **real BDS process**: the\nfirst builds the startup sequence as a DLL with an exported entry point, the second injects it into a\nsuspended `bedrock_server.exe` and calls that export.\n\n> `injector` is **verification scaffolding, not a deliverable**, and is not meant to become a\n> general-purpose injector. It exists because ADR-0022 defers \"who loads us in production\" (PreLoader\n> only offers `DllMain`, which conflicts with ADR-0016), not \"whether we can be loaded\".\n\n## What CI covers\n\n- **The three `verify/` targets** (host-glue, host-dll, injector) build on `windows-latest`.\n- **`carriers/levilamina/`** builds on `windows-latest`. It pins the LLVM version and caches\n  `~/AppData/Local/.xmake`: upstream's `levilamina` package ships no prebuilt binaries, so the first\n  run compiles LeviLamina from source (about ten minutes) and later runs reuse the cache.\n- **`carriers/endstone/`** builds on `windows-latest` and `ubuntu-latest` in about a minute — its\n  SDK is a header-only interface library, so only our own code is compiled.\n- **`carriers/selfhosted-linux/`** builds and deploys on `ubuntu-latest`; `verify-live` with the\n  `selfhosted` input starts BDS through the preloaded shim.\n- **`verify-lip`** (manual) installs the Linux variant with lip on `ubuntu-latest` and checks the\n  placement.\n- **`verify-live`** (manual) downloads BDS, installs Endstone and the released lip package, starts\n  the server on Windows and Linux, and checks that the CLR and carrier come up and the server stops.\n\nLive carrier behaviour is covered by the manual `verify-live` workflow. The fuller\ndelivery/enable/disable/unload/reload pass remains local via `smoke.ps1`.\n\n## Distribution\n\n`tooth.json` sits at the **repository root**: lip resolves the `tooth` field as a whole Git\nrepository, so anything below the root is invisible to it. One package, four variants:\n\n| Variant | What it installs |\n|---|---|\n| default (no label) | The self-hosted Linux carrier: `hosihikari-server` at the server root, the native shim into `plugins/hosihikari/` |\n| `#levilamina` | The LeviLamina carrier into `plugins/hosihikari/`; the Core package adds the managed files |\n| `#endstone` | The Endstone carrier on Windows and Linux: Windows places the DLL and `nethost.dll` next to `bedrock_server.exe`; Linux places the `.so` and `libnethost.so` into `plugins/`. `platform` selects the archive |\n\n```\nlip install github.com/HosihikariFramework/HostingShim                # self-hosted Linux\nlip install github.com/HosihikariFramework/HostingShim#levilamina     # LeviLamina\nlip install github.com/HosihikariFramework/HostingShim#endstone\n```\n\nThe suffix-less package is the self-hosted Linux carrier; LeviLamina is the labeled variant. Every\nvariant depends on the [Core package](https://github.com/HosihikariFramework/PluginManager),\nwhich lip installs into `plugins/hosihikari/`; the native shim checks the hosting-contract version\nbefore it starts the runtime. The release assets contain only native files; the\n`deploy.bat` and `deploy.sh` scripts also copy a sibling core checkout for source deployments; the\nversion comes from a Git tag, so **a tag and a matching release are required before any of this can\nbe installed**. Tagging `v*` runs the release workflow that builds all four archives and attaches\nthem to one release. The self-hosted post-install script marks `hosihikari-server` executable; if\nscripts are skipped, run `chmod +x hosihikari-server` yourself.\n\nlip resolves versions through the **Go module proxy** (`proxy.golang.org`), not git tags directly,\nso a freshly pushed tag takes a while to become installable: until the proxy indexes it,\n`lip install` reports \"Failed to find the latest version\". The variants above are installed this way.\n\n## Not done yet\n\nSelf-hosted Windows remains deferred (ADR-0022). LeviLamina, Endstone on Windows and Linux, and\nself-hosted Linux are in place.\n\n## Licence\n\nLGPL-3.0-or-later, see [LICENSE.md](LICENSE.md).\n"},{"file":"README.zh_hans.md","lang":"zh-Hans","text":"# HostingShim\n\n[English](README.md) | [简体中文](README.zh_hans.md)\n\n星光框架的**原生层**，职责名是 **HostingShim**（CLR 寄宿垫片）：把 CLR 托管进 BDS 进程，然后把控制权交给插件管理者\n[`PluginManager`](https://github.com/HosihikariFramework/PluginManager)。\n\n它只做四件事：定位 hostfxr、以插件管理者的 `runtimeconfig.json` 初始化运行时、载入插件管理者程序集、取托管入口。\n其余一切（发现、依赖、隔离、生命周期）都在托管侧。它不投影载体 API —— 那一侧是 **BindingShim**，\n由星光产出（ADR-0021）。\n\n## 这个仓里有什么\n\n| | |\n|---|---|\n| `common/` | 启动序列 —— **载体无关**，各载体的目标都编这一段 |\n| `carriers/` | 各载体的目标：`levilamina/`（xmake）、`endstone/`（CMake，Windows 与 Linux）与 `selfhosted-linux/`（CMake） |\n| `verify/` | 证明「原生 → 托管」这一跳的验证程序与脚手架 |\n\nnethost 的头文件与静态库**按版本从 NuGet 取**，不随仓带二进制 —— 载体与 `verify/` 两处构建各自下载。\n\n## 跑一遍\n\n### 载体（LeviLamina）\n\n```\ncarriers\\levilamina\\build.bat\ncarriers\\levilamina\\deploy.bat <服务端根目录>\n```\n\n`build.bat` 自己用 `vswhere` 找 vcvars、接上 clang-cl；出网要走代理的网络请先设好 `https_proxy`\n（脚本不替你设）。产物与清单由上游的 `@levibuildscript/modpacker` 落到 `bin/hosihikari/`，\n`deploy.bat` 再把它与插件管理者、nethost.dll 一起铺进 `plugins/hosihikari/`。\n\n真机的一条龙 —— 起服、依次打 `show`/`disable`/`enable`/`unload`/`load`、再断言日志：\n\n```\npowershell -File carriers\\levilamina\\smoke.ps1 -ServerRoot <服务端根目录>\n```\n\n它会先跑一遍托管侧的断言宿主（顺带产出插件包），所以要有并列的 `PluginManager` checkout。\n需要一台已装好 LeviLamina 的服务端；**它不会去杀别人的服务端**，发现已经在跑就直接报错退出。\n\nEndstone 载体另有一条真机路径。它通过 Endstone CLI 启动服务端（CLI 负责把运行时注入原版\n`bedrock_server.exe`），需要 CLI 与 Node：\n\n```\npowershell -File carriers\\endstone\\smoke.ps1 -ServerRoot <Endstone 服务端根目录>\n```\n\n它铺加载器包与两个 Node 插件，依次打 `plugins` / `endstone:disable` / `endstone:enable` /\n`stop`，断言插件写出的文件、崩溃故障与载体的移除告警。CLI 默认找\n`%TEMP%\\endstone-venv\\Scripts\\endstone.exe`，也可以用 `ENDSTONE_EXE` 指。\n\n只验载体本身的一条短路径，对着已经用 lip 装好的包跑，不铺加载器与插件：\n\n```\npowershell -File carriers\\endstone\\smoke-live.ps1 -ServerRoot <服务端根目录>\nbash carriers/endstone/smoke.sh <服务端根目录>\n```\n\nLinux 脚本用 `ENDSTONE_EXE` 或 PATH 上的 `endstone`。两边都断言 CLR 起来、载体接管、父级启用载体、\n服务端正常停服。\n\n### 载体（Endstone）\n\nWindows：\n\n```\ncarriers\\endstone\\build.bat\ncarriers\\endstone\\deploy.bat <bedrock_server 所在目录>\nendstone -s <bedrock_server 所在目录>\n```\n\nLinux：\n\n```\nbash carriers/endstone/build.sh\nbash carriers/endstone/deploy.sh <bedrock_server 所在目录>\nendstone -s <bedrock_server 所在目录>\n```\n\n`build.sh` 需要 CMake 与 C++20 编译器；SDK 与 nlohmann/json 由 CMake 浅克隆，nethost 从 nuget.org 取。\n`deploy.sh` 铺插件、`libnethost.so` 与插件管理者；插件带 `$ORIGIN`，所以 `libnethost.so` 放在它旁边。\n\n与 LeviLamina 那套的三处结构差异，都是父级的形状决定的：\n\n- **插件是按文件加载的**，所以载体本身是 `plugins/hosihikari.dll`（Linux 上是\n  `plugins/hosihikari.so`）一个文件；插件管理者仍在 `plugins/hosihikari/`（父级按插件名给的数据目录）。\n  我们的包是目录，因此覆盖了 `loadPlugins`。\n- **nethost 库必须能被解析到**：Windows 上 `nethost.dll` 放在 `bedrock_server.exe` 旁边，因为\n  Endstone 用普通 `LoadLibrary` 加载插件，依赖按\"应用目录 + 当前目录\"找；Linux 上\n  `libnethost.so` 放在插件旁边，由 `$ORIGIN` 找到。LeviLamina 那边是父级把 mod 目录加进了 PATH，\n  这里没有这待遇。\n- **插件名会被规范化**：Endstone 只接受 `^[a-z0-9_]+$` 且不以 `endstone` 开头，所以 `Bar` 在父级\n  那边叫 `bar`，托管侧仍按清单里的名字记账。\n\n### 载体（自持态 Linux）\n\n```\nbash carriers/selfhosted-linux/build.sh\nbash carriers/selfhosted-linux/deploy.sh <bedrock_server 所在目录>\n./hosihikari-server\n```\n\n`hosihikari-server` 用 `LD_PRELOAD` 预加载 `plugins/hosihikari/libhosihikari.so`。垫片拦截\n`__libc_start_main`，在 BDS 的 `main` 之前启动 CLR 与插件管理者，插件管理者自己枚举 `plugins/`\n（ADR-0005 / 0013 / 0018）。启动器会先切到服务端目录，插件管理者的相对路径因此落在正确的服务端根上；\n需要系统已装 .NET 10 运行时。\n\n自持态的目标是 BDS 1.21.3：容器本身与 BDS 版本无关，但能力面（星光）止于那里（ADR-0001）。\n\n自持态插件是预编译程序集包；没有运行期启停（ADR-0020）。只验载体本身的真机路径：\n\n```\nbash carriers/selfhosted-linux/smoke.sh <bedrock_server 所在目录>\n```\n\n### 原生缝（与载体无关）\n\n```\ncmake -S verify -B build -G \"Visual Studio 18 2026\" -A x64\ncmake --build build --config Release\n./build/Release/host-glue.exe <托管侧输出目录>\n```\n\n它会走完启动序列并调用托管的入口，四步各自报告成败。托管侧先用\n`dotnet build src/Hosihikari.PluginManager.csproj -c Release` 编出来。\n\n`verify/host-dll/` 与 `verify/injector/` 是同一件事在**真实 BDS 进程里**的版本：前者把启动序列编成一个\n导出入口的 DLL，后者把它注入一个挂起启动的 `bedrock_server.exe`，再显式调那个导出。\n\n> `injector` 是**验证脚手架，不是交付物**，也不打算做成通用注入器 —— 它存在的唯一理由是\n> ADR-0022 暂缓的是\"生产里谁加载我们\"（PreLoader 只给 `DllMain`，与 ADR-0016 冲突），而不是\n> \"能不能被加载\"。要把它用在别处，先想清楚这一点。\n\n## CI 覆盖到哪\n\n- **`verify/` 的三个目标**（host-glue / host-dll / injector）在 `windows-latest` 上编出来。\n- **`carriers/levilamina/`** 在 `windows-latest` 上编出来。它钉住 LLVM 版本，并缓存 `~/AppData/Local/.xmake`：\n  上游的 `levilamina` 包没有预编译体，第一次会把 LeviLamina 从源码编一遍（约十分钟），之后走缓存。\n- **`carriers/endstone/`** 在 `windows-latest` 与 `ubuntu-latest` 上编出来，约一分钟 —— 它的 SDK 是\n  纯头文件的 INTERFACE 库，只编我们自己的代码。\n- **`carriers/selfhosted-linux/`** 在 `ubuntu-latest` 上构建与装配；`verify-live` 的 `selfhosted`\n  输入用预加载垫片起 BDS。\n- **`verify-lip`**（手动）在 `ubuntu-latest` 上用 lip 装 Linux 变体并检查落盘。\n- **`verify-live`**（手动）下载 BDS，装 Endstone 与 lip 发布包，在 Windows 与 Linux 上起服，断言 CLR\n  与载体起来、服务端正常停服。\n\n更完整的交付/启停/卸载/重载仍由本地的 `smoke.ps1` 跑，需要一台真服务端。\n\n## 分发\n\n`tooth.json` 在**仓根**：lip 把 `tooth` 字段整个当成一个 Git 仓库来解析，仓根以下的东西它看不见。\n一份包，四个变体：\n\n| 变体 | 装什么 |\n|---|---|\n| 默认（不带 label） | 自持态 Linux 载体：`hosihikari-server` 放服务端根，原生垫片进 `plugins/hosihikari/` |\n| `#levilamina` | LeviLamina 载体，落进 `plugins/hosihikari/`；托管文件由 Core 包补齐 |\n| `#endstone` | Endstone 载体，Windows 与 Linux 共用：Windows 把 dll 与 `nethost.dll` 放到 `bedrock_server.exe` 旁边；Linux 把 `.so` 与 `libnethost.so` 放进 `plugins/`。由 `platform` 选择附件 |\n\n```\nlip install github.com/HosihikariFramework/HostingShim                # 自持态 Linux\nlip install github.com/HosihikariFramework/HostingShim#levilamina     # LeviLamina\nlip install github.com/HosihikariFramework/HostingShim#endstone\n```\n\n无后缀的包是自持态 Linux 载体；LeviLamina 改用带 label 的变体。每个变体都依赖\n[Core 包](https://github.com/HosihikariFramework/PluginManager)，lip 会把它装进\n`plugins/hosihikari/`；原生垫片启动前会检查入口契约版本。发布附件只含原生文件；\n`deploy.bat` 与 `deploy.sh` 在源码部署时还会从同级插件管理者检出复制一份；版本来自 Git tag，\n所以**要先有标签与对应的 release 才装得了**。\n打 `v*` 会跑发布工作流，编出四个归档并挂到同一个 release。自持态的 post_install 脚本会给\n`hosihikari-server` 加可执行位；跳过脚本时请自己 `chmod +x hosihikari-server`。\n\nlip 解析版本走的是 **Go module proxy**（`proxy.golang.org`），不是直接看 git tag —— 所以刚推上去的\n标签要等代理索引到才能装，在那之前 `lip install` 会报 \"Failed to find the latest version\"。\n上面的变体就是这样装出来的。\n\n## 还没做的\n\n自持态 Windows 仍按 ADR-0022 暂缓。LeviLamina、Endstone（Windows 与 Linux）与自持态 Linux\n都已就位。\n\n## 许可\n\nLGPL-3.0-or-later，见 [LICENSE.md](LICENSE.md)。\n"}],"gallery":[],"versions":[{"version":"1.1.0","prerelease":false,"released":"2026-10-22T07:50:23Z","releaseUrl":"https://github.com/HosihikariFramework/HostingShim/releases/tag/v1.1.0","manifestUrl":"https://github.com/HosihikariFramework/HostingShim/blob/v1.1.0/tooth.json","info":{"name":"星光","description":"把 CLR 托管进 BDS，并把插件管理交给星光框架核心","tags":["platform:levilamina","platform:linux","platform:endstone","type:mod"]},"variants":{"":[{"side":"server","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.1.*"}},{"side":"client","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.1.*"}}],"levilamina":[{"side":"server","platform":"win-x64","deps":{"github.com/LiteLDev/LeviLamina":"26.51.*","github.com/HosihikariFramework/PluginManager":"1.1.*"}}],"endstone":[{"side":"server","platform":"win-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.1.*"}},{"side":"client","platform":"win-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.1.*"}},{"side":"server","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.1.*"}},{"side":"client","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.1.*"}}]}},{"version":"1.0.0","prerelease":false,"released":"2026-10-21T10:36:31Z","releaseUrl":"https://github.com/HosihikariFramework/HostingShim/releases/tag/v1.0.0","manifestUrl":"https://github.com/HosihikariFramework/HostingShim/blob/v1.0.0/tooth.json","info":{"name":"星光","description":"把 CLR 托管进 BDS，并把插件管理交给星光框架核心","tags":["platform:levilamina","platform:linux","platform:endstone","type:mod"]},"variants":{"":[{"side":"server","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.0.*"}},{"side":"client","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.0.*"}}],"levilamina":[{"side":"server","platform":"win-x64","deps":{"github.com/LiteLDev/LeviLamina":"26.51.*","github.com/HosihikariFramework/PluginManager":"1.0.*"}}],"endstone":[{"side":"server","platform":"win-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.0.*"}},{"side":"client","platform":"win-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.0.*"}},{"side":"server","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.0.*"}},{"side":"client","platform":"linux-x64","deps":{"github.com/HosihikariFramework/PluginManager":"1.0.*"}}]}}],"dependencies":{"github.com/hosihikariframework/pluginmanager":{"id":"github.com/HosihikariFramework/PluginManager","name":"星光 · 核心","owner":"HosihikariFramework","url":"https://levimc.org/mods/github.com/HosihikariFramework/PluginManager/"},"github.com/liteldev/levilamina":{"id":"github.com/LiteLDev/LeviLamina","name":"LeviLamina","owner":"LiteLDev","url":"https://levimc.org/mods/github.com/LiteLDev/LeviLamina/"}},"requiredBy":[]}