Skip to content

角色攻略-昼雪#64

Open
Nether-Dream wants to merge 1 commit into
cmyyx:mainfrom
Nether-Dream:main
Open

角色攻略-昼雪#64
Nether-Dream wants to merge 1 commit into
cmyyx:mainfrom
Nether-Dream:main

Conversation

@Nether-Dream

@Nether-Dream Nether-Dream commented May 22, 2026

Copy link
Copy Markdown

Summary by Sourcery

添加新干员「昼雪(snowshine)」的完整游戏数据与攻略内容。

新特性:

  • 将可操控干员「雪昼(snowshine)」加入干员库。
  • 为「雪昼(snowshine)」提供完整的属性、技能、天赋、潜能与晋升材料信息。
  • 为「雪昼(snowshine)」新增详尽的装备搭配、编队思路与实战操作攻略,并注明作者信息。
Original summary in English

Summary by Sourcery

Add the new character '昼雪 (snowshine)' with full gameplay data and guide content.

New Features:

  • Introduce the playable character 雪昼 (snowshine) to the character registry.
  • Provide complete stats, skills, talents, potentials, and promotion materials for 雪昼 (snowshine).
  • Add an in-depth equipment, team composition, and operation guide for 雪昼 (snowshine), including author attributions.

Summary by CodeRabbit

新功能

  • 新增角色"雪橄/昼雪"及其完整游戏数据,包括角色属性、技能、天赋、基建技能、潜能系统和队伍配置建议。

Review Change Stack

@netlify

netlify Bot commented May 22, 2026

Copy link
Copy Markdown

Deploy Preview for endfield-essence-planner ready!

Name Link
🔨 Latest commit f1d1bc6
🔍 Latest deploy log https://app.netlify.com/projects/endfield-essence-planner/deploys/6a1000bda16c530008d6639e
😎 Deploy Preview https://deploy-preview-64--endfield-essence-planner.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@sourcery-ai

sourcery-ai Bot commented May 22, 2026

Copy link
Copy Markdown

审阅者指南

新增可玩角色「昼雪 (snowshine)」,包含完整面板、技能、天赋、晋升素材,以及详细配装 / 策略指南,并在全局角色列表中注册该角色 ID。

文件级变更

Change Details Files
在全局角色注册表中注册新的角色 ID,使该角色与其他角色一同加载。
  • 将 "snowshine" 追加到 characterIds 数组中,以便在迭代时将其加载进 window.characters
data/characters.js
为新角色引入完整数据定义,包括面板、战斗配套、成长素材以及游戏攻略元数据。
  • 定义 snowshine 角色元数据(id、name、rarity、element、weapon type、main/sub abilities、profession 以及基础属性)。
  • 描述所有主动技能(普通攻击、技能、连携技与终结技),并提供包含伤害、治疗、冷却以及其他参数的等级成长表。
  • 定义天赋、基建技能(infrastructure skills)以及潜能升级,并说明其在游戏内的效果。
  • 为精英 1–4 阶指定晋升素材,包括物品名称与数量。
  • 新增一块深度攻略内容,包括推荐装备搭配、分析文本、阵容构筑、实战技巧与署名信息,并按现有攻略 UI 所需结构进行组织。
data/characters/snowshine.js

技巧与命令

与 Sourcery 交互

  • 触发新评审: 在 Pull Request 中评论 @sourcery-ai review
  • 继续讨论: 直接回复 Sourcery 的评审评论。
  • 从评审评论生成 GitHub Issue: 在某条评审评论下回复,请求 Sourcery 基于该评论创建 issue。你也可以直接回复 @sourcery-ai issue,从该评审评论创建 issue。
  • 生成 Pull Request 标题: 在 Pull Request 标题中任意位置写上 @sourcery-ai,即可随时生成标题。也可以在 Pull Request 中评论 @sourcery-ai title 以(重新)生成标题。
  • 生成 Pull Request 摘要: 在 Pull Request 正文中任意位置写上 @sourcery-ai summary,即可在该位置生成 PR 摘要。也可以在 Pull Request 中评论 @sourcery-ai summary 以在任意时间(重新)生成摘要。
  • 生成审阅者指南: 在 Pull Request 中评论 @sourcery-ai guide,随时(重新)生成审阅者指南。
  • 一次性解决所有 Sourcery 评论: 在 Pull Request 中评论 @sourcery-ai resolve,将所有 Sourcery 评论标记为已解决。如果你已经处理完所有评论且不想再看到它们,这会很有用。
  • 撤销所有 Sourcery 评审: 在 Pull Request 中评论 @sourcery-ai dismiss,撤销所有现有的 Sourcery 评审。如果你想从头开始一次新的评审,这尤其有用——别忘了再评论 @sourcery-ai review 以触发新的评审!

自定义你的体验

前往你的 控制面板 以:

  • 启用或禁用评审功能,例如 Sourcery 自动生成的 Pull Request 摘要、审阅者指南等。
  • 更改评审语言。
  • 添加、移除或编辑自定义评审说明。
  • 调整其他评审设置。

获取帮助

Original review guide in English

Reviewer's Guide

Adds a new playable character '昼雪 (snowshine)' including full stats, skills, talents, promotion materials, and a detailed build/strategy guide, and registers the character ID in the global character list.

File-Level Changes

Change Details Files
Register new character ID in the global character registry so the character is loaded with others.
  • Append "snowshine" to the characterIds array so it is iterated and loaded into window.characters
data/characters.js
Introduce full data definition for new character, including stats, combat kit, progression materials, and gameplay guide metadata.
  • Define snowshine character metadata (id, name, rarity, element, weapon type, main/sub abilities, profession, and base stats).
  • Describe all active skills (basic attack, skill, chain skill, and ultimate) with level-scaling tables for damage, healing, cooldowns, and other parameters.
  • Define talents, base (infrastructure) skills, and potential upgrades with their in‑game effects.
  • Specify promotion materials for elite levels 1–4 with item names and quantities.
  • Add an in-depth guide block including recommended equipment loadouts, analysis text, team compositions, operation tips, and attribution info, structured for the existing guide UI.
data/characters/snowshine.js

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented May 22, 2026

Copy link
Copy Markdown
📝 Walkthrough

演练

此PR新增了名为"雪橄"(snowshine)的角色数据。在characters.js中注册了角色ID,并创建了snowshine.js包含该角色的完整属性、技能、装备指南和其他游戏相关数据。

变更

角色数据集成

图层 / 文件 总结
角色ID注册
data/characters.js
在characterIds数组中新增"snowshine"条目,触发后续脚本加载机制生成对应的角色数据路径。
角色数据结构定义
data/characters/snowshine.js
新增完整的snowshine角色数据对象,包含基础属性(strength/agility/intellect/will/attack/hp)、四项技能及其数值表(普通攻击、饱和性防御、极地救援、凛冽寒霜)、天赋、基建技能、潜能、培养材料(elite1~elite4)、以及装备推荐、队伍配置和作战指南等游戏指导信息。

评估代码审查工作量

🎯 2 (Simple) | ⏱️ ~12 分钟

雪橄闪耀新降临,
寒霜绽放冰晶纹,
数据行列整齐排,
战场佳人今入阵。
❄️✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 拉取请求标题「角色攻略-昼雪」清晰准确地反映了主要变更内容,即为新角色「昼雪」(snowshine)添加攻略和数据。
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Nether-Dream Nether-Dream changed the title 干员昼雪攻略和数据撰写 角色攻略-昼雪 May 22, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new character, 'snowshine' (昼雪), including detailed stats, skills, and equipment guides. The review feedback focuses on improving data consistency and code quality by suggesting the use of numeric literals instead of strings for stats, removing redundant whitespace and tabs within strings, and correcting a typo in the character guide notes.

@@ -0,0 +1,702 @@
(function () {
window.characters = window.characters || [];
window.characters.push( {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

此处存在多余的空格,建议清理以符合代码风格。

Suggested change
window.characters.push( {
window.characters.push({

Comment on lines +13 to +18
"strength": "154",
"agility": "104",
"intellect": "93",
"will": "108",
"attack": "297",
"hp": "5495"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

数值类型的属性建议直接使用数字字面量而非字符串,以便于后续逻辑处理并保持数据一致性。

Suggested change
"strength": "154",
"agility": "104",
"intellect": "93",
"will": "108",
"attack": "297",
"hp": "5495"
"strength": 154,
"agility": 104,
"intellect": 93,
"will": 108,
"attack": 297,
"hp": 5495

"name": "普攻第一段倍率",
"values": [
"55%",
"61%\t",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

字符串末尾包含多余的制表符 \t,建议移除。此类问题在文件中多处出现(如第 37, 53, 55, 75, 235, 252 行)。

Suggested change
"61%\t",
"61%",

{
"name": "终点之声",
"icon": "",
"note": "2号位,5星专武 装备同昔日精品",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

备注信息中包含过多的连续空格,建议清理以优化显示效果。

Suggested change
"note": "2号位,5星专武 装备同昔日精品",
"note": "2号位,5星专武装备同昔日精品",

{
"name": "生物辅助接驳器·贰型",
"icon": "",
"note": "提供单一了,不如壹型",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

“提供单一了”疑似错别字,建议修正为“属性较为单一”或“提供单一加成”。

Suggested change
"note": "提供单一了,不如壹型",
"note": "属性较为单一,不如壹型",

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - 我发现了 1 个问题,并留下了一些整体性的反馈:

  • 数据中的若干字符串值(例如技能倍率里的 "61%\t"、治疗数值里的 "182\t" 等)包含多余的制表符;建议将其规范化为单纯的数字/百分比字符串,以避免后续在解析或格式化时出现一些隐蔽的问题。
  • guide.equipRows 配置中,有些 equipment 项是显式的 null,而有些则被省略;请确认这是否与消费这些数据的代码中对装备栏位的处理方式一致,或者在 UI/逻辑期望有统一结构时,将 null 替换为明确的占位对象。
  • 第二行装备中出现了两次 "生物辅助护盾针",并且备注和稀有度都相同;如果你的意图是表示两个相同物品但不同栏位,建议通过额外字段或更清晰的备注来显式说明,以免在渲染或维护这些数据时造成混淆。
给 AI 代理的提示
请根据本次代码审查的评论进行修改:

## 整体评论
- 数据中的若干字符串值(例如技能倍率里的 `"61%\t"`、治疗数值里的 `"182\t"` 等)包含多余的制表符;建议将其规范化为单纯的数字/百分比字符串,以避免后续在解析或格式化时出现一些隐蔽的问题。
-`guide.equipRows` 配置中,有些 `equipment` 项是显式的 `null`,而有些则被省略;请确认这是否与消费这些数据的代码中对装备栏位的处理方式一致,或者在 UI/逻辑期望有统一结构时,将 `null` 替换为明确的占位对象。
- 第二行装备中出现了两次 `"生物辅助护盾针"`,并且备注和稀有度都相同;如果你的意图是表示两个相同物品但不同栏位,建议通过额外字段或更清晰的备注来显式说明,以免在渲染或维护这些数据时造成混淆。

## 单独评论

### 评论 1
<location path="data/characters/snowshine.js" line_range="34-43" />
<code_context>
+                "name": "普攻第一段倍率",
+                "values": [
+                  "55%",
+                  "61%\t",
+                  "66%",
+                  "72%",
+                  "77%\t",
+                  "83%",
+                  "88%",
+                  "94%",
+                  "99%",
+                  "106%",
+                  "114%",
+                  "124%"
+                ]
+              },
</code_context>
<issue_to_address>
**suggestion (bug_risk):** 清理数值字符串中多余的制表符转义序列。

多个 `dataTables` 的值(例如 `"61%\t"``"77%\t"``"0.43\t"`)在末尾包含 `\t`,看起来是无意引入的,如果被直接使用,可能会引发排版或解析问题。请将这些值规范化为纯数值(例如 `"61%"``"182"`)。

建议的修改方式:

```javascript
                  "61%",

```

```javascript
                  "77%",

```

```javascript
                  "0.43"

```

```javascript
                  "182"

```

`data/characters/snowshine.js`(或类似数据文件)中可能还有其它数值字符串同样包含末尾的 `\t`。可以在该文件(以及可选的整个 `data/characters` 目录)中快速搜索 `"\t"`,并用同样方式统一清理这些值。
</issue_to_address>

Sourcery 对开源项目免费——如果你觉得我们的审查有帮助,欢迎分享 ✨
帮我变得更有用!请在每条评论上点 👍 或 👎,我会根据你的反馈改进后续审查。
Original comment in English

Hey - I've found 1 issue, and left some high level feedback:

  • Several string values in the data (e.g. skill multipliers like "61%\t", healing values like "182\t") contain stray tab characters; consider normalizing these to plain numbers/percent strings to avoid subtle parsing or formatting issues downstream.
  • In the guide.equipRows configuration, some equipment entries are literal null while others are omitted; please confirm this matches how the consumer code handles equipment slots, or replace null with explicit placeholder objects if the UI/logic expects a consistent shape.
  • The second equip row lists "生物辅助护盾针" twice with identical notes and rarity; if the intention is to represent two distinct slots of the same item, consider making this explicit via an additional field or clarifying note to avoid confusion when rendering or maintaining this data.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Several string values in the data (e.g. skill multipliers like `"61%\t"`, healing values like `"182\t"`) contain stray tab characters; consider normalizing these to plain numbers/percent strings to avoid subtle parsing or formatting issues downstream.
- In the `guide.equipRows` configuration, some `equipment` entries are literal `null` while others are omitted; please confirm this matches how the consumer code handles equipment slots, or replace `null` with explicit placeholder objects if the UI/logic expects a consistent shape.
- The second equip row lists `"生物辅助护盾针"` twice with identical notes and rarity; if the intention is to represent two distinct slots of the same item, consider making this explicit via an additional field or clarifying note to avoid confusion when rendering or maintaining this data.

## Individual Comments

### Comment 1
<location path="data/characters/snowshine.js" line_range="34-43" />
<code_context>
+                "name": "普攻第一段倍率",
+                "values": [
+                  "55%",
+                  "61%\t",
+                  "66%",
+                  "72%",
+                  "77%\t",
+                  "83%",
+                  "88%",
+                  "94%",
+                  "99%",
+                  "106%",
+                  "114%",
+                  "124%"
+                ]
+              },
</code_context>
<issue_to_address>
**suggestion (bug_risk):** Clean up stray tab escape sequences in numeric strings.

Several `dataTables` values (e.g. `"61%\t"`, `"77%\t"`, `"0.43\t"`) include a trailing `\t` that looks unintentional and could cause layout or parsing issues if used directly. Please normalize these to plain values (e.g. `"61%"`, `"182"`).

Suggested implementation:

```javascript
                  "61%",

```

```javascript
                  "77%",

```

```javascript
                  "0.43"

```

```javascript
                  "182"

```

There may be other numeric strings in `data/characters/snowshine.js` (or similar data files) that also contain trailing `\t`. A quick search for `"\t"` in this file (and optionally the whole `data/characters` directory) would allow you to normalize all such values in the same way.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines +34 to +43
"61%\t",
"66%",
"72%",
"77%\t",
"83%",
"88%",
"94%",
"99%",
"106%",
"114%",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (bug_risk): 清理数值字符串中多余的制表符转义序列。

多个 dataTables 的值(例如 "61%\t""77%\t""0.43\t")在末尾包含 \t,看起来是无意引入的,如果被直接使用,可能会引发排版或解析问题。请将这些值规范化为纯数值(例如 "61%""182")。

建议的修改方式:

                  "61%",
                  "77%",
                  "0.43"
                  "182"

data/characters/snowshine.js(或类似数据文件)中可能还有其它数值字符串同样包含末尾的 \t。可以在该文件(以及可选的整个 data/characters 目录)中快速搜索 "\t",并用同样方式统一清理这些值。

Original comment in English

suggestion (bug_risk): Clean up stray tab escape sequences in numeric strings.

Several dataTables values (e.g. "61%\t", "77%\t", "0.43\t") include a trailing \t that looks unintentional and could cause layout or parsing issues if used directly. Please normalize these to plain values (e.g. "61%", "182").

Suggested implementation:

                  "61%",
                  "77%",
                  "0.43"
                  "182"

There may be other numeric strings in data/characters/snowshine.js (or similar data files) that also contain trailing \t. A quick search for "\t" in this file (and optionally the whole data/characters directory) would allow you to normalize all such values in the same way.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@data/characters/snowshine.js`:
- Line 34: The values array contains numeric/percentage strings with trailing
tab characters (e.g., "61%\t") that can break parsing or comparisons; locate the
values array in the snowshine character definition (the "values" property) and
remove all trailing "\t" characters from each string (including entries at the
referenced positions such as lines with "61%\t" and the other noted occurrences)
so each element is a clean value like "61%". Ensure any future additions to the
values array do not include control characters.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 671080ca-06a8-4fa1-9ac1-8ed810521634

📥 Commits

Reviewing files that changed from the base of the PR and between c93ae3d and f1d1bc6.

📒 Files selected for processing (2)
  • data/characters.js
  • data/characters/snowshine.js

"name": "普攻第一段倍率",
"values": [
"55%",
"61%\t",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

清理数值字符串中的制表符,避免解析/展示异常。

这些 values 含有尾随 \t,后续若做数值解析或精确比对会出现隐性问题,建议统一移除。

建议修改
-                  "61%\t",
+                  "61%",
-                  "77%\t",
+                  "77%",
-                  "76%\t",
+                  "76%",
-                  "88%\t",
+                  "88%",
-                  "180%\t",
+                  "180%",
-                  "182\t",
+                  "182",
-                  "0.43\t",
+                  "0.43",

Also applies to: 37-37, 53-53, 55-55, 75-75, 235-235, 252-252

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@data/characters/snowshine.js` at line 34, The values array contains
numeric/percentage strings with trailing tab characters (e.g., "61%\t") that can
break parsing or comparisons; locate the values array in the snowshine character
definition (the "values" property) and remove all trailing "\t" characters from
each string (including entries at the referenced positions such as lines with
"61%\t" and the other noted occurrences) so each element is a clean value like
"61%". Ensure any future additions to the values array do not include control
characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant