[1.10] A question on monsters' mouse-hovering

[Ogodei]

Hello

I would like to know if there was a known way to alter the monster brightness when they're hovered with your mouse. I would like to lower it or to change into something like the D1's selection method (it draws coloured borders on monsters).

Thanks a lot for your time

[Quirinus]

I'm not sure, but maybe it handles it by using different color/colormap/shifts. There was a thread on the ranges, but I can't seem to find it.

The point is that there's darker and lighter ranges, some used for transparency.

If it is handled like that, you'd probably have to edit the *.dat files that hold the them and then change the range/entries that are used for that.

For colored borders, I'd think you'd need code editing, but just changing/shifting/mapping the color can probably be done without code editing.

[weapon-x]

i think this can be pulled-off by high-jacking / rewriting / hooking the monsterdesc code and the sprite-drawing code...

firstly you need to add a simple script to the monsterdesc code, which will pass the unit_guid to a global variable, then perform a check in the sprite-drawing code and draw a brighter monster if the monster_guid of the monster being drawn, matches with the unit_guid being hovered to.



cheers

[Necrolis]

Normally the game just changes the transtbl used (to color mul x2) when you hover over a unit. There isn't really much selection in terms of making it less bright. The outline might also require more memory, as D2 caches these on the fly. Regardless of what you check, here is the starting point:

Code: Select all

/* 
	Date: Fri May 28 14:19:00 2010
	Author: Necrolis
	Function: UNITDRAW_CheckSelection
	Address: D2Client.0x6FB286B0
	Comments: 
*/

BOOL __fastcall UNITDRAW_CheckSelection(D2UnitStrc* pUnit)

[weapon-x]

Normally the game just changes the transtbl used (to color mul x2) when you hover over a unit. There isn't really much selection in terms of making it less bright. The outline might also require more memory, as D2 caches these on the fly. Regardless of what you check, here is the starting point:

Code: Select all

/* 
	Date: Fri May 28 14:19:00 2010
	Author: Necrolis
	Function: UNITDRAW_CheckSelection
	Address: D2Client.0x6FB286B0
	Comments: 
*/

BOOL __fastcall UNITDRAW_CheckSelection(D2UnitStrc* pUnit)

aw, cool... thanks for sharing

[Ogodei]

Thanks! I'll take a look later !