Trouble with 1.10 beta runes poofing

A place to talk about Diablo II as developed by Blizzard North.
Post Reply
alerch
Fallen
Posts: 2
Joined: Thu Sep 14, 2023 2:49 pm

Trouble with 1.10 beta runes poofing

Post by alerch »

Hello,

First of all, thank you for Cactus. I've been enjoying the software for years and have many many characters across several versions.

My issue is not with Cactus per se, but I've recently found interest in the beta versions of 1.10, specifically the rune words that can be created and forwarded to later patches.

I tried forwarding the runes for Crescent Moon along with a 3 socket phase blade from beta a to beta s on an otherwise empty character.
I simply moved the character .d2s from the one Saves folder to the other.
The result was that the phase blade is there, but the runes are gone.

I tried a second time, this time with runes from patch 1.07 and got the same result.

Am I missing something, is this a know issue, or did I mess up the process of forwarding?

Thank you for reading.
Regards
fearedbliss
Site Admin
Posts: 644
Joined: Sun Dec 19, 2021 11:23 am

Re: Trouble with 1.10 beta runes poofing

Post by fearedbliss »

Hey @alerch,

From what I understand regarding the 1.10 beta runewords, you can't use the original beta runeword combinations in the later versions of the beta or 1.10f. Meaning that once the runeword combinations got changed in the second 1.10 beta, the original beta ones won't work. So IIRC, you can only enjoy the original 1.10 beta combinations in the original 1.10 beta itself.

I hope that helps.

- fearedbliss
fearedbliss
Site Admin
Posts: 644
Joined: Sun Dec 19, 2021 11:23 am

Re: Trouble with 1.10 beta runes poofing

Post by fearedbliss »

Actually re-reading what you said, that’s a slightly different scenario since you are losing the runes themselves even before you created a runeword. You didn’t do anything wrong that I can see, but I wonder if some internal code changed between the way that runes themselves were defined and that is causing it to poof. The other thing I’m thinking about is anti-dupe code. Were the runes legitimately found or were they created with some program (Hero Editor)? But that’s strange and isn’t what I would expect. I would recommend forwarding items in this order to be safe:

1.00 -> 1.05b -> 1.07 -> 1.08 -> 1.09b -> 1.10b (Beta 1) -> 1.10s (Beta 2) -> 1.10f.

1.09b items should be able to go straight to 1.10f given that that’s what would have happened on battle.net at the time when 1.10f went live (1.09d was on battle.net to be specific but same thing pretty much for our purposes). 1.09b and 1.09d are also compatible so you can downgrade from 1.09d to 1.09b. The 1.10 betas are listed above for completeness if you happen to play those versions.

On another note, I’m moving this thread to the general d2 section since it isn’t a technical problem but d2 forwarding behavior. I can move it back if we discover it’s actually some other technical issue.
fearedbliss
Site Admin
Posts: 644
Joined: Sun Dec 19, 2021 11:23 am

Re: Trouble with 1.10 beta runes poofing

Post by fearedbliss »

@alerch I did a bunch of tests and wasn't able to reproduce your issue. Everything seems to be working fine. I made a 3os phase blade in Hero Editor and gave myself a Shael + Um + Tir in 1.07 and 1.09b (with and without Singling). Then I moved those save files to 1.10b (Beta 1) and 1.10s (Beta 2), and I also forwarded the items from 1.10b/1.10s -> 1.10f and everything worked fine and was retained. All the Platforms/Files are coming from Cactus.

Below are some screenshots:

1.07 Base (Vanilla Platform)
1.07-base.jpg

1.09b Base (Vanilla Platform)
1.09b-base.jpg

1.10b (Beta 1) (Vanilla Platform) - 1.09b Character
1.10b (1.09b).jpg

1.10s (Beta 2) (Vanilla Platform) - 1.09b Character
1.10s (1.09b).jpg

1.10b (Beta 1) -> 1.10f
1.10b-1.10f.jpg

1.10s (Beta 2) -> 1.10f
1.10s-1.10f.jpg

1.10b (Beta 1) (Vanilla Platform) - 1.07 Character
1.10b (1.07).jpg

1.10s (Beta 2) (Vanilla Platform) - 1.07 Character
1.10s (1.07).jpg

1.10b (Beta 1) (Vanilla Platform) - 1.09b Singling Character
1.10b (1.09b Singling).jpg

1.10s (Beta 2) (Vanilla Platform) - 1.09b Singling Character
1.10s (1.09b Singling).jpg
alerch
Fallen
Posts: 2
Joined: Thu Sep 14, 2023 2:49 pm

Re: Trouble with 1.10 beta runes poofing

Post by alerch »

fearedbliss wrote: Thu Sep 14, 2023 11:14 pm @alerch I did a bunch of tests and wasn't able to reproduce your issue. Everything seems to be working fine. I made a 3os phase blade in Hero Editor and gave myself a Shael + Um + Tir in 1.07 and 1.09b (with and without Singling). Then I moved those save files to 1.10b (Beta 1) and 1.10s (Beta 2), and I also forwarded the items from 1.10b/1.10s -> 1.10f and everything worked fine and was retained. All the Platforms/Files are coming from Cactus.
First of all, thank you for the extensive testing. This gives me hope that I can make it work.
To answer a few of your questions, all runes were found in either 1.07, 1.09b or 1.10beta (as a hellforge quest reward) and the phase blade was from 1.07 IIRC.

My files comes from the cactus repo albeit from probably a good few years ago. I might have performed a minor hex edit to be able to launch multiple windows for that's all.

I will try to re-aquire the proper files and try again.

To clarify the forwarding process: I'm successfully forwarding the supplies from 1.07 -> 1.09b -> 1.10b. I'm trying to forward from 1.10b to 1.10s and the runes poof.

Thanks again for yout time and extenive testing!
fearedbliss
Site Admin
Posts: 644
Joined: Sun Dec 19, 2021 11:23 am

Re: Trouble with 1.10 beta runes poofing

Post by fearedbliss »

@alerch Np. Let me know how it goes.
Post Reply