[Tool] GDAutocaster - play 🎹 builds with ease, autocasting of skills, combos, faster / automatic camera, autohiding of items, centered Inquisitor Seal and more for all games!

[tqFan]

Update

release ComboHolds buttons in reverse order

For example here

• if you hold RButton, z is held 1st, then 0
• if you release RMB, 0 is released, then z

[general]
suspend_key=Tab

[combo holds]
combo1=RButton:z,0

This is for a situation described below

---

Blade Arc on Right Mouse Button with automatic Stationary Attack
Instructions:

1. download the program https://github.com/kowariantny/GDAutocaster/raw/master/GDAutocaster.exe

2. prepare a config for the program similar to this (.ini extension of text file needed)

config.ini (sample name of the file)

[general]
suspend_key=Tab

[combo holds]
combo1=RButton:z,0

Legend (you can change button but in this example):

• this config makes z being held and immediately after that 0 being held after you press and hold RMB

  • release them in reverse order when you release RMB

• Tab - turn the feature on/off

• z - in-game you can set 2 bindings to Stationary Attack. The 1st one is Shift by default. Set the 2nd one to z for example. This is because Shift is sometimes problematic in AutoHotkey, better use other buttons if possible.

• 0 - put Blade Arc on 0 on the hotbar for example, have RButton empty as in the presented GIF

3. run the program (doesn’t matter if turned of before or after GD is run)

4. load the config (config is loaded automatically when Grim Dawn window is active, which means you don’t need to reload the config if you change it)

5. the program needs like 4 seconds after Grim Dawn is unminimized / active to start working. Remember that if Alt Tabbing.

6. The feature is On by default.

[tqFan]

https://github.com/kowariantny/GDAutocaster/raw/master/GDAutocaster.exe

I made a ton of changes in the code in most features so I would be grateful if you redownload and use the most up-to-date version to find potential bugs. I tested everything though.

[GaeanC]

Hi hi. Been away from Grim Dawn for a while, but I’m playing again and looking at my old GDAutocaster scripts. You’ve certainly been busy tqfan! Lots of new stuff and greatly improved documentation.

Speaking of documentation, there are some things that aren’t documented anywhere. For example:

[autocasting]
master_hold=`
master_toggle=`

and (toggle_key in the below):

[6]
toggle_key=t			
delay=15000	
initial_delay=100

Is this stuff deprecated (no longer works) or does it still work as it did, but isn’t the way to do stuff any more?

[tqFan]

but isn’t the way to do stuff any more?

This
w8 I"ll write how it’s done now

[autocast by toggle]
delay=5000

cast1=q:1,2,3
delay1=2000

cast2=d:4,5
cast3=d:6

Or just from documentation:

[autocast by toggle]
autocast_right_away=false
delay=1000

cast1=`:2,4,5
delay1=3000

cast2=`:6
not_hold_keys2=LButton,RButton
delay2=500

cast3=`:1
delay3=18000
reset_key3=1

There’s no master toggle now but you can achieve it if you bind stuff to the same key

• by either definiing multiple casts to the same buttons
• or just one cast with multiple skills

[GaeanC]

As usual, thank you for your very prompt reply. I’m glad it still works, since I have a bunch of old profiles. The new way is more consistent with other syntax.

[tqFan]

Yes, that was the intent. It was the first feature that’s why it was different because I hadn’t come up with a standard way of coding this then.

[GaeanC]

Oh, I see the master key doesn’t work… shouldn’t actually be a problem for me as I didn’t use it before. It was just copied from your old examples.

[tqFan]

Yes, there’s only Suspend now for simplicity. I rewrote Aucast by Toggle from scratch.

@GaeanC oh and there’s a cool feature now of automatically starting Autocast by Toggle
when game window becomes active.

[autocast by toggle]
autocast_right_away=false

@GaeanC Also I fixed manual camera rotation so now it’s precise

Also 2 features for clicking with mouse.

And also you can have a button pressed i.e. 3 times with 100 ms delays every 5 second while you’re holding a button

[GaeanC]

I noticed in an earlier post there was discussion of how to find the correct x and y positions for clicks. Autohotkey, when installed, at least my old install, included a program called Window Spy which shows the mouse position (and lots of other useful stuff). I haven’t actually used that function yet, but I think using Window Spy should be a very easy way to get the coordinates that are needed for clicks.

[tqFan]

Not sure what you mean, I can check where my cursor is without problems on what pixel that is

@GaeanC and check out

[Tool] GDHacker - {Tribute, Exp} Freeze / Game Speed / DPS window toggle from within the game

GDHacker - a command line tool with various features GDHacker on GitHub                         meant to be executed from withing the game using GDAutocaster currently has 3 functions mentioned in the title and works only for 64bit Grim Dawn more features and 32bit planned to be added according to requests / my capabilities meant to provide for comfortable usage for some features found already in Grim Internals / GDStash Game Speed toggle I remember people asking for this f…

also Automatic Camera Rotation was included in GDAutocaster and is more configurable then ever.

also GDAutocaster can now work in multiple applications / windows at once

[GaeanC]

This ([Tool] GDAutocaster - play piano builds with ease, autocasting of skills, combos, faster / automatic camera, autohiding of items, centered Inquisitor Seal and more for all games!) is the post I was referring to. I was suggesting Window Spy as an alternative to taking a screenshot and measuring pixels in paint.

[GaeanC]

I’m trying to use a simple center cast (good old Inquisitor Seal), but it isn’t working at all. Instead of the cursor going to the center, it keeps moving toward the lower corner of my screen. My resolution is 1920x1080 windowed borderless. Any idea what might be wrong? Here is the relevant section of my script:

[center casts]
cast1=c:3
initial_delay1=0
delay_after_cursor1=40
closer_not_center1=false
key_native_function1=false

[tqFan]

Your config works for me with Windowed / Borderless. Your desktop resolution is the same (I mean window filling the whole screen)?
Also works for me with external monitor or even if window doesn’t fill the whole screen.

Do you have multiple screens / monitors?
Have you tried restarting the program or it never works?

[GaeanC]

I’m using two monitors and GD is on my 2nd (not main) monitor. Since you asked, I tried restarting GD and GDAutocaster, both together and separately. No change. It just doesn’t work.

Both monitors are the same resolution, but different physical sizes (laptop screen vs. large desktop monitor). -ed

I also tried increasing delay_after_cursor, no change. -ed2

The GD window does fill my whole screen -ed3

I also tried the auto-camera function and that worked fine. It’s very neat, but not my personal cup of tea.

[tqFan]

I will link you a different version to test it it works
@GaeanC https://mega.nz/file/cB0STISD#1ATe3YNBh0SEBSol2qUrZ6gApW0thQu6pw8Un62ZexA

[GaeanC]

Just got to try that out. Still using the script text shown in the post above, the cast now is occurring about 2 body lengths from center toward the bottom left corner and the cursor (after the cast) is moving from its starting position sort of toward that same corner of the screen, but in a way that seems to be modified somewhat depending on where it started.

The new code definitely changed the behavior and is closer to what I expected, but something is still clearly wrong. If there is anything I can do to help with the diagnosing the problem, let me know.

[tqFan]

https://github.com/kowariantny/GDAutocaster/raw/master/GDAutocaster.exe

Didn’t want to figure it out so I added option to specify screen’s width and height manually:
Please try it and use the link above.

[center casts]
screen_width=1920
screen_height=1280

cast1=RButton:7,6
initial_delay1=0
delay1=200
delay_after_cursor1=40
off_center1=false

or this shorter version should be enough

[center casts]
screen_width=1920
screen_height=1280

cast1=c:3

Also closer_not_center was not updated by me in the documentation.
It’s off_center but it’s not related to the issue you’ve been having.

[GaeanC]

Turns out my actual resolution is 1920x1080 (not 1280), but even after correcting for that in the script, it still isn’t working right. It is getting closer.
The cast is now about 2 body lengths left and the cursor return point is about 2.5 body lengths toward the lower left (not toward the corner, at a 45 degree angle toward from its original position.

In the picture below, I started with my cursor right at the center of my avatar’s feet and did one cast.

The relevent part of my script:

[center casts]
screen_width=1920
screen_height=1080

cast1=c:3
off_center1=true
key_native_function1=false

I also tried with “off_center1=false” but the result was identical. (-ed: correction in italic)

[tqFan]

This is crazy I’m just reading screen’s width and height and moving to
Width/2, Height/2, there’s nothing complicated there

Somehow pixels have some weird coordinates???

Have you checked it while only one monitor is turned on / desktop set to 1 screen only?

[GaeanC]

Trying to think of anything that could be having an affect:

• Using GrimInternals and Rainbow Filter.
• My mouse is a corsair mmo mouse with software that affects the dpi and enables macors and such (not using any macros or such that should be significant though).

Would it help for me to use Window Spy to get exact coordinates?