@dsh-agentic-roleplay/core 0.12.0 → 0.12.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (44) hide show
  1. package/cordis.patch.yml +108 -0
  2. package/lib/{access-DAw54-NI.js → access-Csp80TFX.js} +2 -2
  3. package/lib/{authoring-tools-4NgDhIJV.js → authoring-tools-BZr4bgBy.js} +25 -771
  4. package/lib/authoring.js +136 -12
  5. package/lib/{child-D3QUNb3m.js → child-DTdY14S9.js} +54 -6
  6. package/lib/client.js +16457 -1938
  7. package/lib/client.js.map +1 -1
  8. package/lib/compaction.js +3 -3
  9. package/lib/dev-context-Cgv_wZbG.js +50 -0
  10. package/lib/doctor.js +6 -3
  11. package/lib/{gallery-Ct6nm4UQ.js → gallery-BNg0rPTp.js} +3 -3
  12. package/lib/{generator-CI8fOnXy.js → generator-9-5at9cZ.js} +2 -2
  13. package/lib/helper.js +5 -9
  14. package/lib/{hooks-BNeoGMHZ.js → hooks-Dtq5KZQX.js} +47 -16
  15. package/lib/images.js +4 -4
  16. package/lib/index.js +152 -476
  17. package/lib/{jail-BIF79PJO.js → jail-DVbPSC0R.js} +2 -2
  18. package/lib/{library-BF9ZMSFz.js → library-DTxakw0z.js} +2 -2
  19. package/lib/{lorebook-author-tools-DBk-V0hp.js → lorebook-author-tools-BjcEUo22.js} +19 -6
  20. package/lib/lorebook-authoring.js +13 -5
  21. package/lib/{narration-xvErE2yp.js → narration--K2XVIHI.js} +2 -2
  22. package/lib/orchestration.js +33 -12
  23. package/lib/{pack-jail-C8EyX9Ix.js → pack-jail-Dt0VTsu0.js} +558 -23
  24. package/lib/{packs-S0SzrVv-.js → packs-DWfR2Ted.js} +2 -2
  25. package/lib/{presenter-agent-Bc478nTA.js → presenter-agent-vFOxIuWv.js} +9 -9
  26. package/lib/{preset-SJZyw0kt.js → preset-Dv5YF2qj.js} +4 -4
  27. package/lib/{preset-author-tools-CzogjK42.js → preset-author-tools-BUzO9mTW.js} +8 -7
  28. package/lib/preset-authoring.js +12 -6
  29. package/lib/{reflection-buQiSdvq.js → reflection-Dd3pEiZB.js} +14 -15
  30. package/lib/{presets-DQ5rioMh.js → serial-BUaJGwVy.js} +1241 -390
  31. package/lib/{turn-guard-BSAba8sp.js → turn-guard-87NE-Cnp.js} +3 -3
  32. package/locale/de.json +6 -0
  33. package/locale/en.json +6 -0
  34. package/locale/es.json +6 -0
  35. package/locale/fr.json +6 -0
  36. package/locale/ja.json +6 -0
  37. package/locale/pt.json +6 -0
  38. package/locale/ru.json +6 -0
  39. package/locale/zh.json +6 -0
  40. package/package.json +34 -34
  41. package/prompts/en/import/style.md +2 -1
  42. package/prompts/en/world/procedure.md +1 -1
  43. package/prompts/zh/import/style.md +2 -1
  44. package/prompts/zh/world/procedure.md +1 -1
@@ -1,5 +1,5 @@
1
- import { D as finishOf, E as cutOff } from "./child-D3QUNb3m.js";
2
- import { r as guardRepeatedCalls } from "./hooks-BNeoGMHZ.js";
1
+ import { D as finishOf, E as cutOff } from "./child-DTdY14S9.js";
2
+ import { r as guardRepeatedCalls } from "./hooks-Dtq5KZQX.js";
3
3
  import { ReasoningEffortId, createUserMessage } from "@deepseek-ai/dsh-llm";
4
4
  // src/host/authoring/turn-guard.ts
5
5
  /**
@@ -49,4 +49,4 @@ function guardAuthoringTurns(ctx, prompts, languageOf, reasoning = () => "") {
49
49
  }
50
50
  export { guardAuthoringTurns as t };
51
51
 
52
- //# sourceMappingURL=turn-guard-BSAba8sp.js.map
52
+ //# sourceMappingURL=turn-guard-87NE-Cnp.js.map
package/locale/de.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "Kern des agentischen Rollenspiels",
4
+ "description": "Stellt Rollenspieloberfläche, Agentensteuerung, Autorenwerkzeuge und Geschichtenspeicher bereit."
5
+ }
6
+ }
package/locale/en.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "Agentic Role Play Core",
4
+ "description": "Provides the roleplay interface, agent orchestration, authoring tools, and story storage."
5
+ }
6
+ }
package/locale/es.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "Núcleo de juego de rol agéntico",
4
+ "description": "Ofrece la interfaz de juego de rol, la coordinación de agentes, herramientas de creación y almacenamiento de historias."
5
+ }
6
+ }
package/locale/fr.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "Cœur du jeu de rôle agentique",
4
+ "description": "Fournit l’interface de jeu de rôle, l’orchestration des agents, les outils de création et le stockage des histoires."
5
+ }
6
+ }
package/locale/ja.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "エージェント・ロールプレイ コア",
4
+ "description": "ロールプレイ画面、エージェントの連携、作成ツール、物語の保存機能を提供します。"
5
+ }
6
+ }
package/locale/pt.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "Núcleo do jogo de interpretação agêntico",
4
+ "description": "Disponibiliza a interface de jogo de interpretação, a coordenação de agentes, ferramentas de criação e armazenamento de histórias."
5
+ }
6
+ }
package/locale/ru.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "Ядро агентной ролевой игры",
4
+ "description": "Предоставляет интерфейс ролевой игры, координацию агентов, инструменты создания и хранение историй."
5
+ }
6
+ }
package/locale/zh.json ADDED
@@ -0,0 +1,6 @@
1
+ {
2
+ "meta": {
3
+ "title": "智能体角色扮演核心",
4
+ "description": "提供角色扮演界面、智能体编排、创作工具和故事存储。"
5
+ }
6
+ }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dsh-agentic-roleplay/core",
3
- "version": "0.12.0",
3
+ "version": "0.12.2",
4
4
  "description": "Core plugin of the agentic roleplay bundle for DeepSeek Harness: roleplay UI, orchestration and storage.",
5
5
  "author": {
6
6
  "name": "Firefox2100",
@@ -20,7 +20,8 @@
20
20
  "./helper": "./lib/helper.js",
21
21
  "./images": "./lib/images.js",
22
22
  "./client": "./lib/client.js",
23
- "./package.json": "./package.json"
23
+ "./package.json": "./package.json",
24
+ "./locale/*.json": "./locale/*.json"
24
25
  },
25
26
  "dsh": {
26
27
  "bundle": {
@@ -62,6 +63,7 @@
62
63
  },
63
64
  "files": [
64
65
  "icon.svg",
66
+ "locale",
65
67
  "lib/*.js",
66
68
  "packs",
67
69
  "prompts",
@@ -78,41 +80,39 @@
78
80
  "@deepseek-ai/schemastery": "^3.18.5"
79
81
  },
80
82
  "dependencies": {
81
- "@dsh-agentic-roleplay/state": "0.12.0",
82
- "@dsh-ai-providers/core": "^0.7.0"
83
+ "@dsh-agentic-roleplay/state": "0.12.2"
83
84
  },
84
85
  "devDependencies": {
85
- "@deepseek-ai/cordis": "^4.0.5",
86
- "@deepseek-ai/cordis-plugin-loader": "^1.0.6",
87
- "@deepseek-ai/dsh-agent": "0.2.2-rc.1",
88
- "@deepseek-ai/dsh-agent-loop": "0.2.2-rc.1",
89
- "@deepseek-ai/dsh-api-remotes": "0.2.2-rc.1",
90
- "@deepseek-ai/dsh-client-locale": "0.2.2-rc.1",
91
- "@deepseek-ai/dsh-client-store": "0.2.2-rc.1",
92
- "@deepseek-ai/dsh-client-ui-chat": "0.2.2-rc.1",
93
- "@deepseek-ai/dsh-client-ui-conversation": "0.2.2-rc.1",
94
- "@deepseek-ai/dsh-client-ui-layout": "0.2.2-rc.1",
95
- "@deepseek-ai/dsh-client-ui-primitives": "0.2.2-rc.1",
96
- "@deepseek-ai/dsh-client-ui-renderer": "0.2.2-rc.1",
97
- "@deepseek-ai/dsh-client-ui-session": "0.2.2-rc.1",
98
- "@deepseek-ai/dsh-client-ui-settings": "0.2.2-rc.1",
99
- "@deepseek-ai/dsh-client-ui-sidebar": "0.2.2-rc.1",
100
- "@deepseek-ai/dsh-client-ui-sidebar-right": "0.2.2-rc.1",
101
- "@deepseek-ai/dsh-client-ui-slots": "0.2.2-rc.1",
102
- "@deepseek-ai/dsh-compaction": "0.2.2-rc.1",
103
- "@deepseek-ai/dsh-compaction-basic": "0.2.2-rc.1",
104
- "@deepseek-ai/dsh-host-webserver": "0.2.2-rc.1",
105
- "@deepseek-ai/dsh-llm": "0.2.2-rc.1",
106
- "@deepseek-ai/dsh-session": "0.2.2-rc.1",
107
- "@deepseek-ai/dsh-session-projection": "0.2.2-rc.1",
108
- "@deepseek-ai/dsh-subagent": "0.2.2-rc.1",
109
- "@deepseek-ai/dsh-subagent-spawn-in-process": "0.2.2-rc.1",
110
- "@deepseek-ai/dsh-system-prompt": "0.2.2-rc.1",
111
- "@deepseek-ai/dsh-token-meter": "0.2.2-rc.1",
112
- "@deepseek-ai/dsh-tool-executor-native": "0.2.2-rc.1",
113
- "@deepseek-ai/dsh-tools": "0.2.2-rc.1",
114
- "@deepseek-ai/dsh-user-approval": "0.2.2-rc.1",
86
+ "@deepseek-ai/cordis": "^4.1.0",
87
+ "@deepseek-ai/cordis-plugin-loader": "^1.1.0",
88
+ "@deepseek-ai/dsh-agent": ">=0.2.2-rc.1 <0.2.3",
89
+ "@deepseek-ai/dsh-agent-loop": ">=0.2.2-rc.1 <0.2.3",
90
+ "@deepseek-ai/dsh-client-locale": ">=0.2.2-rc.1 <0.2.3",
91
+ "@deepseek-ai/dsh-client-store": ">=0.2.2-rc.1 <0.2.3",
92
+ "@deepseek-ai/dsh-client-ui-chat": ">=0.2.2-rc.1 <0.2.3",
93
+ "@deepseek-ai/dsh-client-ui-conversation": ">=0.2.2-rc.1 <0.2.3",
94
+ "@deepseek-ai/dsh-client-ui-layout": ">=0.2.2-rc.1 <0.2.3",
95
+ "@deepseek-ai/dsh-client-ui-renderer": ">=0.2.2-rc.1 <0.2.3",
96
+ "@deepseek-ai/dsh-client-ui-settings": ">=0.2.2-rc.1 <0.2.3",
97
+ "@deepseek-ai/dsh-client-ui-sidebar": ">=0.2.2-rc.1 <0.2.3",
98
+ "@deepseek-ai/dsh-client-ui-sidebar-right": ">=0.2.2-rc.1 <0.2.3",
99
+ "@deepseek-ai/dsh-client-ui-slots": ">=0.2.2-rc.1 <0.2.3",
100
+ "@deepseek-ai/dsh-compaction": ">=0.2.2-rc.1 <0.2.3",
101
+ "@deepseek-ai/dsh-compaction-basic": ">=0.2.2-rc.1 <0.2.3",
102
+ "@deepseek-ai/dsh-host-webserver": ">=0.2.2-rc.1 <0.2.3",
103
+ "@deepseek-ai/dsh-llm": ">=0.2.2-rc.1 <0.2.3",
104
+ "@deepseek-ai/dsh-scope": ">=0.2.2-rc.1 <0.2.3",
105
+ "@deepseek-ai/dsh-session": ">=0.2.2-rc.1 <0.2.3",
106
+ "@deepseek-ai/dsh-session-projection": ">=0.2.2-rc.1 <0.2.3",
107
+ "@deepseek-ai/dsh-subagent": ">=0.2.2-rc.1 <0.2.3",
108
+ "@deepseek-ai/dsh-subagent-spawn-in-process": ">=0.2.2-rc.1 <0.2.3",
109
+ "@deepseek-ai/dsh-system-prompt": ">=0.2.2-rc.1 <0.2.3",
110
+ "@deepseek-ai/dsh-token-meter": ">=0.2.2-rc.1 <0.2.3",
111
+ "@deepseek-ai/dsh-tool-executor-native": ">=0.2.2-rc.1 <0.2.3",
112
+ "@deepseek-ai/dsh-tools": ">=0.2.2-rc.1 <0.2.3",
113
+ "@deepseek-ai/dsh-user-approval": ">=0.2.2-rc.1 <0.2.3",
115
114
  "@deepseek-ai/schemastery": "^3.18.5",
115
+ "@dsh-ai-providers/core": "^0.7.0",
116
116
  "@types/node": "^22.20.0",
117
117
  "@types/react": "~18.3.1",
118
118
  "dsh-roleplay-model": "0.0.0",
@@ -1,4 +1,5 @@
1
1
  You turn the instructions a character card gives to the AI into the style notes of a role-playing world. ${rules}
2
2
  Keep only guidance about how the story is written and how the characters behave: voice, tone, perspective, tense, pacing, level of detail, staying in character, manner of speaking, and how a character reacts to what it is asked to do or declines to do. Write it as short, direct guidance to the AI, in the language of the instructions, and keep what the card asks for as faithfully as it can be said in a few sentences.
3
- Leave out, and list in left_out: rules of the game or how to run it, formats and status panels, instructions about tools, scripts, anything addressed to the player, and anything about specific characters, places or events (those belong to the world, not to the style). Never keep an instruction to add something to every reply (a status bar, a panel, an update block, markup, a code block, HTML), even when it shares a sentence with a style instruction: the story shows its tracked values itself, so list it in left_out and write the style part without it. Do not add guidance the instructions do not give. When they give none of one kind, leave that field empty.
3
+ Rules of the world that the instructions lay down (what exists, does not exist or may not happen in the story, such as "there are no firearms") go in world_rules, one short sentence each, in the language of the instructions and as faithfully as they say it; do not repeat them in the style notes.
4
+ Leave out, and list in left_out: how to run the game, formats and status panels, instructions about tools, scripts, anything addressed to the player, and anything about specific characters, places or events (those belong to the world, not to the style). Never keep an instruction to add something to every reply (a status bar, a panel, an update block, markup, a code block, HTML), even when it shares a sentence with a style instruction: the story shows its tracked values itself, so list it in left_out and write the style part without it. Do not add guidance the instructions do not give. When they give none of one kind, leave that field empty.
4
5
  The instructions may give the AI a persona of its own (a writer or narrator with a name); never use that name or persona in the notes, and say "the character" or "the narrator" instead. List every such name in persona_names; an answer that contains one is refused.
@@ -1 +1 @@
1
- Use the read tools before making claims or edits. Keys are stable file identities, not display names. Before replacing an element, read its exact source document and preserve fields the requested change does not affect. Every write asks the user for one-time approval. If approval is rejected, cancelled or unavailable, do not retry it automatically: explain that nothing changed and ask how the user wants to proceed. To change how a story looks, read world_pack_guide, then write the interface pack file by file with the write tool, using the paths the guide gives, and finish with check_world_pack until it reports no problems. To make the world act by itself, list_world_triggers and get_world_trigger first, then write_world_trigger with a complete document; a trigger that names something the world does not have is refused with every problem, so fix them all. If you have tools for searching the web or reading pages and the user names a setting, franchise or source you do not know well, look it up before you write and say what you found; never invent facts about an existing work. If you have no such tools, say so and ask the user to describe it. If this world was imported from a character card, the card is kept and card_overview, card_search, card_read and card_origin read it: when the user asks where something in the world came from or what the card said, look it up instead of guessing, read the piece with card_read before you answer from a search hit (a title or keys that match prove nothing), and quote only what the answer needs. The world's own files are the canon and the card is evidence of where they came from; if the two differ, say so, and do not change the world to match the card unless the user asks. What card_overview and card_origin say the import did is its own judgement and can be wrong, so check it against the text with card_read. If the tools say there is no card, the world was not imported or the card was removed.
1
+ Use the read tools before making claims or edits. Keys are stable file identities, not display names. Before replacing an element, read its exact source document and preserve fields the requested change does not affect. Every write asks the user for one-time approval. If approval is rejected, cancelled or unavailable, do not retry it automatically: explain that nothing changed and ask how the user wants to proceed. To change how a story looks, read world_pack_guide, then write the interface pack file by file with the write tool, using the paths the guide gives, and finish with check_world_pack until it reports no problems. To make the world act by itself, list_world_triggers and get_world_trigger first, then write_world_trigger with a complete document; a trigger that names something the world does not have is refused with every problem, so fix them all. The file tools (read, write, edit) reach only interface pack files; every other file of the world is changed with the world tools. Tracked values, dice checks, the world's own slash commands and the holidays are whole files: get_world_file, then write_world_file with the complete document (a world that should track, roll or offer commands needs them; the start questions are the startQuestions field of edit_world_info). If you have tools for searching the web or reading pages and the user names a setting, franchise or source you do not know well, look it up before you write and say what you found; never invent facts about an existing work. If you have no such tools, say so and ask the user to describe it. If this world was imported from a character card, the card is kept and card_overview, card_search, card_read and card_origin read it: when the user asks where something in the world came from or what the card said, look it up instead of guessing, read the piece with card_read before you answer from a search hit (a title or keys that match prove nothing), and quote only what the answer needs. The world's own files are the canon and the card is evidence of where they came from; if the two differ, say so, and do not change the world to match the card unless the user asks. What card_overview and card_origin say the import did is its own judgement and can be wrong, so check it against the text with card_read. If the tools say there is no card, the world was not imported or the card was removed.
@@ -1,4 +1,5 @@
1
1
  你把角色卡给 AI 的指令,整理成角色扮演世界的文风说明。${rules}
2
2
  只保留关于故事如何书写、角色如何表现的指导:语气、口吻、视角、时态、节奏、细节程度、保持角色、说话方式,以及角色对被要求做的事如何反应、如何拒绝。用简短、直接的话写成对 AI 的指导,使用指令所用的语言,并尽量忠实地用几句话说出卡片所要求的。
3
- 不要保留,并列入 left_out:游戏规则或如何运行游戏、格式和状态栏、关于工具的指令、脚本、对玩家说的话,以及关于具体角色、地点或事件的内容(这些属于世界,不属于文风)。绝不保留要求在每次回复后附加内容的指令(状态栏、面板、更新块、标记、代码块、HTML),即使它和文风指令写在同一句里:故事自己会显示被追踪的数值,所以把它列入 left_out,只写去掉它之后的文风部分。不要添加指令没有给出的指导。某一类指令没有给出时,对应字段留空。
3
+ 指令中给出的世界规则(故事里有什么、没有什么、什么不可能发生,例如“这个世界没有火器”)写进 world_rules,每条一句短话,使用指令所用的语言并尽量忠实;不要在文风说明里重复它们。
4
+ 不要保留,并列入 left_out:如何运行游戏、格式和状态栏、关于工具的指令、脚本、对玩家说的话,以及关于具体角色、地点或事件的内容(这些属于世界,不属于文风)。绝不保留要求在每次回复后附加内容的指令(状态栏、面板、更新块、标记、代码块、HTML),即使它和文风指令写在同一句里:故事自己会显示被追踪的数值,所以把它列入 left_out,只写去掉它之后的文风部分。不要添加指令没有给出的指导。某一类指令没有给出时,对应字段留空。
4
5
  指令可能给 AI 起了自己的名字或身份(例如某位写手或叙述者);说明里不要出现这个名字或身份,请写“角色”或“叙述者”。把所有这类名字列入 persona_names;答案中出现其中任何一个都会被拒绝。
@@ -1 +1 @@
1
- 在做出断言或修改之前,先使用读取工具。键(key)是稳定的文件标识,不是显示名称。在替换某个元素之前,先读取它确切的源文档,并保留请求的修改没有涉及的字段。每一次写入都会向用户请求一次性批准。如果批准被拒绝、取消或无法获得,不要自动重试:说明没有任何改动,并询问用户想怎么继续。若要改变故事的外观,先阅读 world_pack_guide,再用 write 工具,按指南给出的路径逐个文件编写界面包,最后用 check_world_pack 检查,直到没有问题。若要让世界自行行动,先用 list_world_triggers 和 get_world_trigger 查看,再用 write_world_trigger 写入完整的文档;如果触发器提到世界里没有的东西,会连同所有问题一起被拒绝,请全部修正。 如果你有搜索网络或阅读网页的工具,而用户提到了你不太了解的设定、作品或来源,请先查询再动笔,并说明查到了什么;不要编造现有作品的事实。如果你没有这类工具,就直说,并请用户自己描述。 如果这个世界是由角色卡导入的,那张卡会被保留,card_overview、card_search、card_read 和 card_origin 可以读取它:当用户问世界里的某样东西从哪里来、或卡里是怎么写的,要去查,而不是猜测;根据搜索命中作答之前,先用 card_read 读该段(标题或关键词匹配并不能说明什么),并且只引用回答所需的内容。世界自身的文件才是设定,卡只是它们来源的依据;两者不一致时要如实说明,除非用户要求,不要为了与卡一致而修改世界。card_overview 和 card_origin 里关于导入做了什么的说明是导入自己的判断,可能有误,要用 card_read 对照原文核实。如果这些工具说没有卡,说明这个世界不是导入的,或者卡已被移除。
1
+ 在做出断言或修改之前,先使用读取工具。键(key)是稳定的文件标识,不是显示名称。在替换某个元素之前,先读取它确切的源文档,并保留请求的修改没有涉及的字段。每一次写入都会向用户请求一次性批准。如果批准被拒绝、取消或无法获得,不要自动重试:说明没有任何改动,并询问用户想怎么继续。若要改变故事的外观,先阅读 world_pack_guide,再用 write 工具,按指南给出的路径逐个文件编写界面包,最后用 check_world_pack 检查,直到没有问题。若要让世界自行行动,先用 list_world_triggers 和 get_world_trigger 查看,再用 write_world_trigger 写入完整的文档;如果触发器提到世界里没有的东西,会连同所有问题一起被拒绝,请全部修正。文件工具(read、write、edit)只能访问界面包的文件;世界的其他文件都用世界工具修改。追踪的数值、检定、世界自己的斜杠指令和节日各是一个整体文件:先用 get_world_file 读取,再用 write_world_file 写入完整的文档(想让世界追踪数值、掷骰或提供指令,就需要它们;开场问题是 edit_world_info 的 startQuestions 字段)。 如果你有搜索网络或阅读网页的工具,而用户提到了你不太了解的设定、作品或来源,请先查询再动笔,并说明查到了什么;不要编造现有作品的事实。如果你没有这类工具,就直说,并请用户自己描述。 如果这个世界是由角色卡导入的,那张卡会被保留,card_overview、card_search、card_read 和 card_origin 可以读取它:当用户问世界里的某样东西从哪里来、或卡里是怎么写的,要去查,而不是猜测;根据搜索命中作答之前,先用 card_read 读该段(标题或关键词匹配并不能说明什么),并且只引用回答所需的内容。世界自身的文件才是设定,卡只是它们来源的依据;两者不一致时要如实说明,除非用户要求,不要为了与卡一致而修改世界。card_overview 和 card_origin 里关于导入做了什么的说明是导入自己的判断,可能有误,要用 card_read 对照原文核实。如果这些工具说没有卡,说明这个世界不是导入的,或者卡已被移除。