Food wrote:While we're at it I may as well ask: do you plan on fixing LCS damage display? And in that case, how do you plan to mage that? Just curious.
It's not in my plans. Not that I do not want to, but that's just way too much work. To start off the damage display itself is handled in 24 different functions:
Code: Select all
/*
Table: Stat Screen Damage Desc Drawing Functions
Address: D2Client.0xF5210
Notes:
*/
D2SkillDamDesc_t gptSkillDamDescFunctions[] =
{
NULL,
D2CLIENT_SkillDescDamFunc01,
D2CLIENT_SkillDescDamFunc02,
D2CLIENT_SkillDescDamFunc03,
D2CLIENT_SkillDescDamFunc04,
D2CLIENT_SkillDescDamFunc05,
D2CLIENT_SkillDescDamFunc06,
D2CLIENT_SkillDescDamFunc07,
D2CLIENT_SkillDescDamFunc08,
D2CLIENT_SkillDescDamFunc09,
D2CLIENT_SkillDescDamFunc10,
D2CLIENT_SkillDescDamFunc11,
D2CLIENT_SkillDescDamFunc12,
D2CLIENT_SkillDescDamFunc13,
D2CLIENT_SkillDescDamFunc14,
D2CLIENT_SkillDescDamFunc15,
D2CLIENT_SkillDescDamFunc16,
D2CLIENT_SkillDescDamFunc17,
D2CLIENT_SkillDescDamFunc18,
D2CLIENT_SkillDescDamFunc19,
D2CLIENT_SkillDescDamFunc20,
D2CLIENT_SkillDescDamFunc21,
D2CLIENT_SkillDescDamFunc22,
D2CLIENT_SkillDescDamFunc23,
D2CLIENT_SkillDescDamFunc24,
};
Then there's the fact some incorrect display bugs are caused by stuff like x thing is not sent to the client by the server, x skill/stat not being updated properly, or whatever, and that means finding the source of said bugs, fix them, and so on....