Assertion failure in 1.09b?

S

scuti

New member
Joined
May 4, 2025
Messages
27
Points
3
Is it just me or does the game fail to create a Sorceress (and possibly Necromancer) character if the -act5 parameter is passed to the game?

Steps:

1. In Cactus, add the '-act5' as a launch parameter for Diablo II.

2. Go to Single Player

3. Create a new Sorceress.

On the loading screen, the door will never creak open. For Other Multiplayer, there will be some progress, but the character will fail to join the game.

There'll be a pop up that mentions an assertion failure relating to ItemStats. So I suspect Necromancer (the other class that has a +skills starter item) may have the same problem.
 
Not sure about this, but I would recommend not using that flag. I don't remember 100% but that may be a debugging flag as well. Does this also happen without using Singling (or are you already doing this without Singling)? Also what version of Windows are you on?
 
Already doing this without Singling. Also tried without PlugY. Also no Windows (using Wine).
 
Ah interesting. It would be good to try this on Windows since the game was designed for it. It could be possible that the flag might work on Windows but not through Wine. If someone with Windows (preferably something below 11) wants to give this feel free and report back. If I don't hear back I can also give it a try on either Windows XP, 7, or 10 whenever I get a chance.
 
@scuti I just tested this in Windows 10 x64 for you using patch 1.09b and observed the same result. I couldn't successfully create a Sorceress or Necro. The Barbarian loaded up instantly. I did not try the other classes.
 
That would indicate that this may possibly be a 1.09b bug then. Given act 5 was introduced in LOD, it's possible that 1.07/1.08 might also have this. If someone can test in 1.09d and 1.10f that would be useful as well. If it works in 1.09d that means that they silently fixed that because that isn't documented in 1.09c or 1.09d patch notes (nor in 1.10 IIRC).
 
I did some more testing of the -act5 flag (in Windows 10) per @fearedbliss recommendations:

1.07 - Always failed to load a Sorc or Necro
1.08 - Always failed to load a Sorc or Necro
1.09d - Always failed to load a Sorc or Necro
1.10 - All heroes loaded up just fine

I did not have a platform in Cactus called 1.10f, so I used 1.10. Are they the same? 👀
 
Thanks for testing this @Manny. You've confirmed my suspicion that this was a bug that existed since LOD launch.. which means it actually existed since LOD beta because 1.07 and 1.08 are actually beta builds as per my analysis. One being an early beta build and the other being a late beta build. We normally don't talk about them as such given they got official release names. I'm not surprised that 1.09d still had the issue, and that after all the work Peter and some other folks did on 1.10, that some of those bugs were fixed.

The only other thing would be testing on Windows XP since that's a lot closer to the original source platform (and bitness - 32 bit vs running on 64 bit). I can do that since I still have a Windows XP (SP3) environment but I can test on SP2 as well.

@Manny Yup, 1.10 = 1.10f. I mentioned the 'f' to be more specific vs 1.10s and 1.10b beta builds :).
 
I wasn't aware of this command being bugged pre 1.10, but looks like it is. Tested on windows 7, sorc/necro wont load but the rest do. May be related, but the seed command was silently broken in 1.09 and fixed again in 1.10. It works fine in 1.00-1.08 and 1.10+, but not 1.09a-d.
 
@galaxyhaxz I've used the seed command a few times on my MF Sorceress to restore her map when I accidently clicked on Nightmare instead of Hell, and it always worked as intended. Are you sure it's bugged in 1.09? 🤔
 
Oh it works for restoring the game seed, but run the game with the command on and go out and see what happens with the monsters... lol
 
Aha! That explains it, lol. I've never actually stuck around and played the game after running that command. =P

Thanks for clarifying!
 
You must log in or register to reply here.
Back
Top