PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Removing abyss socket suffix does not revert sockets to original number

未关闭
#7,964 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

bug
主要语言
Lua
星标
5.4k
派生
2.4k
平均合并
1 天 12 小时
30 天内合并 PR
26

描述

Check version
  • I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
  • I've checked for duplicate open and closed issues by using the search function of the issue tracker
Check for support
  • I've checked that the behaviour is supposed to be supported. If it isn't please open a feature request instead (Red text is a feature request).
What platform are you running Path of Building on?

Windows

What is the behaviour in-game?

Once abyssal socket suffix is removed from an item, the socket itself is removed from an item and its maximum number of sockets became default (4/6)

What is the behaviour in Path of Building?

Once Delve modifier (Has 1 Abyssal Socket (suffix)) is removed from an item (under modifiers section), links on the item remain as, for example, R-R-R A, which later triggers a warning if one places 4 gems into the given item.

How to reproduce the issue
  1. Create a new item which can have abyssal socket (armor piece)
  2. Click 'Add Modifier', select 'Delve' and Has 1 Abyssal Socket (suffix) mod
  3. Click 'Add'
  4. Once added, click 'Remove' against added modifier

Expected:
Sockets revert to original (i.e. R-R-R-R)

Actual:
Abyssal socket is still applied (so it is still R-R-R A)

Character build code
https://pastebin.com/dxKwmbD6 
(Socket Bug, Titan Greaves item as an example)
Screenshots

No response

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

使用列出的 modifier 步骤和链接的 Titan Greaves build 重现该问题,然后跟踪移除 Delve modifier 后物品的 socket 如何更新。完成的标准是移除 abyssal socket,并且物品在不触发警告的情况下恢复到原始的 socket 数量和连接。

由索引模型根据 Issue 内容生成。

评估

技术栈
lua
领域
game-dev
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。