SlashBlade: Resharped

SlashBlade: Resharped

Mods
185k Downloads

同種の抜刀剣を複数所持しているときに耐久値が正しく表示されない。Incorrect Durability Displayed When Possessing Multiple Identical SlashBlades

Closed this issue · 4 comments

commented

概要

一人のプレイヤーのインベントリに同じ抜刀剣が複数存在する場合、持ち帰ると直前に持っていた抜刀剣の耐久値がクライアント側で表示される。
自己修復機能もクライアントの耐久値情報に基づいて作動するため、修復の必要のない抜刀剣の修復が見かけ上発生する。
さらに、経験値を再度入手して正しい値をサーバーから得るまで実際には発生しないはずの修復の経験値コストを消費したように見える。

Modバージョン

Forge 47.4.0
SlashBlade ReSharped 1.2.30

再現手順

  1. 同じIDの抜刀剣を用意する（Sharpness -White-二本セットなど）（それぞれA,Bと呼称）
  2. Aの耐久を減らす
  3. Bに持ち替えて耐久がAの耐久値で表示されるのを確認する
  4. Bを持った状態でAの自己修復条件を満たす（空腹エフェクトなど）
  5. Aの自己修復と同時にBも自己修復をしているかのような表記が発生する。

Overview

If multiple identical SlashBlades exist in a single player's inventory, when switching to one, the client displays the durability of the previously held SlashBlade.
Because the self-repair function also operates based on this client-side durability information, it appears as though a SlashBlade that does not require repair is being repaired.
Furthermore, until the player gains experience again and obtains the correct value from the server, it appears as though the experience cost for a repair that should not have actually occurred has been consumed.

Mod Version

Forge 47.4.0
SlashBlade ReSharped 1.2.30

Reproduction Steps

  1. Prepare two identical SlashBlades (same ID, e.g., two Sharpness -White- blades). Call them A and B.
  2. Reduce the durability of A.
  3. Switch to holding B and confirm that its displayed durability matches the durability value of A.
  4. While holding B, meet the self-repair condition for A (e.g., get the hunger effect).
  5. When A self-repairs, an indication will appear suggesting that B is also self-repairing simultaneously.
commented

SlashBlade use a UUID that identify the blade stack.
I think that because of the same UUID, you COPIED a blade using creative mode method or something.
That won't be fixed because no effect when player in survive mode, if you find could reproduce in normal game, please reply.

commented

After preparing the materials, I switched to survival mode and was able to reproduce the problem using two manually created Anonymity -Wood- bottles.
The same problem occurred when using multiple Anonymity -Wood- bottles in other pure survival environments that were not the minimum configuration.

commented

Confirmed that SlashBlades have the same UUID!
Also confirmed that ActiveState is a completely failure, update on the ways.

commented

Fixed in 1.2.32
Warning: Major code change for this fixing, so maybe some addon will break.