Since you suggesting here, I’ll tag other players I know that would use this Grim Internals feature
@RektbyProtoss @Maska322 @tqFan
And also A for making characters move in a different way
5 Likes
With patch testing going on, I really want to emphasize when a particular build gets damage spikes done to it, but it looks like the current setting require a sustained damage over a particular time period in order for the “highest damage output” to be saved to the second column. What’s the best way to demonstrate that a big damage spike happens? Maybe the damage interval should be 0.25 seconds and the time until the highest damage resets be reset to something really long?
I’ve seen the left side of the incoming damage column display pretty big numbers (like when activating Valdaran’s electric projectile aura or Mad Queen’s aura), but the right side column doesn’t take note of it. Mind you, this burst damage only happens across maybe a half-second, but that burst damage is going to kill a build and I want to make sure the tool captures it.
In short, what’s the best way for this tool to take the best notes on receiving burst damage?
Can anybody help me, please? 
Gotta be a quick fox, much appreciatedd.
[/img][/url]
Looks so good!
Fixed it! Just deleted the DPYes ini file and allowed it to restore on launch. Thanks for the amazing work, will get some screenshots.
Here we go, grim cam really displays how much of grim dawns beautiful artwork is a hidden beauty of the entire game itself.
It looks absolutely gorgeous.
Just found out about this tool ! ill take a look looks great
What I would love to see in future version:
regular game speed mode and alternative game speed when rare/boss is nearby/engaged (because fighting them at high speed can be rippy 
).
Also the loot filter needs more high level settings. All I wanted was settings like:
- do not show normal and magic stuff
- do not show any rare weapons except 2h ranged (or better, spectral arbalest only)
- do not show epic weapons
- show all legendary+.
I really appreciate you working on this feature, but is anyone outside of me providing feedback? I tried it once and it had a few quirks (monsters dropping MI’s when killed) until Wave 165 when some unkillable Wraiths showed up and I couldn’t progress to the next wave. I could see how you feel it’s not ready for prime time.
Do you want me to provide any video evidence to you to help you see where things are going off?
I assume this doesn’t work with 1.2.0.4?
It works fine.
Is the source code for DPYes available anywhere?
1 Like
since this seems to be the predecessor of griminternals, is it possible to add Ranged Retaliation=true?
Following up on this - I played some more Crucible with this tool and this time, the unhittable Wraiths came at Wave 159, which I’m assuming is due to Namadea the Screecher which sometimes spawn at this Wave. Seems that any Wendigo monster that spawns Wraiths makes them somehow invulnerable to damage or targeting (pressing pet attack on them causes my pets to do nothing).
Hopefully this narrows down any bugs that are causing this issue.
DPYes is currently closed source.
I’ll take a look at it, but no promises. GI has a lot more features than I’m able to maintain.
What mod are you playing?
Once modded crucible is loaded, DPYes doesn’t actively modify anything to do with crucible, spawns, etc
I’m playing the Grimarillion mod. It’s weird, I believe what you’re saying about DPSYes not touching the Crucible, but enemies dropping MIs and Vital Essences is something I’ve never seen before, much less the untargetable Wraiths. There’s nothing in the Grimarillion mod that would lead to anything like this, so I’m confused as to what the cause would be.
DPYes is currently closed source.
What is the reason for not open sourcing this code base? Given that it’s openly discussed here on Crate’s website there isn’t a threat from them for removing the code.
Open sourcing it would also provide benefits of allowing others to contribute features as needed and if you no longer want to maintain the tool we would have the option to fork and maintain a version that remains compatible. The community wouldn’t be stuck like we were when GrimInternals maintainer stopped updating their tool. It also provides transparency in what’s running on our systems.
Probably for the same reason that GlockenGerda never made hers open source - piracy of the game.
Could you elaborate on what you mean a bit more?
Is the concern that the source code would be used to hook and remove the anti-piracy checks?
Why would anyone ever need a reason not to open source something?
Why would anyone ever need a reason not to open source something?
I didn’t say the author needed a reason to not open source it. I’m trying to understand their decision 
and the only way to do that is to ask.
It would be unfortunate for the community to lose another extremely useful tool like this if the author decides they no longer want to maintain it. That’s my main motivation for wanting to understand.