I’m using windows 10 and steam Grim Dawn. It’s not a big deal because the problem doesn’t happen if I activate the options on the main menu.
I had to laugh heartily! 
Thank you!
I noticed that issue too, but I thought that’s because of my color blindness…
In v1.30 every color covers now 1/4 of the monsters health, so, color red will start below 25% health.
Update V1.30
- obsolete code fragments removed
- Monster health values reduced to four colors (*)
- (if you want only 3 different colors (**), open the file “GrimInternals.ini” and insert “UseMonsterHealthTrafficLights=True” under [Settings])
(*) 4 colors
- monster hp >= 75% colorCode {^g} = green
- monster hp 50-74% colorCode {^o} = orange
- monster hp 25-49% colorCode {^y} = yellow
- monster hp 00-24% colorCode {^r} = red
(**) 3 colors
-
monster hp >= 66% colorCode {^g} = green
-
monster hp 33-65% colorCode {^y} = yellow
-
monster hp 00-32% colorCode {^r} = red
-
added duration time for buffs (e.g potions) and duration time with damage values for debuffs
Ok, now that happened to me on my Laptop, too!
It never happened before… Weird!
But I found the bug! 
Update V1.30a
- fixes a bug that could cause the player to stop moving after opening the configurator
Thanks to laudon for reporting!
Thanks for the update man!
About the colors is there any chance of us being able to control the indication color?
Its not like I’m digging deeper and deeper into this color thingy but for example the orange color is a combination of yellow and red and should be after the yellow and not green ;] (just read about the colorblind, Peace out man! :D) so id rather not drive you crazy put this color here and there. Either way i love the utility.
And i was wondering if you found anything about the issue sometimes not booting the game from the utility shortcut. Like i said in a previous post of this thread there are sometimes that the game wont boot from the internals shortcut unless i go ahead and start it from the main shortcut of the game.
Today as I installed the new update i decided to delete the old .ini file to try the 3 color option and when i tried to start the game it had the issue. I will throw you the crash report here just in case it helps you figuring out anything
Its not like a big or even an issue for me
My desktop system
(Windows 7 64bit 8GB ram SP1)
Also in the launch options i use /d3d9
Today’s report:
<?xml version=“1.0” encoding=“UTF-8”?>
<crashreport version=“0.95”>
<guid>59e12180-d001-4097-af4c-f3cbc4c50b00</guid>
<name>Grim Dawn</name>
<version>v1.0.2.1</version>
<thread>872</thread>
<pointers>8580776</pointers>
<content>
<file name=“crash.xml” description=“Crash Description”/>
<file name=“minidump.dmp” description=“Crash Dump”/>
<file name=“log.html” description=“Included File”/>
</content>
<properties>
<property name=“os_name” value=“windows”/>
<property name=“os_platformid” value=“2”/>
<property name=“os_version” value=“6.1”/>
<property name=“os_producttype” value=“1”/>
<property name=“os_servicepack” value=“1.0”/>
<property name=“os_bits” value=“64”/>
<property name=“distribution” value=“steam”/>
<property name=“userid” value=“47243DD5E0E8F8DDC64BA302CEA10805”/>
<property name=“mem_load” value=“29”/>
<property name=“mem_totalphys” value=“8482680832”/>
<property name=“mem_availablephys” value=“6006124544”/>
<property name=“mem_totalpagefile” value=“16963457024”/>
<property name=“mem_availablepagefile” value=“14063026176”/>
<property name=“mem_totalvirtual” value=“4294836224”/>
<property name=“mem_availablevirtual” value=“3996860416”/>
</properties>
</crashreport>
Thanks for your efforts man, me and many others appreciate your work
Is it possible to make it show only temporary buffs rather and exclude auras?
Yes, I’ll add this.
I think the color order green, yellow, orange and red (respectively green, yellow, red for the 3 colors version) should be fine now for all. 
After a few hours of testing, I made a workaround to prevent freezing at startup.
Works fine for me now.
You’re welcome!
Update V1.31
- fixed a bug that could cause the tool to freeze at startup
- added option to hide monster health values
- added option to show only temporary buffs
- fixed gameLog (missing Lua messages)
Nice man!! i tried over 10 times the shortcut through steam and no more boot problems! thanks for the color order aswell
Any interest in taking over grim damage? =)
C# / C++, may be right up your alley.
I’m glad the startup issue is gone!
If I had more time I would think it over. But my own projects claim all my free time. Thanks for the offer!
Id love to know on what projects you are working
Related to Grim Dawn I’m currently working on a Quest Status Viewer / Editor,
also I’m trying to figure out how to extend the Lua API and so on (only for my own purposes).
There’s a lot stuff to research that consumes a lot of free time, though. But I have fun with that.
You got a thread of that? looks neat
Also…not fair ! you got 1.32 version of internals ;(
that does look interesting…
In ‘my’ thread there today was a request
sounds like your tool could eventually (already ?) handle this 
Sounds very great!
Hope it comes with language support!?
(Like “[Tool] Grim Dawn Build Calculator”.)
I don’t know exactly what ArchHeretic means by “ability to change the type of Summoned Ravager”.
My tool can change the status of quests, but not the type of an enemy.
I sure understood something wrong.
As soon as my tool works reasonably, I will contact ArchHeretic.
Thanks for the hint, Mamba!