UgliBiBagli

They don't differentiate actual GOD on screen indicators from beautified version of whats already available on interlude ;)

noice :^)

It actually could display up to 80 (h5) macros on the list that would be fully functional. More than that could cause bugs (more severe than displaying incorrect amounts like 66/48) It's just a minor modification to make it work as intended tho...

just call the OnRaceSelect event handler with your desired race id (RT_HUMAN in your case, or 0)

nwindow.dll, it must've been still hardcoded back then

skill.mo.4 for interlude

So its resolved server side and doesn't address the question you raised. Who would've thought...

wait... you understood the rest? no way

No you wont (if we speak client side only) because its not like you are allowed to grab anything you want from the server, its right there in your links. What client does is literally asking the server "what are the stats of my character?" in this case only changing the way server responds to this question is a viable solution. Buuuut just for shit'n'giggles... theoretically what you could do is calculate the critical damage rate basing on the damage dealt, but then again this would require dealing the damage multiple times, it would have to be same skills/items/target etc etc - not worth it

you cant just ask the server for those stats, unless its implemented on servers side

no, you cant

the real question is... do the ores have names? :v horry shiet, that was like a year ago

yisss.... mining ;3

emmm.... its just port from god, no?

well, you should be easily able to do that by setting unk 107 (eighth value from the top) to 1 - guess i should consider downloading latest schemes for property names ... :x

unk stands for unknown, people had to figure out whats the actual purpose of each property - you are using latest release which comes with most of them being described properly - anyway... just look at the order of values on his screenshot so you know what to edit

remove handles draggable - false save/load position - false anchor to the main view port, set default coordinates in case you are going to use initialize option

use DXT5 compression for interpolated alpha

nwindow.dll

StatusWnd TargetStatusWnd AbnormalStatusWnd

maybe you are using -ru locale? xd

commandname-e.dat

are you possessed? are there voices in your head telling you to do things? because i dont feel like any sane person would ever want to share such thing this is your 1st try? 2nd? 3rd? ok whatever, if its garbage dont put it up for the world... keep on improving untill theres something valuable to show

you dont deserve to be helped... this is the last post

https://translate.google.com/#en/el/handle or even better... since you are using h5 with almost complete scheme, why dont you just set draggable property to false ;x and then you either make it acquire the position via WindowsInfo.ini or anchoring in xdat - thats up to you