[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]

@steve01055 I’ve just noticed / recalled that at least with melee when you spam 2 cooldown Primal Strike like that and hold LMB (Savagery) very close to your character when there are no monsters around / highlighted - Primal Strike is activated in place without targeting any monsters which can be kinda meh at times. One can probably used to it but I’ll think now if it can be avoided.

[steve01055]

The build is Melee.
And the first solution worked for the cooldown based Primal Strike. Had the delay set to 3000 so there’s no “skill isn’t ready” announcement, works great so far. Tested it on the dummies, the no-target-activation doesn’t seem to be happening.
Thanks for the help!

[tqFan]

@steve01055

And the first solution worked for the cooldown based Primal Strike. Had the delay set to 3000 so there’s no “skill isn’t ready” announcement, works great so far. Tested it on the dummies, the no-target-activation doesn’t seem to be happening.

You need to turn it off in options. I cannot imagine using GDAutocaster with these on
And I recommend revert the delay back to 200

There are 2 separate options (in different menus I believe) for

• message on the screen
• sound informing you about the cooldown

@steve01055

Tested it on the dummies, the no-target-activation doesn’t seem to be happening.

The thing I mentioned happens when no monster / dummies are around / highlighted. When you are just running with your char, holding LMB and move it very close you your character.

---

[edit] I don’t think there’s a solution for that but it’s not that big of a deal. This is how Grim Dawn works for the most part. Only skills on LMB don’t behave like that.

Alternative could be having

• Move on LMB
• Primal Strike + Savagery on RMB

(probably better for Ranged Shaman)

Depends on preferences.

[steve01055]

MY bad, the 3000 was perhaps not the right choice.
Otherwise Solution 2 is working great. The initial delay-short hold is much better ingame.

And yes the secondary issue isn’t that big of a deal. Thanks for the quick response!

[tqFan]

@steve01055

MY bad, the 3000 was perhaps not the right choice.

Yeah, you want that PS button to be spammed so that it fires as soon as off cooldown in various different scenarios.

3s delay could cause very long delays, for example if PS was pressed just before targetting the monster
it would activate nearly 3 second after you started fighting with it because that’s when the next press would be
(at least if you kept holding LMB the whole time and not release + press down again after highlighting the monster)

[TheGrimmest]

When I load the .ini file that is posted here, or attempt any edits to it, I get the following error and GD Autocaster closes:
“Some functions bound to 1 differ in
whether they allow 1 native function.”

[tqFan]

Hi. I don’t think you should attempt to load this super extensive config by the program. It’s just a showcase of options not meant to work, I’ve never loaded it. Better to write config from scratch or ask me to write you some basic one with stuff you want.

Anyway, here’s some example when you can get such error (or rather a warning):

[autocast by hold]
cast1=1:Space
key_native_function1=false

[combo presses]
combo1=1:Enter
key_native_function1=true

See that one function bound to 1 has key_native_function equal to false, another to true.
This warning tells you to make it consistent because

• in one place ([combo presses]) you say you want pressing 1 to still send 1 press
• in other ([autocast by hold]) you say you don’t want 1 press signal sent after pressing 1

(“1” being sent after pressing “1” is button’s 1 native function)

---

Anyway, the easy solution is just to delete the key_native_function thing from the config:

[autocast by hold]
cast1=1:Space

[combo presses]
combo1=1:Enter

(or just delete all features activated by 1 altogether)

---

although it might be possible that some features (aka sections of the config) have different default setting for this nativeness but it should be pretty rare

[3sword]

Hi, I’m trying to use the modifiers you added. By making me hold space to use my LMB skill stationary

[autocast by hold]
cast1=Space:+LButton
delay1=0

but it doesn’t seem to work for that, only after I take away the + (shift) does it start registering LButton clicks

[tqFan]

I’ll look into this but one thing I’ve noticed already:

• [autocast by hold] spams button so it seems you’d like to spam LButton clicks instead

  • wouldn’t you prefer for the LButton to be held ([combo holds] feature)?
    (for the game to spam the skill and not rely on spamming LMB click)

  • if really not and you’d like clicks to be spammed and not LMB to be held:

    I’d recommend to set the delay to 200 or 100, no need to spam that many clicks
    (although my program probably doesn’t allow click / 1ms or something as it’s too slow for that)

---

[edit] Ok. So it seems to be that I only added this i.e. + modifiers thing to [combo presses].
I could most probably add them to [autocast by hold] if you need it but first I’d like you to read / consider
what I wrote in my previous message and maybe also write what you need it for in-game.

Also you could just add [combo hold] Space:Shift to it instead of having +LButton in this scenario I believe
Or instead of spamming +LButtons you could hold both Shift and LMB perhaps.

---

Maybe this could work (I’ll test it)

[combo holds]
combo1=Space:Shift,LButton

[edit] Yep, I’ve tested and it works, dude is attacking in-place with Savagery

[Crater]

Upon download both chrome and windows flags the exe as a virus does anyone else have the same issue?

[tqFan]

False positive, antyviruses and other programs flag unknown programs like that left and right.
Doesn’t mean anything - the antyvirus just doesn’t have it in its database.
You can compile yourself a “Hello World” program and your AV will probably flag it as well

If you want you can download the code from GitHub, check out the .ahk files that there’s nothing there besides pressing buttons
and compile it with AutoHotkey (nothing complicated, just a few clicks and need to select GDAutocaster.ahk and click Convert)

Compiling is not even needed because AutoHotkey can just run GDAutocaster.ahk script
but then you need to have AutoHotkey installed permanently on your machine.

Trust me bro

[Crater]

I looked around and I guess it is a common issue with AHK so that’s reassuring. Thanks for the reply and the awesome tool!

[tqFan]

No problem, let me know if you’d like some configuration ideas / missing some feature.

[GaeanC]

Hi Tqfan,

It’s been a while since I played GD, but I’m back, I hope everything is going well for you.

I’m playing the Dawn of Masteries mod, but I don’t think that should have any affect on how GDAutocaster works. The build I’m playing with at the moment has a bunch of powers that I want to cast all the time, essentially keeping them running, like one would Blood of Dreeg, so I’m using [autocast by toggle]. Here’s that part of the relatively short profile:

[autocast by toggle]
autocast_right_away=true

	cast1=t:a
	delay1=4750
	reset_key1=a
	
	cast2=t:q,x
	delay2=200
	reset_key2=q
	
	cast3=c:c,v
	delay3=5050
	inner_delay3=5050
	reset_key3=v

Cast1 and Cast2 work fine, but Cast3 doesn’t. Cast3 is setting off two instances of the same skill each of which is on a ring and the game allows there to be 2 simultaneous instances. Each of the skills last 6 seconds and has a 10 second cooldown, so what I’m trying to do is have the instance on “c” go off and 5.05 seconds later the one on “v” goes off, then 5.05 seconds later “c”, and so on, essentially casting each just one of them go off every 5 seconds.

When I turn the toggle on, it works perfectly and it continues to work until I zone at which point both instances (c and v) start going off at the same time. If I turn off the toggle and wait until both instances cooldown, I can turn the toggle back on and it works fine until the next time I zone. There may be other things that are causing the loss of delay, but I can definitely see it happen every time I zone. I’ve also tried it with and without inner_delay specified. That doesn’t seem to matter.

Is there a better way to do this or should it work, but is bugged?

Edit – It actually doesn’t seem to do it every time I zone either, although that often causes it. All I can say is that eventually, the two instances will start going off simultaneously. Sometimes, using the reset key will fix it, but not always.

[tqFan]

Hi. delay3 needs to be 2 times longer than inner_delay3 for it to work as you want.
For example with delay3=11000 and inner_delay3=5500 you’ll achieve the following:

• every 11 seconds
  • c is presssed
  • 5500 ms gap
  • v is pressed

which will result in them alternating roughly every 5500ms.

---

But you don’t even have to use a trick like that since there’s alternate option (not sure when added so better to redownload)! Btw seems it’s autocast_on_launch now

[autocast by toggle]
autocast_on_launch=true

cast3=c:c,v
delay3=5100
alternate3=true

It alternates c and v with 5100 ms in between.

[GaeanC]

My post-Covid brain strikes again. I completely missed that “alternate=” keyword when looking at the doc again. There is an example, but it isn’t explained in words.

So , “delay” is the total time before the entire set of actions loops and the “alternate” keyword makes the loop choose a different inner action (stuff between commas), that it does during a loop. “Inner_delay” controls the gap between the inner actions (without “alternate”).

I’d guess that inner_delay and alternate don’t play well together.

Thanks.

[tqFan]

Precisely

@GaeanC

I’d guess that inner_delay and alternate don’t play well together.

I don’t even now, would have to look in the code[edit] I looked

---

inner_delay won’t work if alternate is true, it’s in a separate part of the code / different branch of IF

if (index)
            {
                key := keys_pressed[this.current_buttons[index]]
                Send {%key%}
                this.current_buttons[index] := 1 + Mod(this.current_buttons[index], keys_pressed.Length())
            }
            else
                Common.PressButtons(keys_pressed, inner_delay)

before adding this feature I just had the last line Common.PressButtons...

[tqFan]

@Vaxew

hello, is there config for GDautocaster?

This is for Advanced character because beginner might be slightly different

---

Here are my hotbars, 1st is active and the 2nd one is for toggling passive buffs once:

---

In-game Bindings recommendation for this specific config:

• Q - skill 4, for manual Pneumatic Burst casts

  • could potentially be also configured in GDAutocaster no in game but I chose native pressing
    by [combo presses] such as combo1=q:4

• I also have W for Health pot and E for Blade Barrier so that

  • Q, W, E are in a row just like on the hotbar (4,5,6) and you should cast them in that order of priority when your Health drops
    and it’s easy to look at the hotbar and choose the first one that’s not on cooldown

• Y configured for Hotbar swap in game’s Keybindings

• Space configured to be skill 7 - not needed as it spammed on Space by GDAutocaster anyway
  but it might speed up Shadow Strike activation by 100ms or so sometimes

---

Here the most important thing from my config:

[general]
suspend_key=Tab
suspend_stops_autocast=true

[autocast by toggle]
autocast_on_launch=true

cast1=`:4,4,4,4,4
delay1=23000
inner_delay1=1000
reset_key1=q
key_native_function1=true

cast2=`:2
delay2=2000
key_native_function2=true

[combo presses]
combo2=r:y,0,7,8,9,0,y
delay2=500

[autocast by hold]
delay=200

cast1=Space:7,8
cast2=RButton:7,0,9
cast3=s:9,0

(I have other minor stuff there like fast keyboard camera rotation / one click map / freezing Tribues for Crucible / camera speed hack / 1press to drink multiple potions etc.) Let me know if you’re interested in stuff like that.

---

Here is explanation of all the things:

[autocast by toggle]

cast1=`:4,4,4,4,4
delay1=23000
inner_delay1=1000
reset_key1=q
key_native_function1=true

cast2=`:2
delay2=2000
key_native_function2=true

The first one casts Pneumatic Burst automatically very rarely (every 23 second) but presses the buttons 5 times (which lasts less than PB’s cooldown so it’s not cast multiple times) to prevent it not being cast in loading screen / when you’re Shadow Striking and cannot cast then. Also makes the 23s timer reset when after you press Q (which is meant for manual PB casts).

The second one presses Word of Renewal button (2) every 2 seconds. I just spam it for more heals. No resetting / manual casts here because the heal amount is too small for it to be worth it

You can turn this on / off if needed with the ` in this config (over Tab)

The first one might look complicated because it uses many options [autocast by toggle] provides.

The key_native_function is a technical thing that I should honestly get rid of in GDAutocaster so it’s not needed here.

---

[combo presses]

combo2=r:y,0,7,8,9,0,y
delay2=500

This one casts perma buffs and Spirits from the 2nd hotbar after pressing R.
Y needs to be configured for Hotbar swap in game’s Keybindings.

You can also have one just for 3 buffs w/o Spirits for when you’re nullified (Spirit don’t disappear then)
and maybe even smaller delay.

---

[autocast by hold]

delay=200

cast1=Space:7,8
cast2=RButton:7,0,9
cast3=s:9,0

• cast1 (Space) spams Shadow Strike and another Movement Skill on Space just for movement / initiating the fight not for the fight itself

• cast2 (RMB) is spamming Rune of Hagarrad, Shadow Strike and the Seal during the fight with RMB

  • notice in this way Seal is spammed as often as possible, this can be configured in a different way so that Seal is cast only once per RMB Click + Hold if you prefer to cast it once per its whole life time which depends on your playstyle

• cast2 (S) can be sometimes used to place Seals and Runes of Hagarrad manually before a fight

[Vaxew]

oh thank you a lot for this(i rearranged some bindings and it works fine now)

[Christian]

Great tool overall, but may I make the suggestion to enable comments in the config file?