dimitrius154

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.

@bestreducerAddendum patch links updated with the proposed bug solution. Should that suffice, the main archive wil be updated as well. @FlixThe fixed s2logic.dll for the D2F:https://drive.google.com/file/d/1Otv_froTqTnWKCplJX5ZNKurPydY9W1D/view?usp=sharing

Phew, took a LOT less time than anticipated. @bestreducer Any extra bug input is appreciated, so that I can deal with those before releasing the new iteration.

A very unfortunate issue this one turns out to be, a two-and-a-half year old compounded calculation error. While I, generally, avoid solution through attrition, that's the way I have to undertake.

Hmm, would you, please, supply an error entry screenshot from the Windows Application Event Log?

The Battle Extension Double-Hit is a separate mechanics/ Yes, you can. Screens proving the point would be appreciated. They are. The reported effect doesn't look like my doing. Oh, those early attempts at server-client games... and the code itself. Specifics would be appreciated. What bosses? Wondered when someone would report that. The entire naming solution was hedgewizardry. No way to do it otherwise with the original resources on hand. The same issue of the server-client solution. You could end up to 40 minutes with the vanilla.

The _TITLE was missing, will be fixed in the next release.

The one once you enter Bengaresh, west-west from Tyr-Lysia point of entry? It's been around at least since 1.50, I've never altered it, at least knowingly.

There's been a few reports of anomalous drop rates. Working on it.

Yes, I've erroneously retconned the function for non-D2F Addendum editions.

I see, incorrect spawn.txt entries. The issue will be fixed on the next release.

Nope, I've left it stationary.