BaseMod and Diablo II general issues
====================================


1) Formatting custom strings with \grey; in AFJ tbl edit always gives white strings.
   I don't think it's a bug in AFG tbl edit, because the same thing happens with code,
   when formatting a string with COL_LIGHTGREY (0x10).


2) UberDuriel Doesn't spawn.  Caused by reducing number of Unique Monsters to less than 
   5 in Forgotten Sands map. Uber Duriel spawns in place of the 5th Unique Monster in 
   the map.


3) World Event Uber Diablo drops junk.  Use the fixed txt files for 1.13c. recomile
   all the txt to bin files, and update Patch_D2.mpq. see \TXT\FixedTxt.txt.
-This Fix is now provided in Patch_D2.mpq with BaseMod.


4) Ubers are weak. Caused by broken chains. Use the fixed txt files for 1.13c. 
   recomile all the txt to bin files, and update Patch_D2.mpq. see \TXT\FixedTxt.txt.
-This Fix is now provided in Patch_D2.mpq with basemod.


5) The SlashDiablo Mod CPU Fix conflicts with BaseMod's CPU Fix. You can disabled it in BaseMod.


6) Some Resolution plugins that enable vsync or change the frame rate for Diablo2 can 
   interfere with BaseMods Framerate/CPU fix.


7) HIPS firewall can block modified Game.exe Loader for BaseMod


Solution shared by user Arkprecession ... Thanks!
-----------------------------------------------------------------------------
The problem is that i reinstalled win 10. and when i try to open the game 
patches with basemod it freezes my computer...

it was my firewall. Comodos firewall to be exact. It did not allow game.exe to execute 
and the rules to authorize it didn't prompt since the game got full screen quite fast.

Ok, I discovered the HIPS of comodo firewall was blocking my game. Added a custom 
ruleset for firewall and HIPS. Opened the game in windowed mode and authorized plugy 
and other game services than prompted. Now it works.
-----------------------------------------------------------------------------

- HIPS firewalls can store file hashes, like an MD5 check sum, for known versions 
of Game.exe published by Blizzard..  When you add in a modified Game.exe loader, 
from BaseMod, the checksum is not found in their database, and can be automaticly 
blocked from running. 



Windows Issues with Diablo II
=============================


1) Firewalls can cause issues with GameExplorer (GameUX dll's) in Vista or later OS's. 
   This happens if you're playing offline, or block internet with firewall. Windows 
   GameExplorer can auto launch RunDLL32 that gets stuck at 100% of one CPU core, and 
   the Game never starts, unless you open it twice. See Files in \Other folder for 
   a regedit Windows fix for this problem.


