From a3d777fc974ae8effb978b9518d7c6c6c8c55a2c Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Fri, 15 Dec 2023 02:17:37 +0000 Subject: Deployed 5cf3a4a5 to dev with MkDocs 1.5.3 and mike 2.0.0 --- dev/404.html | 2 +- dev/API/index.html | 2 +- dev/CLI/index.html | 4 ++-- dev/Core/index.html | 4 ++-- dev/Help/PythonSkill/index.html | 2 +- dev/Help/TermList/index.html | 2 +- dev/Help/emoji/index.html | 2 +- dev/RulePackage/Write/prepare/index.html | 2 +- dev/RulePackage/Write/python/index.html | 2 +- dev/RulePackage/Write/write/index.html | 2 +- dev/RulePackage/getStart/attribute/index.html | 2 +- dev/RulePackage/getStart/class/index.html | 2 +- dev/RulePackage/getStart/getDeeper/Module/index.html | 2 +- dev/RulePackage/getStart/getDeeper/Package/index.html | 2 +- dev/RulePackage/getStart/getDeeper/object/index.html | 2 +- dev/RulePackage/getStart/method/index.html | 2 +- dev/RulePackage/intro/index.html | 4 ++-- dev/RulePackage/skill/fstring/index.html | 2 +- dev/RulePackage/skill/index.html | 2 +- dev/Standard/Term/DefaultDice/_counts/index.html | 2 +- dev/Standard/Term/DefaultDice/_sides/index.html | 2 +- dev/Standard/Term/DefaultDice/index.html | 2 +- dev/Standard/Term/PlayerCard/index.html | 2 +- dev/Standard/Term/check/ability/index.html | 2 +- dev/Standard/Term/check/index.html | 2 +- dev/Standard/Term/duration/campaign/index.html | 2 +- dev/Standard/Term/duration/index.html | 2 +- dev/Standard/Term/duration/module/index.html | 2 +- dev/Standard/Term/duration/sene/index.html | 2 +- dev/Standard/Term/scenario/index.html | 2 +- dev/Standard/Term/setting/index.html | 2 +- dev/Standard/what-is-rule-package/index.html | 4 ++-- dev/Standard/what-is-standard/index.html | 2 +- dev/Standard/why-rule-package/index.html | 2 +- .../index.html" | 4 ++-- dev/blog/archive/2023/index.html | 2 +- dev/blog/category/rules/index.html | 2 +- dev/blog/index.html | 2 +- dev/changelog/index.html | 2 +- dev/index.html | 2 +- dev/sitemap.xml.gz | Bin 127 -> 127 bytes 41 files changed, 45 insertions(+), 45 deletions(-) (limited to 'dev') diff --git a/dev/404.html b/dev/404.html index 18930347..2df6ad4b 100644 --- a/dev/404.html +++ b/dev/404.html @@ -1 +1 @@ - infini 核心文档

404 - Not found

\ No newline at end of file + Infini 核心文档

404 - Not found

\ No newline at end of file diff --git a/dev/API/index.html b/dev/API/index.html index 54ff136e..62559af6 100644 --- a/dev/API/index.html +++ b/dev/API/index.html @@ -1 +1 @@ - API Reference - infini 核心文档

API Reference

\ No newline at end of file + API Reference - Infini 核心文档

API Reference

\ No newline at end of file diff --git a/dev/CLI/index.html b/dev/CLI/index.html index 7c7d1e68..6987b074 100644 --- a/dev/CLI/index.html +++ b/dev/CLI/index.html @@ -1,4 +1,4 @@ - CLI Reference - infini 核心文档

CLI Reference

```python exec="1" idprefix="" import argparse import re from infini import Cli

parser = Cli().parser

MONOSPACED = ("pyproject.toml", "pdm.lock", ".pdm-python", ":pre", ":post", ":all")

def clean_help(help: str) -> str: # Make dunders monospaced avoiding italic markdown rendering help = re.sub(r"([\w\d_]+)", r"__\1__", help) # Make env vars monospaced help = re.sub(r"env var: ([A-Z_]+)", r"env var: \1", help) for monospaced in MONOSPACED: help = re.sub(rf"\s(['\"]?{monospaced}['\"]?)", f"{monospaced}", help) return help

def render_parser( parser: argparse.ArgumentParser, title: str, heading_level: int = 2 ) -> str: """Render the parser help documents as a string.""" result = [f"{'#' * heading_level} {title}\n"] if parser.description and title != "infini": result.append("> " + parser.description + "\n")

 1
+ CLI Reference - Infini 核心文档     
 
 
 
  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
CLI Reference
 
```python exec="1" idprefix="" import argparse import re from infini import Cli
 
parser = Cli().parser
 
MONOSPACED = ("pyproject.toml", "pdm.lock", ".pdm-python", ":pre", ":post", ":all")
 
def clean_help(help: str) -> str: # Make dunders monospaced avoiding italic markdown rendering help = re.sub(r"([\w\d_]+)", r"__\1__", help) # Make env vars monospaced help = re.sub(r"env var: ([A-Z_]+)", r"env var: \1", help) for monospaced in MONOSPACED: help = re.sub(rf"\s(['\"]?{monospaced}['\"]?)", f"{monospaced}", help) return help
 
def render_parser( parser: argparse.ArgumentParser, title: str, heading_level: int = 2 ) -> str: """Render the parser help documents as a string.""" result = [f"{'#' * heading_level} {title}\n"] if parser.description and title != "infini": result.append("> " + parser.description + "\n")
 
 1
  2
  3
  4
@@ -59,4 +59,4 @@
     result.append("")
 
 return "\n".join(result)
-
 
print(render_parser(parser, "infini")) ```
  
 
   
  
  
 
 
 
 
          
\ No newline at end of file
+

print(render_parser(parser, "infini")) ```

\ No newline at end of file diff --git a/dev/Core/index.html b/dev/Core/index.html index 3cf2384b..6cd872b6 100644 --- a/dev/Core/index.html +++ b/dev/Core/index.html @@ -1,4 +1,4 @@ - 核心概览 - infini 核心文档
跳转至

infini'水系核心

🎁 Getting⚓

  1. 安装库

在命令行输入。

1
+ 核心概览 - Infini 核心文档      
 
  
  
 
  
 
  
 
 
  
 
 
 
 
       
infini'水系核心
 
          
 
🎁 Getting⚓
 
     
  1. 安装库
    2.  
 
在命令行输入。
 
1
 2
 3
 4
@@ -19,4 +19,4 @@
 
 class Myrule(Rule):
   """自设规则包，继承 Rule 基类"""
-
 
     
  1. 合理修改你的 config.toml 配置文件，完成注册!
    2.  
 
📄 License⚓
 
MIT © 2023-PRESENT 简律纯
  
 
   
  
  
 
 
 
 
          
\ No newline at end of file
+
  1. 合理修改你的 config.toml 配置文件，完成注册!

📄 License⚓

MIT © 2023-PRESENT 简律纯

\ No newline at end of file diff --git a/dev/Help/PythonSkill/index.html b/dev/Help/PythonSkill/index.html index 5fcf4bf3..d791c255 100644 --- a/dev/Help/PythonSkill/index.html +++ b/dev/Help/PythonSkill/index.html @@ -1 +1 @@ - Python 技巧 - infini 核心文档

Python 技巧

\ No newline at end of file + Python 技巧 - Infini 核心文档

Python 技巧

\ No newline at end of file diff --git a/dev/Help/TermList/index.html b/dev/Help/TermList/index.html index 7be178b6..56dbadde 100644 --- a/dev/Help/TermList/index.html +++ b/dev/Help/TermList/index.html @@ -1 +1 @@ - 术语表一览 - infini 核心文档
跳转至

术语表一览

移步正式术语⚓

\ No newline at end of file + 术语表一览 - Infini 核心文档
跳转至

术语表一览

移步正式术语⚓

\ No newline at end of file diff --git a/dev/Help/emoji/index.html b/dev/Help/emoji/index.html index 71dce85f..3a112be9 100644 --- a/dev/Help/emoji/index.html +++ b/dev/Help/emoji/index.html @@ -1 +1 @@ - 图标、注释说明 - infini 核心文档
跳转至

图标、图例、注释说明

目录树、侧边栏图标⚓

这些图标将会出现在页面左侧的 navigation 与文章右侧的 toc 当中。

在 release 版本中 不推荐使用 但是 仍然有效 的功能、特性。并且在 latest 版本中已经完全废弃1。

在上一个 release 版本作为实验功能或作为扩展特性但是核心本体并未支持的功能、特性，于 latest 版本被引入。

存在于当前 dev 版本中但是未在 latest 版本中加入的功能、特性。

在支持 latest 或 dev 或 特定 release 版本的插件扩展中存在此特性的可行性方案。

抽象概念⚓

这些图标会出现在文章内容中作为抽象概念的具体表达，用于迁移记忆。

以下是图标应用举例:

  • [人物背景]: 生于银河纪元11988年，卒于银河纪元12069年。他的卒年后来被确定为基地纪元元年。他是一位年轻有为的数学家，中等个子，长相俊朗。他曾经担任川陀大学数学系主任，是第一帝国克里昂一世皇帝的御前首相，川陀大学心理史学系荣誉教授，心理史学研究计划主持人、银河百科全书执行编辑。他是心理史学创始人之一（另一位是雨果·阿玛瑞尔），同时也是基地创始人。他还被认为是第二基地第一任首席发言者，后来也成了基地的传奇英雄。

注释说明⚓

  1. 具体还要看下一个大版本的文档如何编写。 ↩

\ No newline at end of file + 图标、注释说明 - Infini 核心文档
跳转至

图标、图例、注释说明

目录树、侧边栏图标⚓

这些图标将会出现在页面左侧的 navigation 与文章右侧的 toc 当中。

在 release 版本中 不推荐使用 但是 仍然有效 的功能、特性。并且在 latest 版本中已经完全废弃1。

在上一个 release 版本作为实验功能或作为扩展特性但是核心本体并未支持的功能、特性，于 latest 版本被引入。

存在于当前 dev 版本中但是未在 latest 版本中加入的功能、特性。

在支持 latest 或 dev 或 特定 release 版本的插件扩展中存在此特性的可行性方案。

抽象概念⚓

这些图标会出现在文章内容中作为抽象概念的具体表达，用于迁移记忆。

以下是图标应用举例:

  • [人物背景]: 生于银河纪元11988年，卒于银河纪元12069年。他的卒年后来被确定为基地纪元元年。他是一位年轻有为的数学家，中等个子，长相俊朗。他曾经担任川陀大学数学系主任，是第一帝国克里昂一世皇帝的御前首相，川陀大学心理史学系荣誉教授，心理史学研究计划主持人、银河百科全书执行编辑。他是心理史学创始人之一（另一位是雨果·阿玛瑞尔），同时也是基地创始人。他还被认为是第二基地第一任首席发言者，后来也成了基地的传奇英雄。

注释说明⚓

  1. 具体还要看下一个大版本的文档如何编写。 ↩

\ No newline at end of file diff --git a/dev/RulePackage/Write/prepare/index.html b/dev/RulePackage/Write/prepare/index.html index 1797e604..e5fcf545 100644 --- a/dev/RulePackage/Write/prepare/index.html +++ b/dev/RulePackage/Write/prepare/index.html @@ -1 +1 @@ - 准备规则书 - infini 核心文档

准备规则书

\ No newline at end of file + 准备规则书 - Infini 核心文档

准备规则书

\ No newline at end of file diff --git a/dev/RulePackage/Write/python/index.html b/dev/RulePackage/Write/python/index.html index 52b59e67..a943a21f 100644 --- a/dev/RulePackage/Write/python/index.html +++ b/dev/RulePackage/Write/python/index.html @@ -1 +1 @@ - 了解Python - infini 核心文档

了解Python

\ No newline at end of file + 了解Python - Infini 核心文档

了解Python

\ No newline at end of file diff --git a/dev/RulePackage/Write/write/index.html b/dev/RulePackage/Write/write/index.html index 02f4f94a..66036cc5 100644 --- a/dev/RulePackage/Write/write/index.html +++ b/dev/RulePackage/Write/write/index.html @@ -1 +1 @@ - 编写规则包 - infini 核心文档

编写规则包

\ No newline at end of file + 编写规则包 - Infini 核心文档

编写规则包

\ No newline at end of file diff --git a/dev/RulePackage/getStart/attribute/index.html b/dev/RulePackage/getStart/attribute/index.html index 4fb36ad5..9d252e15 100644 --- a/dev/RulePackage/getStart/attribute/index.html +++ b/dev/RulePackage/getStart/attribute/index.html @@ -1 +1 @@ - attribute 属性 - infini 核心文档

属性

Info

关联到一个对象的值，通常使用点号表达式按名称来引用。 举例来说，如果对象 o 具有属性 a 则可以用 o.a 来引用它。

如果对象允许，将未被定义为 标识符和关键字 的非标识名称用作一个对象的属性也是可以的，例如使用 setattr()。 这样的属性将无法使用点号表达式来访问，而是必须通过 getattr() 来获取。

\ No newline at end of file + attribute 属性 - Infini 核心文档

属性

Info

关联到一个对象的值，通常使用点号表达式按名称来引用。 举例来说，如果对象 o 具有属性 a 则可以用 o.a 来引用它。

如果对象允许，将未被定义为 标识符和关键字 的非标识名称用作一个对象的属性也是可以的，例如使用 setattr()。 这样的属性将无法使用点号表达式来访问，而是必须通过 getattr() 来获取。

\ No newline at end of file diff --git a/dev/RulePackage/getStart/class/index.html b/dev/RulePackage/getStart/class/index.html index 23316aea..d1f5ce85 100644 --- a/dev/RulePackage/getStart/class/index.html +++ b/dev/RulePackage/getStart/class/index.html @@ -1 +1 @@ - class 类 - infini 核心文档

类

Info

用来创建用户定义对象的模板。类定义通常包含对该类的实例进行操作的方法定义。

\ No newline at end of file + class 类 - Infini 核心文档

类

Info

用来创建用户定义对象的模板。类定义通常包含对该类的实例进行操作的方法定义。

\ No newline at end of file diff --git a/dev/RulePackage/getStart/getDeeper/Module/index.html b/dev/RulePackage/getStart/getDeeper/Module/index.html index 9b55ef3e..cafb180c 100644 --- a/dev/RulePackage/getStart/getDeeper/Module/index.html +++ b/dev/RulePackage/getStart/getDeeper/Module/index.html @@ -1 +1 @@ - Module 模块 - infini 核心文档

模块

Info

此对象是 Python 代码的一种组织单位。各模块具有独立的命名空间，可包含任意 Python 对象。模块可通过 importing 操作被加载到 Python 中。

另见 package。

\ No newline at end of file + Module 模块 - Infini 核心文档

模块

Info

此对象是 Python 代码的一种组织单位。各模块具有独立的命名空间，可包含任意 Python 对象。模块可通过 importing 操作被加载到 Python 中。

另见 package。

\ No newline at end of file diff --git a/dev/RulePackage/getStart/getDeeper/Package/index.html b/dev/RulePackage/getStart/getDeeper/Package/index.html index 93b043d6..d48a502b 100644 --- a/dev/RulePackage/getStart/getDeeper/Package/index.html +++ b/dev/RulePackage/getStart/getDeeper/Package/index.html @@ -1 +1 @@ - Package 包 - infini 核心文档
\ No newline at end of file + Package 包 - Infini 核心文档
\ No newline at end of file diff --git a/dev/RulePackage/getStart/getDeeper/object/index.html b/dev/RulePackage/getStart/getDeeper/object/index.html index 1d56d258..ebc943e9 100644 --- a/dev/RulePackage/getStart/getDeeper/object/index.html +++ b/dev/RulePackage/getStart/getDeeper/object/index.html @@ -1 +1 @@ - object 对象 - infini 核心文档

对象

Info

任何具有状态（属性或值）以及预定义行为（方法）的数据。object 也是任何 new-style class 的最顶层基类名。

\ No newline at end of file + object 对象 - Infini 核心文档

对象

Info

任何具有状态（属性或值）以及预定义行为（方法）的数据。object 也是任何 new-style class 的最顶层基类名。

\ No newline at end of file diff --git a/dev/RulePackage/getStart/method/index.html b/dev/RulePackage/getStart/method/index.html index 8acbad66..360e235d 100644 --- a/dev/RulePackage/getStart/method/index.html +++ b/dev/RulePackage/getStart/method/index.html @@ -1 +1 @@ - method 方法 - infini 核心文档

方法

Info

在类内部定义的函数。如果作为该类的实例的一个属性来调用，方法将会获取实例对象作为其第一个 argument (通常命名为 self)。参见 function 和 nested scope。

\ No newline at end of file + method 方法 - Infini 核心文档

方法

Info

在类内部定义的函数。如果作为该类的实例的一个属性来调用，方法将会获取实例对象作为其第一个 argument (通常命名为 self)。参见 function 和 nested scope。

\ No newline at end of file diff --git a/dev/RulePackage/intro/index.html b/dev/RulePackage/intro/index.html index d863b875..0051a06d 100644 --- a/dev/RulePackage/intro/index.html +++ b/dev/RulePackage/intro/index.html @@ -1,3 +1,3 @@ - 概述 - infini 核心文档
跳转至

概述

Abstract

此章节涉及到真正的 Python 规范问题，因此请认真阅读并多加练习，方能写出漂亮的代码。

安装规则包⚓

水系规则包可以通过 pip Pyhton 包管理工具直接下载，但是为了方便，我们推荐以下两个安装方案。

1
pdm install MyRule
+ 概述 - Infini 核心文档      
 
  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
概述
 
 
Abstract
 
此章节涉及到真正的 Python 规范问题，因此请认真阅读并多加练习，方能写出漂亮的代码。
 
 
安装规则包⚓
 
水系规则包可以通过 pip Pyhton 包管理工具直接下载，但是为了方便，我们推荐以下两个安装方案。
 
 
 
 
1
pdm install MyRule
 
 
如果你使用pdm管理自己的规则包或开启自己的水系骰子，那么非常推荐使用这种方案来集成形如 infini-Rule-The_Pool这般包名的规则。
 
 
 
1
hrc install MyRule
-
 
一般来说推荐使用hrc管理器来安装和调试规则包。 (1)
 
     
  1. 这样会无视虚拟环境规则而直接找到当前使用的文件路径，而不需要像pdm那样只能用在pdm本身创建的虚拟环境内了。
    2.  
 
 
 
 
HRC管理器的原理是使用pip获取包后cp到当前所指定的目录(或者默认目录)。对于不熟悉命令行的用户来说，一个webui或许是更适合的方案。
 
编写规则包⚓
 
要编写规则包，需要懂得Python相关的知识以及一些计算机常识。在接下来的好几个章节里你将会被一步一引导学习如何制作一个规则包。
  
 
   
  
  
 
 
 
 
          
\ No newline at end of file
+

一般来说推荐使用hrc管理器来安装和调试规则包。 (1)

  1. 这样会无视虚拟环境规则而直接找到当前使用的文件路径，而不需要像pdm那样只能用在pdm本身创建的虚拟环境内了。

HRC管理器的原理是使用pip获取包后cp到当前所指定的目录(或者默认目录)。对于不熟悉命令行的用户来说，一个webui或许是更适合的方案。

编写规则包⚓

要编写规则包，需要懂得Python相关的知识以及一些计算机常识。在接下来的好几个章节里你将会被一步一引导学习如何制作一个规则包。

\ No newline at end of file diff --git a/dev/RulePackage/skill/fstring/index.html b/dev/RulePackage/skill/fstring/index.html index 63dfb642..8ab3f791 100644 --- a/dev/RulePackage/skill/fstring/index.html +++ b/dev/RulePackage/skill/fstring/index.html @@ -1 +1 @@ - 善用语法糖 - infini 核心文档
\ No newline at end of file + 善用语法糖 - Infini 核心文档
\ No newline at end of file diff --git a/dev/RulePackage/skill/index.html b/dev/RulePackage/skill/index.html index d944034a..c831a676 100644 --- a/dev/RulePackage/skill/index.html +++ b/dev/RulePackage/skill/index.html @@ -1 +1 @@ - Index - infini 核心文档

Index

\ No newline at end of file + Index - Infini 核心文档

Index

\ No newline at end of file diff --git a/dev/Standard/Term/DefaultDice/_counts/index.html b/dev/Standard/Term/DefaultDice/_counts/index.html index 110ef8f1..7e61e8a6 100644 --- a/dev/Standard/Term/DefaultDice/_counts/index.html +++ b/dev/Standard/Term/DefaultDice/_counts/index.html @@ -1 +1 @@ - _counts 骰子个数 - infini 核心文档
跳转至

_counts 骰子个数

Tip

这是一个必须的值，根据不同规则书的要求设置相对应的值

属性说明⚓

用于规定默认投掷时骰子的个数

\ No newline at end of file + _counts 骰子个数 - Infini 核心文档
跳转至

_counts 骰子个数

Tip

这是一个必须的值，根据不同规则书的要求设置相对应的值

属性说明⚓

用于规定默认投掷时骰子的个数

\ No newline at end of file diff --git a/dev/Standard/Term/DefaultDice/_sides/index.html b/dev/Standard/Term/DefaultDice/_sides/index.html index 6ae129a6..5e8cb101 100644 --- a/dev/Standard/Term/DefaultDice/_sides/index.html +++ b/dev/Standard/Term/DefaultDice/_sides/index.html @@ -1 +1 @@ - _sides 骰子面数 - infini 核心文档
跳转至

_sides 骰子面数

属性说明⚓

用于规定默认投掷时骰子的面数

\ No newline at end of file + _sides 骰子面数 - Infini 核心文档
跳转至

_sides 骰子面数

属性说明⚓

用于规定默认投掷时骰子的面数

\ No newline at end of file diff --git a/dev/Standard/Term/DefaultDice/index.html b/dev/Standard/Term/DefaultDice/index.html index f7ee3a0d..a1d1c405 100644 --- a/dev/Standard/Term/DefaultDice/index.html +++ b/dev/Standard/Term/DefaultDice/index.html @@ -1 +1 @@ - DefaultDice 默认骰子 - infini 核心文档
跳转至

DefaultDice 默认骰子

Tip

这是一个必须的类，根据不同规则书的要求设置相对应的值

类说明⚓

用于规定默认投掷时骰子的各种属性，例如默认骰子数量，面数

\ No newline at end of file + DefaultDice 默认骰子 - Infini 核心文档
跳转至

DefaultDice 默认骰子

Tip

这是一个必须的类，根据不同规则书的要求设置相对应的值

类说明⚓

用于规定默认投掷时骰子的各种属性，例如默认骰子数量，面数

\ No newline at end of file diff --git a/dev/Standard/Term/PlayerCard/index.html b/dev/Standard/Term/PlayerCard/index.html index e60d0b4a..bd8e7005 100644 --- a/dev/Standard/Term/PlayerCard/index.html +++ b/dev/Standard/Term/PlayerCard/index.html @@ -1 +1 @@ - PlayerCard 人物卡 - infini 核心文档
跳转至

PlayerCard 人物卡

Tip

这是一个可选实现但是{建议尽量必须实现}的方法，主要表现在规则书正是检定方法不同而有所不同上。

类说明⚓

用于规定人物卡的格式，包括人物属性，属性之间的计算关系等

\ No newline at end of file + PlayerCard 人物卡 - Infini 核心文档
跳转至

PlayerCard 人物卡

Tip

这是一个可选实现但是{建议尽量必须实现}的方法，主要表现在规则书正是检定方法不同而有所不同上。

类说明⚓

用于规定人物卡的格式，包括人物属性，属性之间的计算关系等

\ No newline at end of file diff --git a/dev/Standard/Term/check/ability/index.html b/dev/Standard/Term/check/ability/index.html index cdfbd38c..e0f21cf4 100644 --- a/dev/Standard/Term/check/ability/index.html +++ b/dev/Standard/Term/check/ability/index.html @@ -1 +1 @@ - ability 检定 - infini 核心文档
\ No newline at end of file + ability 检定 - Infini 核心文档
\ No newline at end of file diff --git a/dev/Standard/Term/check/index.html b/dev/Standard/Term/check/index.html index 7b3476c7..51e8faf4 100644 --- a/dev/Standard/Term/check/index.html +++ b/dev/Standard/Term/check/index.html @@ -1 +1 @@ - check 检定 - infini 核心文档
跳转至

check 检定

Tip

这是一个可选实现但是{建议尽量必须实现}的方法，主要表现在规则书正是检定方法不同而有所不同上。

方法说明⚓

使用check或者ability方法, 必须对检定结果设定一个完整的输出判定范围。

检定结果表⚓

如方法所言，你必须为检定的结果设计一个完整的输出判定范围，因此你需要严格并且合理的分配划分界限，保证所有情况都在允许范围内有一个类似”成功””失败”的输出。

\ No newline at end of file + check 检定 - Infini 核心文档
跳转至

check 检定

Tip

这是一个可选实现但是{建议尽量必须实现}的方法，主要表现在规则书正是检定方法不同而有所不同上。

方法说明⚓

使用check或者ability方法, 必须对检定结果设定一个完整的输出判定范围。

检定结果表⚓

如方法所言，你必须为检定的结果设计一个完整的输出判定范围，因此你需要严格并且合理的分配划分界限，保证所有情况都在允许范围内有一个类似”成功””失败”的输出。

\ No newline at end of file diff --git a/dev/Standard/Term/duration/campaign/index.html b/dev/Standard/Term/duration/campaign/index.html index 41c6f3e8..51f7e6ae 100644 --- a/dev/Standard/Term/duration/campaign/index.html +++ b/dev/Standard/Term/duration/campaign/index.html @@ -1 +1 @@ - campaign 战役 - infini 核心文档

campaign 战役

\ No newline at end of file + campaign 战役 - Infini 核心文档

campaign 战役

\ No newline at end of file diff --git a/dev/Standard/Term/duration/index.html b/dev/Standard/Term/duration/index.html index 9574ec01..868db2ed 100644 --- a/dev/Standard/Term/duration/index.html +++ b/dev/Standard/Term/duration/index.html @@ -1 +1 @@ - duration (时长) - infini 核心文档
跳转至
\ No newline at end of file + duration (时长) - Infini 核心文档
跳转至
\ No newline at end of file diff --git a/dev/Standard/Term/duration/module/index.html b/dev/Standard/Term/duration/module/index.html index 97587008..caf043a2 100644 --- a/dev/Standard/Term/duration/module/index.html +++ b/dev/Standard/Term/duration/module/index.html @@ -1 +1 @@ - module 模组 - infini 核心文档

module 模组

\ No newline at end of file + module 模组 - Infini 核心文档

module 模组

\ No newline at end of file diff --git a/dev/Standard/Term/duration/sene/index.html b/dev/Standard/Term/duration/sene/index.html index abd6a535..c1ca9a00 100644 --- a/dev/Standard/Term/duration/sene/index.html +++ b/dev/Standard/Term/duration/sene/index.html @@ -1 +1 @@ - sene 场 - infini 核心文档

sene 场

\ No newline at end of file + sene 场 - Infini 核心文档

sene 场

\ No newline at end of file diff --git a/dev/Standard/Term/scenario/index.html b/dev/Standard/Term/scenario/index.html index 4364e59f..fb5c70dc 100644 --- a/dev/Standard/Term/scenario/index.html +++ b/dev/Standard/Term/scenario/index.html @@ -1 +1 @@ - scenario 剧本 - infini 核心文档

scenario 剧本

\ No newline at end of file + scenario 剧本 - Infini 核心文档

scenario 剧本

\ No newline at end of file diff --git a/dev/Standard/Term/setting/index.html b/dev/Standard/Term/setting/index.html index 7662240e..143b736a 100644 --- a/dev/Standard/Term/setting/index.html +++ b/dev/Standard/Term/setting/index.html @@ -1 +1 @@ - setting 背景 - infini 核心文档

setting 背景

\ No newline at end of file + setting 背景 - Infini 核心文档

setting 背景

\ No newline at end of file diff --git a/dev/Standard/what-is-rule-package/index.html b/dev/Standard/what-is-rule-package/index.html index 6f2f9dba..9ec6d64e 100644 --- a/dev/Standard/what-is-rule-package/index.html +++ b/dev/Standard/what-is-rule-package/index.html @@ -1,4 +1,4 @@ - 什么是规则包？ - infini 核心文档

什么是规则包?

规则包是水系核心用来加载的对象，可以理解为水系核心加载的一个一个规则实例。

规则包更类似于插件的设计，所以规则包也可以是一个Python文件或者一个Python包，但它必须像插件那样继承一个像Plugin这样的类（不然无法读取，我们姑且叫这个类为Rule），以及在Rule的子类里实现一些像handle()或者rule()这样必须实现的方法（也叫函数），而这些必须实现的方法，就是我们要讨论的，一个通用规则包标准就是明确了一个继承自Rule类的子类它本身应该实现什么方法。

举个例子（随便写的，其中一些必须实现的属性或者类名都是不确定的，以后或许会改）：

 1
+ 什么是规则包？ - Infini 核心文档     
 
 
 
  
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
       
什么是规则包?
 
规则包是水系核心用来加载的对象，可以理解为水系核心加载的一个一个规则实例。
 
规则包更类似于插件的设计，所以规则包也可以是一个Python文件或者一个Python包，但它必须像插件那样继承一个像Plugin这样的类（不然无法读取，我们姑且叫这个类为Rule），以及在Rule的子类里实现一些像handle()或者rule()这样必须实现的方法（也叫函数），而这些必须实现的方法，就是我们要讨论的，一个通用规则包标准就是明确了一个继承自Rule类的子类它本身应该实现什么方法。
 
举个例子（随便写的，其中一些必须实现的属性或者类名都是不确定的，以后或许会改）：
 
 1
  2
  3
  4
@@ -45,4 +45,4 @@
             return self.rule.ability.success # 返回大成功时骰主自定义的大成功文本
         else:
             ... # 其他的检定情况
-
 
这样就实现了一个水系规则包，当pl使用检定掷骰指令时就会调用check()方法，如果检定结果数值小于5且大于0那么返回大成功。
 
我们要做的通用规则包标准就是这样一个“到底需要在Rule的子类MyRule里必须实现哪些方法？”的问题。
  
 
   
  
  
 
 
 
 
          
\ No newline at end of file
+

这样就实现了一个水系规则包，当pl使用检定掷骰指令时就会调用check()方法，如果检定结果数值小于5且大于0那么返回大成功。

我们要做的通用规则包标准就是这样一个“到底需要在Rule的子类MyRule里必须实现哪些方法？”的问题。

\ No newline at end of file diff --git a/dev/Standard/what-is-standard/index.html b/dev/Standard/what-is-standard/index.html index e54cdf46..1001591c 100644 --- a/dev/Standard/what-is-standard/index.html +++ b/dev/Standard/what-is-standard/index.html @@ -1 +1 @@ - 什么是通用规则包标准? - infini 核心文档

什么是通用规则包标准?

\ No newline at end of file + 什么是通用规则包标准? - Infini 核心文档

什么是通用规则包标准?

\ No newline at end of file diff --git a/dev/Standard/why-rule-package/index.html b/dev/Standard/why-rule-package/index.html index bdbfbff4..ada4d584 100644 --- a/dev/Standard/why-rule-package/index.html +++ b/dev/Standard/why-rule-package/index.html @@ -1 +1 @@ - 为什么要做规则包? - infini 核心文档

为什么要做规则包?

\ No newline at end of file + 为什么要做规则包? - Infini 核心文档

为什么要做规则包?

\ No newline at end of file diff --git "a/dev/blog/2023/10/07/rule-\345\237\272\347\261\273\345\267\262\347\273\217\346\224\257\346\214\201\346\263\233\345\236\213\344\272\206/index.html" "b/dev/blog/2023/10/07/rule-\345\237\272\347\261\273\345\267\262\347\273\217\346\224\257\346\214\201\346\263\233\345\236\213\344\272\206/index.html" index 5815879f..302680ea 100644 --- "a/dev/blog/2023/10/07/rule-\345\237\272\347\261\273\345\267\262\347\273\217\346\224\257\346\214\201\346\263\233\345\236\213\344\272\206/index.html" +++ "b/dev/blog/2023/10/07/rule-\345\237\272\347\261\273\345\267\262\347\273\217\346\224\257\346\214\201\346\263\233\345\236\213\344\272\206/index.html" @@ -1,5 +1,5 @@ Rule 基类已经支持泛型了 - infini 核心文档
跳转至

Rule 基类已经支持泛型了⚓

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

This article explains how to build a standalone blog with Material for MkDocs. If you want to build a blog alongside your documentation, please refer to the plugin's documentation.

Quick start⚓

Creating a standalone blog⚓

You can bootstrap a new project using the mkdocs executable:

1
mkdocs new .
+">Rule 基类已经支持泛型了 - Infini 核心文档      
 
  
  
 
  
 
  
 
 
  
 
 
 
 
 
 
  
 
 
 
       
Rule 基类已经支持泛型了⚓
 
Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.
 
Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.
  
This article explains how to build a standalone blog with Material for MkDocs. If you want to build a blog alongside your documentation, please refer to the plugin's documentation.
 
Quick start⚓
 
Creating a standalone blog⚓
 
You can bootstrap a new project using the mkdocs executable:
 
1
mkdocs new .
 
 
This will create the following structure:
 
1
 2
 3
@@ -103,4 +103,4 @@
 arcu tincidunt pulvinar. Vestibulum laoreet risus scelerisque porta congue.
 In velit purus, dictum quis neque nec, molestie viverra risus. Nam pellentesque
 tellus id elit ultricies, vel finibus erat cursus.
-
 
     
  1. If you mark a post as a draft, a red marker appears next to the post date on index pages. When the site is built, drafts are not included in the output. This behavior can be changed, e.g. for rendering drafts when building deploy previews.
    2.  
 
When you spin up the live preview server, you should be greeted by your first post! You'll also realize, that archive and category indexes have been automatically generated for you:
 
Blog
 
However, this is just the start. The built-in blog plugin packs a lot of functionality needed in day-to-day blogging. Visit the documentation of the plugin to learn about the following topics:
 
  
 
Additionally, the built-in blog plugin has dozens of configuration options which allow for fine-tuning the output. You can configure post slugs, general behavior and much more.
 
What's next?⚓
 
Getting basic blogging support out the door was quite a challenge – the built-in blog plugin is probably the biggest release this year and already packs a lot of functionality. However, Material for MkDocs is used in many different contexts, which is why we'd expect to iterate, as always.
 
Some ideas already proposed by users:
 
     
  •  
    Blog series: Authors should be able to create so called blog series and assign posts to a blog series using simple identifiers. For each post that is part of a series, a list with links to all other posts should be included in the post's content.
     
    •  
  •  
    Author indexes: Besides archive and category indexes, authors should be able to create per-author indexes, which list all posts linked to an author. Additionally, a profile should be created for each author and linked from posts.
     
    •  
  •  
    Social share buttons: It should be easy to share blog posts via social media or other ways. For this reason, it should be possible to automatically include social sharing buttons with each post.
     
    •  
 
What's still missing from the brand new built-in blog plugin? Feel free to share your ideas in the comments. Together, we can build one of the best modern engines for technical blogging!
  
 
   
  
  
 
 
 
 
          
\ No newline at end of file
+
  1. If you mark a post as a draft, a red marker appears next to the post date on index pages. When the site is built, drafts are not included in the output. This behavior can be changed, e.g. for rendering drafts when building deploy previews.

When you spin up the live preview server, you should be greeted by your first post! You'll also realize, that archive and category indexes have been automatically generated for you:

Blog

However, this is just the start. The built-in blog plugin packs a lot of functionality needed in day-to-day blogging. Visit the documentation of the plugin to learn about the following topics:

Additionally, the built-in blog plugin has dozens of configuration options which allow for fine-tuning the output. You can configure post slugs, general behavior and much more.

What's next?⚓

Getting basic blogging support out the door was quite a challenge – the built-in blog plugin is probably the biggest release this year and already packs a lot of functionality. However, Material for MkDocs is used in many different contexts, which is why we'd expect to iterate, as always.

Some ideas already proposed by users:

  • Blog series: Authors should be able to create so called blog series and assign posts to a blog series using simple identifiers. For each post that is part of a series, a list with links to all other posts should be included in the post's content.

  • Author indexes: Besides archive and category indexes, authors should be able to create per-author indexes, which list all posts linked to an author. Additionally, a profile should be created for each author and linked from posts.

  • Social share buttons: It should be easy to share blog posts via social media or other ways. For this reason, it should be possible to automatically include social sharing buttons with each post.

What's still missing from the brand new built-in blog plugin? Feel free to share your ideas in the comments. Together, we can build one of the best modern engines for technical blogging!

\ No newline at end of file diff --git a/dev/blog/archive/2023/index.html b/dev/blog/archive/2023/index.html index 0e1b6e6c..52e66f26 100644 --- a/dev/blog/archive/2023/index.html +++ b/dev/blog/archive/2023/index.html @@ -1 +1 @@ - 2023 - infini 核心文档
跳转至

2023⚓

  • 分类于 Rules
  • 需要 5 分钟阅读时间

Rule 基类已经支持泛型了

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

\ No newline at end of file + 2023 - Infini 核心文档
跳转至

2023⚓

  • 分类于 Rules
  • 需要 5 分钟阅读时间

Rule 基类已经支持泛型了

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

\ No newline at end of file diff --git a/dev/blog/category/rules/index.html b/dev/blog/category/rules/index.html index 6a12d89d..5c8747c4 100644 --- a/dev/blog/category/rules/index.html +++ b/dev/blog/category/rules/index.html @@ -1 +1 @@ - Rules - infini 核心文档
跳转至

Rules⚓

  • 分类于 Rules
  • 需要 5 分钟阅读时间

Rule 基类已经支持泛型了

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

\ No newline at end of file + Rules - Infini 核心文档
跳转至

Rules⚓

  • 分类于 Rules
  • 需要 5 分钟阅读时间

Rule 基类已经支持泛型了

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

\ No newline at end of file diff --git a/dev/blog/index.html b/dev/blog/index.html index ad62a1a6..d4b901b0 100644 --- a/dev/blog/index.html +++ b/dev/blog/index.html @@ -1 +1 @@ - Blog - infini 核心文档
跳转至

Blog⚓

  • 分类于 Rules
  • 需要 5 分钟阅读时间

Rule 基类已经支持泛型了

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

\ No newline at end of file + Blog - Infini 核心文档
跳转至

Blog⚓

  • 分类于 Rules
  • 需要 5 分钟阅读时间

Rule 基类已经支持泛型了

Hey there! You're looking at our new blog, built with the brand new built-in blog plugin. With this plugin, you can easily build a blog alongside your documentation or standalone.

Proper support for blogging, as requested by many users over the past few years, was something that was desperately missing from Material for MkDocs' feature set. While everybody agreed that blogging support was a blind spot, it was not obvious whether MkDocs could be extended in a way to allow for blogging as we know it from Jekyll and friends. The built-in blog plugin proves that it is, after all, possible to build a blogging engine on top of MkDocs, in order to create a technical blog alongside your documentation, or as the main thing.

\ No newline at end of file diff --git a/dev/changelog/index.html b/dev/changelog/index.html index 03f99be9..6e72de5b 100644 --- a/dev/changelog/index.html +++ b/dev/changelog/index.html @@ -1 +1 @@ - 变更日志 - infini 核心文档
跳转至

变更日志

1.0.5 (2023-10-08)⚓

BREAKING CHANGES⚓

FEATURES⚓

  • Docs: balabla.
  • Rule: 支持泛型。

BUG FIX⚓

  • Docs: balabla.

CHORE⚓

  • Readme: 添加了主页介绍。

1.0.4 (2023-10-07)⚓

FEATURES⚓

  • Docs: 美化 style。
  • Deps: 添加 reportlab 依赖，用于以后的 pdf 生成。

1.0.3 (2023-10-07)⚓

1.0.2 (2023-10-07)⚓

FEATURES⚓

  • Docs: 优化 css 细节。

1.0.1 (2023-10-07)⚓

BUG FIX⚓

  • Docs: 修复 Dev 与 latest 分支的错别字。

0.1.2 (2023-10-07)⚓

同步版本所做的测试。

0.1.1 (2023-10-07)⚓

BUG FIX⚓

  • CLI: 添加命令行参数解析。

0.1.0-rc1 (2023-10-07)⚓

CHORE⚓

  • README: 更新主页介绍的安装指南。

0.1.0 (2023-10-07)⚓

Features⚓

  • CLI 添加两个命令行名称 infini 与 HRC。

0.0.1 (2023-07-04)⚓

Features⚓

  • init: 添加命令行参数解析。
  • Rule: 添加 Rule 基类，实现读取指定文件夹下的 python 脚本或 python 包

BREAKING CHANGE⚓

  • infini: 添加命令行Path。
\ No newline at end of file + 变更日志 - Infini 核心文档
跳转至

变更日志

1.0.5 (2023-10-08)⚓

BREAKING CHANGES⚓

FEATURES⚓

  • Docs: balabla.
  • Rule: 支持泛型。

BUG FIX⚓

  • Docs: balabla.

CHORE⚓

  • Readme: 添加了主页介绍。

1.0.4 (2023-10-07)⚓

FEATURES⚓

  • Docs: 美化 style。
  • Deps: 添加 reportlab 依赖，用于以后的 pdf 生成。

1.0.3 (2023-10-07)⚓

1.0.2 (2023-10-07)⚓

FEATURES⚓

  • Docs: 优化 css 细节。

1.0.1 (2023-10-07)⚓

BUG FIX⚓

  • Docs: 修复 Dev 与 latest 分支的错别字。

0.1.2 (2023-10-07)⚓

同步版本所做的测试。

0.1.1 (2023-10-07)⚓

BUG FIX⚓

  • CLI: 添加命令行参数解析。

0.1.0-rc1 (2023-10-07)⚓

CHORE⚓

  • README: 更新主页介绍的安装指南。

0.1.0 (2023-10-07)⚓

Features⚓

  • CLI 添加两个命令行名称 infini 与 HRC。

0.0.1 (2023-07-04)⚓

Features⚓

  • init: 添加命令行参数解析。
  • Rule: 添加 Rule 基类，实现读取指定文件夹下的 python 脚本或 python 包

BREAKING CHANGE⚓

  • infini: 添加命令行Path。
\ No newline at end of file diff --git a/dev/index.html b/dev/index.html index 424e6fed..1cd52f08 100644 --- a/dev/index.html +++ b/dev/index.html @@ -1 +1 @@ - 水系核心 - infini 核心文档

水系核心

一个基于通用规则包标准的规则包加载器.

快速开始 查看标准
\ No newline at end of file + 水系核心 - Infini 核心文档

水系核心

一个基于通用规则包标准的规则包加载器.

快速开始 查看标准
\ No newline at end of file diff --git a/dev/sitemap.xml.gz b/dev/sitemap.xml.gz index fb95d6b4..31acb01c 100644 Binary files a/dev/sitemap.xml.gz and b/dev/sitemap.xml.gz differ -- cgit v1.2.3-70-g09d2