-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue Report]: Item Morphing #7742
Comments
Can you label which screenshots are which? They would be any of these:
|
Here's what I'm observing, using the latest master of 1.6.0-dev, Commit d92bdd2: Multiplayer Diablo 1.5.4: Multiplayer Hellfire 1.5.4: Multiplayer Diablo 1.6.0-dev: Multiplayer Hellfire 1.6.0-dev: There is no morphing occuring, and the new feature that prevents invalid items from being usable is working as expected. The only thing I anticipate is happening is either you are using an older version of 1.6.0-dev, or you're using a modified build of 1.6.0-dev. Although I don't recall any commits being merged that fix any sort of morphing. Anyway, the problem isn't reproducible and you can resolve this by using the current latest master. |
Oh, it wasn't clear from the steps that you need to load the save twice. |
Operating System
Linux x64
DevilutionX version
Other (please specify version number)
Describe
Items that were shopped in Hellfire are morphing when brought into classic. This is only happening in the beta version (downloaded February 1st, 2025). This is in multiplayer.
Multiplayer Diablo 1.5.4
Multiplayer Diablo 1.6.0-dev (2 Screenshots)
To Reproduce
Made a copy of my save in an external folder
Launched game using different versions
Loaded up character save to check if items morphed (and started a second game to double check if they would morph for 1.5.4 and lower)
I've attached my original hellfire save and also the classic version that I have been using. Cannot upload .sv or .hsv so I added .txt to these files.
multi_30.hsv.txt
multi_30.sv.txt
Expected Behavior
Items should never morph and instead be colored red to signify that they cannot be used.
Additional context
The text was updated successfully, but these errors were encountered: