Merge branch 'main' into develop

Author: futrime

.github/workflows/build.yml

@@ -1,6 +1,14 @@
 on:
   pull_request:
+    paths:
+      - .github/workflows/build.yml
+      - src/**
+      - xmake.lua
   push:
+    paths:
+      - .github/workflows/build.yml
+      - src/**
+      - xmake.lua
   workflow_dispatch:
 
 jobs:

.github/workflows/release.yml

@@ -5,18 +5,26 @@ on:
 
 jobs:
   build:
+    runs-on: windows-latest
     strategy:
       matrix:
         backend:
           # - libnode
           - lua
           # - python310
           - quickjs
-    runs-on: windows-latest
     steps:
       - uses: actions/checkout@v4
 
       - uses: xmake-io/github-action-setup-xmake@v1
+
+      - uses: actions/cache@v4
+        with:
+          path: |
+            ~/AppData/Local/.xmake
+          key: xmake-${{ hashFiles('xmake.lua') }}
+          restore-keys: |
+            xmake-
       
       - run: |
           xmake repo -u
@@ -27,7 +35,7 @@ jobs:
       - run: |
           xmake -w -y
 
-      - uses: actions/upload-artifact@v3
+      - uses: actions/upload-artifact@v4
         with:
           name: legacy-script-engine-${{ matrix.backend }}-windows-x64-${{ github.sha }}
           path: |
@@ -68,7 +76,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - uses: actions/download-artifact@v3
+      - uses: actions/download-artifact@v4
         with:
           name: legacy-script-engine-${{ matrix.backend }}-windows-x64-${{ github.sha }}
           path: release/
@@ -87,6 +95,7 @@ jobs:
           chmod 400 ~/.ssh/id_rsa
           git config --global user.name "Actions"
           git config --global user.email "shrbox@liteldev.com"
+          rm release/legacy-script-engine-${{ matrix.backend }}/*.pdb
           git clone git@gitea.litebds.com:LiteLDev/legacy-script-engine-${{ matrix.backend }}.git
           cd legacy-script-engine-${{ matrix.backend }}
           rm -rf legacy-script-engine-${{ matrix.backend }}
@@ -116,7 +125,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - uses: actions/download-artifact@v3
+      - uses: actions/download-artifact@v4
         with:
           name: legacy-script-engine-${{ matrix.backend }}-windows-x64-${{ github.sha }}
           path: release/

CHANGELOG.md

@@ -5,6 +5,28 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.2] - 2024-02-06
+
+### Fixed
+
+- Fix runcmdEx error when command has no output
+
+## [0.2.1] - 2024-02-06
+
+### Fixed
+
+- Fix endless loop
+
+## [0.2.0] - 2024-02-06
+
+### Added
+
+- Support LeviLamina 0.7.x
+
+### Fixed
+
+- Fix Device::getIP
+
 ## [0.1.6] - 2024-02-05
 
 ### Fixed
@@ -23,8 +45,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - First release.
 
-  [0.1.5]: https://github.com/LiteLDev/LegacyScriptEngine/compare/v0.1.4...v0.1.5
-
+[0.2.2]: https://github.com/LiteLDev/LegacyScriptEngine/compare/v0.2.1...v0.2.2
+[0.2.1]: https://github.com/LiteLDev/LegacyScriptEngine/compare/v0.2.0...v0.2.1
+[0.2.0]: https://github.com/LiteLDev/LegacyScriptEngine/compare/v0.1.6...v0.2.0
 [0.1.6]: https://github.com/LiteLDev/LegacyScriptEngine/compare/v0.1.5...v0.1.6
 [0.1.5]: https://github.com/LiteLDev/LegacyScriptEngine/compare/v0.1.4...v0.1.5
 [0.1.4]: https://github.com/LiteLDev/LegacyScriptEngine/releases/tag/v0.1.4

README.md

@@ -4,15 +4,17 @@ A plugin engine for running LLSE plugins on LeviLamina
 
 ## Install
 
-### Lua Engine
+To install all engines as a whole, you can use the following command:
 
 ```sh
-lip install gitea.litebds.com/LiteLDev/legacy-script-engine-lua
+lip install github.com/LiteLDev/LegacyScriptEngine
 ```
 
-### QuickJs Engine
+To install a specific engine, you can use the following command:
 
 ```sh
+lip install gitea.litebds.com/LiteLDev/legacy-script-engine-lua
+
 lip install gitea.litebds.com/LiteLDev/legacy-script-engine-quickjs
 ```
 

docs/apis/ScriptAPI/ScriptHelp.md

@@ -4,40 +4,6 @@
 
 They make it easier and more natural for you to develop scripts and avoid a lot of unnecessary details.
 
-## 🎯 Plugin Registration API 
-
-Before you start writing code for your plugin, you first need to provide the loader with some plugin-related information.
-
-`ll.registerPlugin(name, introduction, version, otherInformation)`
-
-- Parameters: 
-
-  - name : `String`  
-    Plugin Name
-    
-  - introduction : `String`  
-    A short description of the plugin.
-    
-  - version : `Array<Integer,Integer,Integer[,VersionStatus]>`  
-    Plugin version information.
-    
-    For `VersionStatus`, the following enumeration can be used
-    | Enum      | Description                        |
-    | --------- | ---------------------------------- |
-    | `Release` | Official release version (default) |
-    | `Beta`    | Test version                       |
-    | `Dev`     | Development Version                |
-    
-  - other : `Object<string,string>`  
-    Other additional information you are willing to provide (such as license, open source address, etc.)
-
-Among them, version version information is an array of version number numbers, such as `[2,0,1]` indicates that the version number is 2.0.1  
-If you do not pass in valid version information, the version number of the plugin will be set to the default value `1.0.0`
-
-For plugin additional information, you can pass in any information you need to inform the user in the same format as `Object` key-value pair. The specific data of the key-value pair needs to be `String` format.
-
-<br>
-
 ## 💼 Script Assist API
 
 The following APIs add necessary auxiliary interfaces to scripts.
@@ -164,4 +130,4 @@ The bottom layer has lock protection, different `fastLog` There will be no strin
 - Return value type:  `Boolean`
   - If it returns `Null`, the cancellation of the task failed.
 
-<br>
+<br>

docs/apis/ScriptAPI/ScriptHelp.zh.md

@@ -4,41 +4,6 @@
 
 他们让你开发脚本变得更加容易而自然，避免了很多无谓的细节问题的纠缠。
 
-## 🎯 插件注册 API
-
-在开始为你的插件编写代码之前，你首先需要向加载器提供一些插件相关的信息
-
-`ll.registerPlugin(name, introduction, version, otherInformation)`
-
-- 参数：
-
-  - name : `String`  
-    插件名字
-    
-  - introduction : `String`  
-    对插件的简短介绍
-    
-  - version : `Array<Integer,Integer,Integer[, VersionStatus]>`  
-    插件的版本信息
-    
-    对于 `VersionStatus`，可以使用以下枚举
-    
-    | Enum              | Description            |
-    | ----------------- | ---------------------- |
-    | `Version.Release` | 正式发布版本（默认值） |
-    | `Version.Beta`    | 测试版本               |
-    | `Version.Dev`     | 开发版本               |
-    
-  - other : `Object<string,string>`  
-    其他你愿意提供的的附加信息（如许可证、开源地址等）
-
-其中，version 版本信息为版本号数字构成的数组，如`[2,0,1]`表示版本号为2.0.1  
-如果你没有传入有效的版本信息，插件的版本号将被设置为默认值`1.0.0`
-
-对于插件附加信息，你可以传入任意你需要告知用户的信息，格式同样为`Object`键值对。键值对的具体数据需要为`String`格式
-
-<br>
-
 ## 💼 脚本辅助 API
 
 下面这些API为脚本增加了必要的辅助接口

docs/index.md

@@ -4,17 +4,17 @@ A plugin engine for running LLSE plugins on LeviLamina
 
 ## Install
 
-Before installing, you need to install a suitable version of LeviLamina server.
-
-### Lua Engine
+To install all engines as a whole, you can use the following command:
 
 ```sh
-lip install gitea.litebds.com/LiteLDev/legacy-script-engine-lua
+lip install github.com/LiteLDev/LegacyScriptEngine
 ```
 
-### QuickJs Engine
+To install a specific engine, you can use the following command:
 
 ```sh
+lip install gitea.litebds.com/LiteLDev/legacy-script-engine-lua
+
 lip install gitea.litebds.com/LiteLDev/legacy-script-engine-quickjs
 ```
 

docs/index.zh.md

@@ -1,37 +1,43 @@
-# 旧版脚本引擎
+# LegacyScriptEngine
 
-用于在 LeviLamina 上运行 LLSE 插件的插件引擎
+一个用于在 LeviLamina 上运行 LLSE 插件的插件引擎
 
 ## 安装
 
-在安装之前，您需要安装合适版本的LeviLamina服务器。
-
-### Lua引擎
+要一次性安装所有引擎，您可以使用以下命令：
 
 ```sh
-lip install gitea.litebds.com/LiteLDev/legacy-script-engine-lua
+lip install github.com/LiteLDev/LegacyScriptEngine
 ```
 
-### QuickJs引擎
+要安装特定的引擎，您可以使用以下命令：
 
 ```sh
+lip install gitea.litebds.com/LiteLDev/legacy-script-engine-lua
+
 lip install gitea.litebds.com/LiteLDev/legacy-script-engine-quickjs
 ```
 
-## 用法
+## 使用
 
-1. 将LLSE插件直接放在`/path/to/bedrock_dedicated_server/plugins/`中。
+1. 直接将 LLSE 插件放在 `/path/to/bedrock_dedicated_server/plugins/` 中。
 
-2. 运行服务器，然后插件将自动迁移到 LeviLamina 插件清单。
+2. 运行服务器，然后插件将自动迁移到 LeviLamina 插件清单中。
 
 3. 要加载它们，您需要重新启动服务器。
 
 ## 贡献
 
-如果您有任何疑问，请创建issue进行讨论。
+如果您有任何问题，请开启一个 issue 来讨论。
 
 欢迎 PR。
 
-## 执照
+## 许可
+
+GPL-3.0-only © LiteLDev
 
-仅 GPL-3.0 © LiteLDev
+源: 与必应的对话， 2024/2/5
+(1) Translate and convert Markdown files - GroupDocs. <https://products.groupdocs.app/translation/markdown>.
+(2) Is there a method for translating markdown formatted text?. <https://stackoverflow.com/questions/30585841/is-there-a-method-for-translating-markdown-formatted-text>.
+(3) Translate Markdown file from English to Chinese - GroupDocs. <https://products.groupdocs.app/translation/markdown/English-Chinese>.
+(4) undefined. <https://gt4t.net/>.

docs/tutorials/create_your_first_plugin.md

@@ -14,10 +14,6 @@ With your IDE in hand, and the server installation complete, you are ready to be
 
 Developing a LLSE Plugin begins with creating your plugin's file. This file should be named "LLMyPlugin.js", replacing "MyPlugin" with what you would like to call your plugin. It should be placed in the plugins folder of your server installation. Some IDEs will allow you to create a new file and choose a location, while others will allow you to choose only after hitting "Save As".
 
-The first line you will need in that file is the one below. For information on parameters for this method, and information on the Script Assist API, you can go [here](https://lse.liteldev.com/apis/ScriptAPI/ScriptHelp/).
-
-`ll.registerPlugin(name, introduction, version, otherInformation)`
-
 This might confuse some developers, as `ll` should be undefined. However, this file is going to be utilized by the LeviLamina ScriptX Engine. `ll` will be automatically included during the script's runtime. This is the same with any other variables/classes you see referenced without a definition.
 
 Now that we have created our .js file, and registered the plugin, all we have to do from here is create an event listener. We do that by utilizing `mc`.

docs/tutorials/create_your_first_plugin.zh.md

@@ -19,10 +19,6 @@
 
 开发一个脚本插件，首先要创建你的插件文件。这个文件应该命名为 "LLMyPlugin.js"，将 "MyPlugin" 替换为你想要的插件名称。它应该被放在你的服务器安装的插件文件夹中。有些开发环境会允许你创建一个新文件并选择一个位置，而其他开发环境则允许你在点击 "另存为" 后才选择。
 
-你在该文件中需要的第一行是下面这行。关于这个方法的参数信息，以及关于Script Assist API的信息，你可以去[这里](https://lse.liteldev.com/zh/apis/ScriptAPI/ScriptHelp/)。
-
-`ll.registerPlugin(name, introduction, version, otherInformation)`。
-
 这可能会使一些开发者感到困惑，因为`ll`应该是未定义的。然而，这个文件将被LeviLamina ScriptX引擎所利用。`ll`将在脚本运行时自动包含。这与你看到的任何其他没有定义的变量/类的引用是一样的。
 
 现在我们已经创建了我们的.js文件，并注册了插件，我们要做的就是创建一个事件监听器。我们通过使用`mc`来实现。