If you have been using NoFiX's DoSFix.dll along with a DoSFix.cs a possible crash issue has been discovered.
IT DOES NOT AFFECT 1.40 / 1.41 and should not used used on those! (1.11 and 1.30 only!)
A fix is available in:
http://ns2.pu.net/dosfix2015.zip
This zip contains the v15 mem.dll with no changes - I just included a copy in case someone happens to be running an older one.
It contains a new DoSFix.dll which is the v16 NoFiX dll plus Altimor's one byte fix plus some hex edits for this fix. There is an included example DoSFix.cs which has been edited.
The basic idea is that we are renaming the "remoteFilter()" function defined in DoSFix.dll and used in DoSFix.cs - we are calling it "Filterremote()" now. We are doing the same thing for the "remoteBadFilter()" function - we are changing the name to "BadFilterremote()". It seems silly ... but ...
As a result if you want to use this you will have to edit your DoSFix.cs. Some server operators have customized their own copy - so they will have to make the simple edits to their own copy.
IT DOES NOT AFFECT 1.40 / 1.41 and should not used used on those! (1.11 and 1.30 only!)
A fix is available in:
http://ns2.pu.net/dosfix2015.zip
This zip contains the v15 mem.dll with no changes - I just included a copy in case someone happens to be running an older one.
It contains a new DoSFix.dll which is the v16 NoFiX dll plus Altimor's one byte fix plus some hex edits for this fix. There is an included example DoSFix.cs which has been edited.
The basic idea is that we are renaming the "remoteFilter()" function defined in DoSFix.dll and used in DoSFix.cs - we are calling it "Filterremote()" now. We are doing the same thing for the "remoteBadFilter()" function - we are changing the name to "BadFilterremote()". It seems silly ... but ...
As a result if you want to use this you will have to edit your DoSFix.cs. Some server operators have customized their own copy - so they will have to make the simple edits to their own copy.
