|
|
metadata
I was really looking forward to Contingency Autocasting – until I used it. I thought that it was applied once before a priority autocasting to make sure that X amount of Mana existed before running the entire ‘group’ of autocast spells. In other words:
If Mana=1300 {
cast Call to Arms
wait for 100 more mana and then cast Gem Grinder
}
Instead it set a mana minimum for any spell in an autocast group. Using the example above, the Call to Arms would run at 1300 Mana but time out before another 1300 Mana was generated for Gem Grinder to run.
My goal was to have the two spells running at the same time, something almost impossible with Contingency Autocasting as it stands now. I’d prefer that it was either changed to one check before entering into the autocast group or have one mana limit for each item in an autocast group.
|
|
|
|
|
metadata
What you need is Planned Autocasting.
It behaves the way you were hoping/expecting Contingency Autocasting to work. Planned gives you two sets of priorities; priority 1 behaves exactly like Planned, but priority 2 fires off as soon as enough mana is available, as long as the spells tagged as priority 1 are active.
|
|
|
|
|
metadata
Thanks. Now all I need is another 7 million mana to get it. :)
|
|
|
|
|
metadata
It’s slow, but worth it. :)
|
|
|
|
|
metadata
I’ve been thinking hard and have not yet found any place where I would use Contingency Autocasting as it stands now. I find it more of a limitation than a help. Have you used it in the past? Do you have an example that might spur my mind?
Thanks
|
|
|
|
|
metadata
I used it a lot for combocasting before planned showed up.
With mercs it’s easy to get 5000+ mana, meaning quadcast + 10 TC with contingency
|
|
|
|
|
metadata
Contingency casting definitely has it uses in early game. Contingency way outperforms priority for AFK titans.
Titans : Contingency LS+CtA (+TC should you have enough mana left). With the slow mana regen on titan, no priority setup can beat this pre-bloodline, and by r7, your neutral phase is so short, you shouldn’t AFK through it anyway.
I’m pretty sure contingency works better for druids as well, unless you are on a really long run. High max mana, and not exceedingly high mps (only long druid runs get a decent mps, if I recall correctly) means more uptime for full combo and more tc’s in that combo with contingency. They’ve reworked druids a bit since I had the chance to test them in early game, so I might be wrong here.
Once you get to higher r-numbers and spend most your time on mercs, then yes, contingency doesn’t hold up. And having planned is always better than just having contingency. But contingency isn’t useless in the context of the entire game.
|
|
|
|
|
metadata
> *Originally posted by **[green200](/forums/8945/topics/542373?page=1#posts-9695503):***
>
> How do you even use auto casting? I already purchased it but I have not found any way to use it.
It’s in tooltip of upgrade. Ctrl+Click on spell to set it into autocast. Then after 2 autocast upgrades which first lower, then eliminate mana regen penalty is priority where you can set in which order spell will be activated (also by ctrl+click). Except that priority is useless for nearly everyone except angels as spells turn on as soon there is mana, yet pretty much rest of faction doesn’t have enough mana regen to make use of it. Then there is contingency where you can set to fire off spell only when you have x mana. You decide how much x will be by yellow pointer (or whatever it’s called) on mana bar. By ctrl+click you can turn off and on contingency. And lastly Planned, best one. First you have contingency casting – only when x mana is available after which comes second turn of priority which fires off as soon there is mana (in order) and as long previous spells are active.
And to unlock each next autocast upgrade you must take care of milestones of spent mana. [http://realm-grinder.wikia.com/wiki/Upgrades](http://realm-grinder.wikia.com/wiki/Upgrades)
|
|
|
|
|
metadata
> *Originally posted by **[MysticRPG](/forums/8945/topics/542373?page=1#posts-9692579):***
>
> I was really looking forward to Contingency Autocasting – until I used it. I thought that it was applied once before a priority autocasting to make sure that X amount of Mana existed before running the entire ‘group’ of autocast spells. In other words:
>
> If Mana=1300 {
> cast Call to Arms
> wait for 100 more mana and then cast Gem Grinder
> }
>
> Instead it set a mana minimum for any spell in an autocast group. Using the example above, the Call to Arms would run at 1300 Mana but time out before another 1300 Mana was generated for Gem Grinder to run.
> My goal was to have the two spells running at the same time, something almost impossible with Contingency Autocasting as it stands now. I’d prefer that it was either changed to one check before entering into the autocast group or have one mana limit for each item in an autocast group.
Well, what it actually does is attempt to fire off the entire group when you hit the bar. Once you run out of mana the chain ‘breaks’ and it waits for the bar to be hit again before it fires off again. Basically with enough max mana it is decent enough to multi-cast 2 spells for most factions, but not the two most expensive ones.
|
 "MysticRPG"){kind=avatar}
 "ElegantCaveman"){kind=small}
 "Juunash"){kind=small}
 "sciurusaurus"){kind=small}
 "Adwark"){kind=small}
 "Crystalis"){kind=small}