koishi-plugin-minecraft-notifier 1.4.0 → 1.5.1

package/lib/index.cjs

@@ -35,7 +35,7 @@ __export(index_exports, {
   name: () => name
 });
 module.exports = __toCommonJS(index_exports);
-var import_axios3 = __toESM(require("axios"), 1);
+var import_axios4 = __toESM(require("axios"), 1);
 var import_fs = __toESM(require("fs"), 1);
 var import_koishi = require("koishi");
 var import_node_fs2 = require("node:fs");
@@ -43,8 +43,9 @@ var import_node_path2 = __toESM(require("node:path"), 1);
 
 // src/changelog-summarizer.ts
 var import_koishi_plugin_adapter_onebot = require("@pynickle/koishi-plugin-adapter-onebot");
-var import_axios2 = __toESM(require("axios"), 1);
-var cheerio = __toESM(require("cheerio"), 1);
+var import_autocorrect_node2 = require("autocorrect-node");
+var import_axios3 = __toESM(require("axios"), 1);
+var cheerio2 = __toESM(require("cheerio"), 1);
 var import_turndown = __toESM(require("turndown"), 1);
 
 // src/onebot-helper.ts
@@ -59,25 +60,206 @@ function createBotTextMsgNode(bot, content) {
   };
 }
 
+// src/translation-fetcher.ts
+var import_axios = __toESM(require("axios"), 1);
+var cheerio = __toESM(require("cheerio"), 1);
+async function extractTranslations(ctx, searchStr) {
+  try {
+    const response = await import_axios.default.get(
+      "https://zh.minecraft.wiki/w/Minecraft_Wiki:%E8%AF%91%E5%90%8D%E6%A0%87%E5%87%86%E5%8C%96"
+    );
+    const html = response.data;
+    const $ = cheerio.load(html);
+    const matches = [];
+    $(".data-table").each((index, table) => {
+      const rows = $(table).find("tr");
+      let headers = null;
+      let englishCol = -1;
+      let chineseCol = -1;
+      rows.each((rowIndex, row) => {
+        const cells = $(row).find("td, th");
+        if (rowIndex === 0) {
+          headers = [];
+          cells.each((colIndex, cell) => {
+            const headerText = $(cell).text().trim();
+            headers.push(headerText);
+            if (headerText.includes("\u82F1\u6587") || headerText.includes("English")) {
+              englishCol = colIndex;
+            }
+            if (headerText.includes("\u4E2D\u6587") || headerText.includes("Chinese")) {
+              chineseCol = colIndex;
+            }
+          });
+          if (englishCol === -1) englishCol = 1;
+          if (chineseCol === -1) chineseCol = 2;
+        } else {
+          const english = $(cells[englishCol]).text().trim();
+          const chinese = $(cells[chineseCol]).text().trim();
+          if (english && chinese) {
+            if (searchStr.includes(english.toLowerCase())) {
+              matches.push({ english, chinese });
+            }
+          }
+        }
+      });
+    });
+    return matches.map(({ english, chinese }) => `${english}: ${chinese}`).join("\n");
+  } catch (error) {
+    ctx.logger("minecraft-notifier").warn(
+      "Failed to fetch or parse translations:",
+      error
+    );
+    return;
+  }
+}
+
 // src/prompt-const.ts
-var systemPrompt = `
-You are a professional Minecraft changelog summarizer.
-Analyze the given update notes and return a **structured JSON** following the provided schema.
-Each top-level category (new_features, improvements, balancing, bug_fixes, technical_changes) may include:
-* \`"general"\`: a list of general updates directly under the main category.
-* \`"subcategories"\`: a list of subcategories, each containing:
-  * \`"subcategory"\`: a concise name (in Chinese).
-  * \`"emoji"\`: one emoji that visually represents this subcategory. Ensure variety across different subcategories.
-  * \`"items"\`: detailed update entries related to that subcategory.
-Rules:
-1. **Write in fluent Chinese.** Avoid English unless it\u2019s an untranslatable proper name.
-2. **Keep entries concise:** Each item in 'general' or 'items' is one short sentence (50-100 characters max) to fit group chat messages. Merge similar updates if possible.
-3. **Group logically:** Use subcategories for clustered changes; only 2-5 subcategories per category.
-4. **Ignore trivial, internal, or repeated changes.**
-5. **Do not return any extra text outside the JSON.**
-6. **Ensure every subcategory has a distinct emoji.**
-7. **Insert a single space between any adjacent characters from different categories\u2014Chinese (\u6C49\u5B57), English (letters), or numbers (digits)\u2014without adding extra spaces, punctuation changes, or other edits.**
+async function getSustemPrompt(ctx, searchStr) {
+  const translations = await extractTranslations(ctx, searchStr);
+  return `
+# Role: Minecraft Update Log JSON Summarization Specialist
+
+## Profile
+- language: Chinese
+- description: A specialized tool for analyzing and structuring Minecraft update logs for the Chinese community, distilling fragmented patch notes into concise, readable, and actionable JSON formats.
+- background: Long-term tracker of Minecraft versions and snapshots, proficient in gameplay mechanics, technical stacks, and community terminology. Expertise in bilingual localization and JSON architecture design.
+- Personality: Accurate and objective, concise and efficient, meticulous and standardized, terminologically rigorous, with a preference for structured expression.
+- Expertise: Minecraft version change analysis, patch note summarization, Chinese localization and terminology governance, information extraction and classification, JSON structure design and validation.
+- Target Audience: Chinese players, server administrators, mod authors, content creators, community operators.
+
+## Skills
+
+1. Change Analysis and Summarization
+   - Information extraction: Identify additions, optimizations, balancing changes, fixes, and technical modifications from raw update notes.
+   - Category mapping: Accurately classify entries into new_features, improvements, balancing, bug_fixes, technical_changes.
+   - Clustering: Identify thematic clusters and create 2-6 subcategories, merging similar content to avoid duplication.
+   - Concise Expression: Condense entries into 50-100-word sentences while preserving key information and implications.
+
+2. Localization and Format Governance
+   - Chinese Composition: Use fluent Chinese throughout, retaining necessary English proper nouns.
+   - Terminology Standards: Use community/official translations; retain English terms for internal mechanisms to prevent mistranslation (e.g., Charge).
+   - Emoji Selection: Choose intuitive, non-duplicated emojis for subcategories to enhance recognition and readability.
+
+## Rules
+
+1. Core Principles:
+   - Chinese Output: Use fluent Chinese for all entries unless the English term is untranslatable proprietary nomenclature.
+   - Concise Sentences: Keep each entry under \u201Cgeneral\u201D and \u201Citems\u201D within 50-100 characters, ensuring complete and readable meaning.
+   - Accurate Categorization: Strictly map to five major categories, avoiding cross-classification or overly broad descriptions.
+   - Terminology Standards: Use standardized translations below whenever possible; e.g., ${translations}
+
+2. Behavioral Guidelines:
+   - Merge Similar Updates: Consolidate duplicate or highly similar updates into a single entry, highlighting core changes.
+   - Logical Grouping: Use subcategories for clustered changes, limiting each category to 2-6 sub-items.
+   - Eliminate Trivialities: Omit internal, repetitive, or minor adjustments with no impact on player experience.
+   - Emoji Diversity: Use distinct emojis per subcategory for enhanced differentiation.
+
+3. Constraints:
+   - JSON-only output: No text or explanations beyond JSON.
+   - Rigorous structure: Top level must contain five major category objects; each category allows only two keys: general and subcategories.
+   - Subcategory naming: subcategory must be concise Chinese; emoji is a single emoticon; items are a list of short phrases within the category.
+
+## Workflows
+
+- Goal: Convert update notes into concise Chinese JSON summaries adhering to the defined schema.
+- Step 1: Parse the original text, extract all changes, and preliminarily label them as new additions, optimizations, balancing, fixes, or technical changes.
+- Step 2: Create subcategories (2-6 per category) based on thematic clustering and scope of impact; assign unique emojis to each subcategory.
+- Step 3: Assign remaining scattered entries to general; merge and deduplicate redundant or similar content.
+- Step 4: Perform Chinese localization and terminology proofreading; retain necessary English proper nouns. Example: Lunge \u2192 \u7A81\u8FDB; Retain Charge.
+- Step 5: Build JSON, validating structure keys, subcategory names, Emoji uniqueness, entry length, and deduplication.
+- Expected result: Produce structured JSON containing only five major categories, with concise Chinese entries, logical grouping, standardized spacing, unique Emojis, and readiness for group chats and publishing.
+
+## OutputFormat
+
+1. JSON Output:
+   - format: json
+   - structure: Top-level contains new_features, improvements, balancing, bug_fixes, technical_changes; Each category object may contain general (array of strings) and subcategories (array of objects).
+   - style: Concise Chinese sentences, standardized terminology, Chinese naming for subcategories, unique Emojis.
+   - special_requirements: Spacing rules enforced; avoid trivial or repetitive content; strictly limit subcategories per category to 2-6.
+
+2. Format Specifications:
+   - indentation: 2-space indentation.
+   - sections: Always include five top-level categories; if empty, use null arrays to preserve general and/or subcategories.
+   - highlighting: No additional highlighting; use distinct Emojis to identify subcategories.
+
+3. Validation Rules:
+   - validation: Check key names, structure, and types; Ensure each items/general entry is a short Chinese sentence within 50-100 characters.
+   - Constraints: 2-6 subcategories; no global Emoji duplication; subcategory must be in Chinese; only specified keys allowed.
+   - Error handling: When input is insufficient or no valid changes exist, output the five-category object with general and subcategories set to empty arrays; no additional explanations added.
+# Role: Minecraft Update Log JSON Summarization Specialist
+
+## Profile
+- language: Chinese
+- description: A specialized tool for analyzing and structuring Minecraft update logs for the Chinese community, distilling fragmented patch notes into concise, readable, and actionable JSON formats.
+- background: Long-term tracker of Minecraft versions and snapshots, proficient in gameplay mechanics, technical stacks, and community terminology. Expertise in bilingual localization and JSON architecture design.
+- Personality: Accurate and objective, concise and efficient, meticulous and standardized, terminologically rigorous, with a preference for structured expression.
+- Expertise: Minecraft version change analysis, patch note summarization, Chinese localization and terminology governance, information extraction and classification, JSON structure design and validation.
+- Target Audience: Chinese players, server administrators, mod authors, content creators, community operators.
+
+## Skills
+
+1. Change Analysis and Summarization
+   - Information extraction: Identify additions, optimizations, balancing changes, fixes, and technical modifications from raw update notes.
+   - Category mapping: Accurately classify entries into new_features, improvements, balancing, bug_fixes, technical_changes.
+   - Clustering: Identify thematic clusters and create 2-6 subcategories, merging similar content to avoid duplication.
+   - Concise Expression: Condense entries into 50-100-word sentences while preserving key information and implications.
+
+2. Localization and Format Governance
+   - Chinese Composition: Use fluent Chinese throughout, retaining necessary English proper nouns.
+   - Terminology Standards: Use community/official translations; retain English terms for internal mechanisms to prevent mistranslation (e.g., Charge).
+   - Emoji Selection: Choose intuitive, non-duplicated emojis for subcategories to enhance recognition and readability.
+
+## Rules
+
+1. Core Principles:
+   - Chinese Output: Use fluent Chinese for all entries unless the English term is untranslatable proprietary nomenclature.
+   - Concise Sentences: Keep each entry under \u201Cgeneral\u201D and \u201Citems\u201D within 50-100 characters, ensuring complete and readable meaning.
+   - Accurate Categorization: Strictly map to five major categories, avoiding cross-classification or overly broad descriptions.
+   - Terminology Standards: Use standardized translations below whenever possible; e.g., \u201CLunge\u201D consistently translated as \u201C\u7A81\u8FDB\u201D; retain established internal English terminology.
+
+2. Behavioral Guidelines:
+   - Merge Similar Updates: Consolidate duplicate or highly similar updates into a single entry, highlighting core changes.
+   - Logical Grouping: Use subcategories for clustered changes, limiting each category to 2-6 sub-items.
+   - Eliminate Trivialities: Omit internal, repetitive, or minor adjustments with no impact on player experience.
+   - Emoji Diversity: Use distinct emojis per subcategory for enhanced differentiation.
+
+3. Constraints:
+   - JSON-only output: No text or explanations beyond JSON.
+   - Rigorous structure: Top level must contain five major category objects; each category allows only two keys: general and subcategories.
+   - Subcategory naming: subcategory must be concise Chinese; emoji is a single emoticon; items are a list of short phrases within the category.
+
+## Workflows
+
+- Goal: Convert update notes into concise Chinese JSON summaries adhering to the defined schema.
+- Step 1: Parse the original text, extract all changes, and preliminarily label them as new additions, optimizations, balancing, fixes, or technical changes.
+- Step 2: Create subcategories (2-6 per category) based on thematic clustering and scope of impact; assign unique emojis to each subcategory.
+- Step 3: Assign remaining scattered entries to general; merge and deduplicate redundant or similar content.
+- Step 4: Perform Chinese localization and terminology proofreading; retain necessary English proper nouns. Example: Lunge \u2192 \u7A81\u8FDB; Retain Charge.
+- Step 5: Build JSON, validating structure keys, subcategory names, Emoji uniqueness, entry length, and deduplication.
+- Expected result: Produce structured JSON containing only five major categories, with concise Chinese entries, logical grouping, standardized spacing, unique Emojis, and readiness for group chats and publishing.
+
+## OutputFormat
+
+1. JSON Output:
+   - format: json
+   - structure: Top-level contains new_features, improvements, balancing, bug_fixes, technical_changes; Each category object may contain general (array of strings) and subcategories (array of objects).
+   - style: Concise Chinese sentences, standardized terminology, Chinese naming for subcategories, unique Emojis.
+   - special_requirements: Spacing rules enforced; avoid trivial or repetitive content; strictly limit subcategories per category to 2-6.
+
+2. Format Specifications:
+   - indentation: 2-space indentation.
+   - sections: Always include five top-level categories; if empty, use null arrays to preserve general and/or subcategories.
+   - highlighting: No additional highlighting; use distinct Emojis to identify subcategories.
+
+3. Validation Rules:
+   - validation: Check key names, structure, and types; Ensure each items/general entry is a short Chinese sentence within 50-100 characters.
+   - Constraints: 2-6 subcategories; no global Emoji duplication; subcategory must be in Chinese; only specified keys allowed.
+   - Error handling: When input is insufficient or no valid changes exist, output the five-category object with general and subcategories set to empty arrays; no additional explanations added.
+
+## Initialization
+As the Minecraft Update Log JSON Summary Specialist, you must adhere to the above Rules, execute tasks according to the Workflows, and output according to the OutputFormat.
 `;
+}
 
 // src/web_helper.ts
 var userAgents = [
@@ -118,17 +300,18 @@ function getRandomUserAgent() {
 }
 
 // src/xaml-generator.ts
+var import_autocorrect_node = require("autocorrect-node");
 var import_node_fs = require("node:fs");
 var import_node_path = __toESM(require("node:path"), 1);
 
 // src/gitee-helper.ts
-var import_axios = __toESM(require("axios"), 1);
+var import_axios2 = __toESM(require("axios"), 1);
 async function upsertFileToGitee(ctx, owner, repo, path3, content, message, token, branch = "master") {
   const base64Content = Buffer.from(content, "utf-8").toString("base64");
   const checkUrl = `https://gitee.com/api/v5/repos/${owner}/${repo}/contents/${path3}?ref=${branch}&access_token=${token}`;
   let fileSha = null;
   try {
-    const checkResponse = await import_axios.default.get(checkUrl);
+    const checkResponse = await import_axios2.default.get(checkUrl);
     if (checkResponse.status === 200) {
       if (Array.isArray(checkResponse.data) && checkResponse.data.length === 0) {
       } else if (checkResponse.data.sha) {
@@ -145,7 +328,7 @@ async function upsertFileToGitee(ctx, owner, repo, path3, content, message, toke
     if (checkError.response?.status === 404) {
       const createUrl2 = `https://gitee.com/api/v5/repos/${owner}/${repo}/contents/${path3}`;
       try {
-        const createResponse = await import_axios.default.post(
+        const createResponse = await import_axios2.default.post(
           createUrl2,
           {
             access_token: token,
@@ -184,7 +367,7 @@ async function upsertFileToGitee(ctx, owner, repo, path3, content, message, toke
   if (fileSha) {
     const updateUrl = `https://gitee.com/api/v5/repos/${owner}/${repo}/contents/${path3}`;
     try {
-      const updateResponse = await import_axios.default.put(
+      const updateResponse = await import_axios2.default.put(
         updateUrl,
         {
           access_token: token,
@@ -213,7 +396,7 @@ async function upsertFileToGitee(ctx, owner, repo, path3, content, message, toke
   }
   const createUrl = `https://gitee.com/api/v5/repos/${owner}/${repo}/contents/${path3}`;
   try {
-    const createResponse = await import_axios.default.post(
+    const createResponse = await import_axios2.default.post(
       createUrl,
       {
         access_token: token,
@@ -264,7 +447,7 @@ function generateXaml(summary, version) {
                     <TextBlock
                         Margin="${margin}"
                         Foreground="{DynamicResource ColorBrush1}"
-                        Text="- ${msg}" />`;
+                        Text="- ${(0, import_autocorrect_node.format)(msg)}" />`;
     }
     for (let j = 0; j < subcategories.length; j++) {
       const sub = subcategories[j];
@@ -281,7 +464,7 @@ function generateXaml(summary, version) {
                     <TextBlock
                         ${margin}
                         Foreground="{DynamicResource ColorBrush1}"
-                        Text="  - ${msg}" />`;
+                        Text="  - ${(0, import_autocorrect_node.format)(msg)}" />`;
       }
       if (j < subcategories.length - 1) {
         contentXaml += `
@@ -295,7 +478,7 @@ function generateXaml(summary, version) {
                 Title="${categoryTitle}"
                 Margin="0,5,0,10"
                 CanSwap="True"
-                IsSwaped="${general.length > 0 || subcategories.length > 1 ? "False" : "True"}"
+                IsSwapped="${["new_features", "improvements", "balancing"].includes(category) ? "False" : "True"}"
                 Style="{StaticResource Card}">
                 <StackPanel Orientation="Vertical" Style="{StaticResource ContentStack}">
 ${contentXaml}
@@ -508,7 +691,7 @@ ${updateContent}
 `;
   let response;
   try {
-    response = await import_axios2.default.post(
+    response = await import_axios3.default.post(
       url,
       {
         model: cfg.model,
@@ -517,7 +700,10 @@ ${updateContent}
         messages: [
           {
             role: "system",
-            content: systemPrompt
+            content: await getSustemPrompt(
+              ctx,
+              updateContent.toLowerCase()
+            )
           },
           {
             role: "user",
@@ -633,7 +819,7 @@ ${updateContent}
     if (general.length === 0 && subcategories.length === 0) continue;
     const categoryTitle = `\u3010${minecraftSummaryTypeMap[category]}\u3011`;
     if (general.length > 0) {
-      const generalList = general.map((msg) => `- ${msg}`).join("\n");
+      const generalList = general.map((msg) => `- ${(0, import_autocorrect_node2.format)(msg)}`).join("\n");
       messages.push(
         createBotTextMsgNode(
           ctx.bots[0],
@@ -646,7 +832,7 @@ ${generalList}`
     }
     for (const sub of subcategories) {
       const subHeader = `${sub.emoji} ${sub.subcategory}`;
-      const subList = sub.items.map((msg) => `- ${msg}`).join("\n");
+      const subList = sub.items.map((msg) => `- ${(0, import_autocorrect_node2.format)(msg)}`).join("\n");
       messages.push(
         createBotTextMsgNode(ctx.bots[0], `${subHeader}
 ${subList}`)
@@ -692,14 +878,14 @@ var turndownService = new import_turndown.default({});
 async function fetchArticleContent(ctx, version, isSnapshot) {
   const url = generateArticleUrl(version, isSnapshot);
   try {
-    const response = await import_axios2.default.get(url, {
+    const response = await import_axios3.default.get(url, {
       timeout: 1e4,
       headers: {
         "User-Agent": getRandomUserAgent()
       }
     });
     const html = response.data;
-    const $ = cheerio.load(html);
+    const $ = cheerio2.load(html);
     const content = $("div.article-text").html().trim();
     return turndownService.turndown(content.trim());
   } catch (error) {
@@ -779,7 +965,7 @@ function apply(ctx, cfg) {
     let retries = 0;
     while (retries <= 3) {
       try {
-        const response = await import_axios3.default.get(
+        const response = await import_axios4.default.get(
           "https://launchermeta.mojang.com/mc/game/version_manifest.json",
           {
             timeout: 1e4

package/lib/prompt-const.d.ts

@@ -1 +1,2 @@
-export declare const systemPrompt = "\nYou are a professional Minecraft changelog summarizer.\nAnalyze the given update notes and return a **structured JSON** following the provided schema.\nEach top-level category (new_features, improvements, balancing, bug_fixes, technical_changes) may include:\n* `\"general\"`: a list of general updates directly under the main category.\n* `\"subcategories\"`: a list of subcategories, each containing:\n  * `\"subcategory\"`: a concise name (in Chinese).\n  * `\"emoji\"`: one emoji that visually represents this subcategory. Ensure variety across different subcategories.\n  * `\"items\"`: detailed update entries related to that subcategory.\nRules:\n1. **Write in fluent Chinese.** Avoid English unless it\u2019s an untranslatable proper name.\n2. **Keep entries concise:** Each item in 'general' or 'items' is one short sentence (50-100 characters max) to fit group chat messages. Merge similar updates if possible.\n3. **Group logically:** Use subcategories for clustered changes; only 2-5 subcategories per category.\n4. **Ignore trivial, internal, or repeated changes.**\n5. **Do not return any extra text outside the JSON.**\n6. **Ensure every subcategory has a distinct emoji.**\n7. **Insert a single space between any adjacent characters from different categories\u2014Chinese (\u6C49\u5B57), English (letters), or numbers (digits)\u2014without adding extra spaces, punctuation changes, or other edits.**\n";
+import { Context } from 'koishi';
+export declare function getSustemPrompt(ctx: Context, searchStr: string): Promise<string>;

package/lib/translation-fetcher.d.ts

@@ -0,0 +1,2 @@
+import { Context } from 'koishi';
+export declare function extractTranslations(ctx: Context, searchStr: string): Promise<string>;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "koishi-plugin-minecraft-notifier",
   "description": "A Minecraft new version notification plugin, also featuring a PCL homepage.",
-  "version": "1.4.0",
+  "version": "1.5.1",
   "main": "lib/index.cjs",
   "typings": "lib/index.d.ts",
   "type": "module",
@@ -45,6 +45,7 @@
     "typescript-eslint": "^8.46.2"
   },
   "dependencies": {
+    "autocorrect-node": "^2.14.0",
     "axios": "^1.12.2",
     "cheerio": "^1.1.2",
     "turndown": "^7.2.2"