Tags
Creators
Details
1.4.0-SNAPSHOT
Compatibility
Changes
Changelog · v1.4.0
✨ New Features
1. Direct Parsing and Compilation of .sirc Plugin Projects
Based on the built-in SircDecoder, it now supports directly unpacking the complete file system and metadata from .sirc project files. The system will automatically execute the following complete workflow:
Unpack → Project Compilation → JAR Packaging → Output to
scripts/output
Delivering a true one-click experience "from .sirc to loadable external plugin."
2. Folia Plugin Script Compilation Support
The compiler automatically detects the current server environment at runtime:
- If Folia is detected,
- Or if a server supporting the Global Region Scheduler API is detected,
it will automatically declare the following in the generated plugin.yml:
folia-supported: true
This allows the generated script plugin to be properly loaded and run on Folia servers.
⚠️ Note: Script plugins must be compiled after loading ScriptIrc on a Folia server.
3. .sirc Project Parsing and Structure Preview Capability
In addition to unpacking and compilation, this version adds a read-only parsing mode:
- Parse the
.sircfile - Build a virtual file tree
- View the project directory structure via the in-game command
/sirctree
Furthermore, in some projects, the system will:
- Automatically locate
README.md - Parse and convert it into an in-game book
- Send it to the player who executed the compilation command
更新日志 · v1.4.0
✨ 新增功能
1. 直接解析并编译 .sirc 插件项目
基于内置 SircDecoder,现已支持从 .sirc 项目文件中直接解包出完整的文件系统与元数据。
系统将自动执行以下完整流程:
解包 → 项目编译 → JAR 打包 → 输出到
scripts/output
实现真正意义上的 「一键从 .sirc 到可加载外部插件」 的使用体验。
2. Folia 插件脚本编译支持
编译器在运行时会自动检测当前服务端环境:
- 若检测到 Folia
- 或检测到支持 全局区域调度 API 的服务端
则会在生成的 plugin.yml 中自动声明:
folia-supported: true
从而使生成的脚本插件可在 Folia 服务端 正常加载与运行。
⚠️ 注意:脚本插件需在 Folia 服务器上加载 ScriptIrc 后 再进行编译。
3. .sirc 项目解析与结构预览能力
除了解包与编译,本版本还新增 只读解析模式:
- 对
.sirc文件进行解析 - 构建 虚拟文件树
- 可通过游戏内命令
/sirctree查看项目目录结构
此外,在部分项目中系统会:
- 自动查找
README.md - 解析并转换为 游戏内书本
- 发送给执行编译命令的玩家
便于在游戏内快速阅读插件或脚本的使用说明。
🔧 重构与优化
插件数据与目录结构重构
对 scripts 目录及外部插件数据结构进行了系统性优化:
- 统一使用:
scripts/output scripts/output/Data - 插件数据重定向逻辑更加清晰
- 数据隔离性显著提升,降低插件间相互干扰的风险
⚠️ 升级提示
升级至本版本前,建议手动删除旧版 ScriptIrc 的插件数据目录,
以避免因历史目录结构残留而导致的数据混用或潜在冲突。
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Ql58FVwI:lMJ44QsR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ql58FVwI:lMJ44QsR"
}

