dimitrius154

None observed. I see a very similar picture with "Lionheart: Legacy of the Crusader". Rather than fix the typos, code them in as is and call it a day.

Mostly, some behaviour parts are hardcoded. The usage procedure is dictated by the orcsystem.dll which I believe to be a customized version of the OGRE graphics engine. Particle filenames are tied to hardcoded spell names.

Nope, proposing the most callou... ahem, quickest solution So, it was not about the entry itself, but its absence?

Replace all three files, then add them back, one by one.

I'd suggest replacing the current blueprint.txt with the one from the previous release.

Ten minutes actually. It's that experience thingie

One to three months, I reckon. It's not the gods who burn the pots. By the way, CheatEngine is indeed a premier debugging tool. P.S. This particular crash happens at the checkBlueprint@cDropMgr@@ABE_NIIIII@Z procedure execution, the culprit is most likely a faulty entry in itemtype.txt. The most cost-effective approach would be to systematically hack off parts of itemtype.txt content until the entry in question is found.

Hmm, sacred2.exe actually. Sacred2.exe: 0x000bf8e6 change 0a to 10 0x000c080f change 0a to 10

That's because there're 2 available skills cap expressions in s2logic.dll sacred2.exe.

Although.... perhaps, they shouldn't. Sort of a murderous aura duration, once in range, the subject is, ahem, infected for (short)life.

Something tells me it's the same way in vanilla.

Are those two issues still in place with the latest patch?

The complete package: https://drive.google.com/file/d/1CQiBrlSLAUNGNobyAwlsAjPrjyeat38R/view?usp=sharing. Password is 12345.