ECG_Kinsey I apologize for the confusion. However, as Davide mentioned in the comments on that issue ticket, both the Import PSD and Import Data features utilize the same underlying processing, so the core issue is essentially the same.
Actually, the discussion shifted to internal talks within the Spine team partway through, so it's not visible on the open side—my apologies. While Davide mentioned in the comment that this issue could be closed, I communicated that his proposed solution doesn't resolve the issue. It remains an issue requiring further consideration.
I was rereading your initial request and just noticed this mention:
某些情况下，当PS中的所有图层只发生了位置的偏移，所有的图层命名都和原来的一样，用户只希望根据新Json文件来更新所有图层的位置信息，但是不替换附件，从而能保留之前每个附件的网格信息。
In this case, I believe you can complete the position change by moving the origin in the PSD file, moving the root bone's position by the same amount within the Spine project file, and then returning the root bone's position to X:0 Y:0 while locking all images and bones with compensation.
Therefore, the more troublesome scenario is when you only want to move the images referenced by specific, already-configured mesh attachments.
The same method can be applied to each attachment, but in the case of mesh attachments, they may be bound to various bones. Unlike moving the topmost bone like the root bone, moving a mesh attachment often involves many bones and constraints that require consideration. This may necessitate temporarily moving all weights to a specific placeholder bone, then reassigning the weights after the move. Therefore, we also believe it would be ideal if these issues could be automatically resolved intelligently during import, but addressing that capability seems to be some way off.
