Search results

just roll the socket to vit or dmg% and you are good to go.

The latency issue isn't something I can fix unfortunately its the best possible from where I'm located when connecting to that region. I suppose the issue would have been the lag then. I will pm you the version I modified for my own use base on the current upload and you can have a look and see...

From my perspective cast delay is not for reading the data. Its to reduce the number of times the algorithm decide to select dashing strike to cast. I once tested without delay or something when the charge count went to 0 very often, you can see DB trying to cast dashing strike 3 times in one go...

Its not the cast delay. Its somewhere else. My own cast delays are always 150ms. I dont remember where is the cause but I always modify the handle target and ooc area. No obsidian ring activates only when you HIT the target. you can try casting dashing strike in town you can't reduce...

the > 0 or > 1 doesnt matter the charge count still isn't reliable. I'm using your latest uploaded version and managed to minimised the problem on my side but there are slight occasions of hitting 0. I play with 220 ping which might be the cause. Also I'm wondering with the obidsian...

I edited again regarding the ping. I do hit 0 quite often which is the main reason i switch back to my own edit. It was base on one of my uploads I can't rememeber which but at the same time I do make updates for performance increase from time to time. I've actually always been using FD. Not...

I dont get why everytime I test your updates I actually get worst performance and I end up sticking with version I made myself. The biggest issue I have is when the dash charges hit 0 and I just die. What ping do you play with?

I can't seem to find group runs i'm stuck at 49/50s.

I thought the radar utility is just for debugging purpose at the moment. Hopefully it will be supported in the release. Btw. I'm curious what level leg gems are you guys using.

Can we actually detect if we are standing on inner sanctuary or where the location of it is?

Hmm didn't happen for me. It was always stuck @ 2 charges in 2.9.1 too =/ If I'm not wrong that version thale gave you is the original 2.8.4 trinity with the fuji mods. I think someone updated it to work with the new DB versions.

The problem exist in 2.9.1 too. And 2.10 really has alot more bugs. I'm having other issues not related to the monk combat too. I gave up relying on the Charges value in trinity. I'm not sure why it doesn't get the correct reading. I'm probably not going to do anything else for this version...

Actually I fixed the OOC issue in my port. I just didn't do it the same way as you did. >0 or >= 1 won't change anything. You can look at the method GetSkill(SNOPower power) in Cache.Hotbar.cs. I have some commented code there I used to debug. You can see the charges updating correct but the...

@Beardi For trinity 2.10. I just did the same port over so nothing you added or changed is inside. btw I spend quite some time on dashing strike charges thing. It just seems to be not updated frequently enough. I simplified the logic and added some delays. Didn't extensively test it...

Here is the full zip if anyone else is having issues. Just make sure you delete the CompiledAssemblies folder.

I made some updates to trinity 2.9.1 This files includes the dashing strike logic fuji made in his changes. I just made slight changes to make it work in this version. Delete your CompiledAssemblies folder after replacing the following files then start demonbuddy again...