vaal gem and townrun

[vjxy123]

It seems eb can't cast vaal haste.
I try to reboot eb, check/uncheck the vaal gem setting on the exampleRoutine,dont help.

For the town run,if eb press shift and left mouse on the unid items.It will speed up id items.

 

[WhereIsMyMind]

Do other vaal gems work? There is a check box in the EB gui for 'use vaal gems', if that is not checked then the bot will not use them (and you would need to code the use in a combat routine).

Town run... yes it would be quicker but not take much compared to an entire run.

wimm

 

[vjxy123]

only have vaal haste. AutoCastVaalSkills is checked

 

[pushedx]

Vaal auras were removed by default from being cast via normal aura logic based on user feedback (they originally were cast).

You have to have it on its own slot for it to be cast (and it can't be granted from a corrupted item).

If you want to change that behavior, you'll want to remove the checks for vaal in the following locations:

Line 340:

if (_auraSlot == -1 && ((tags.Contains("aura") && !tags.Contains("vaal")) || IsAuraName(name)))
{
   _auraSlot = skill.Slot;
}

to

if (_auraSlot == -1 && (tags.Contains("aura") || IsAuraName(name)))
{
   _auraSlot = skill.Slot;
}

Line 1400

if ((skill.SkillTags.Contains("aura") && !skill.SkillTags.Contains("vaal")) || IsAuraName(skill.Name))

to

if (skill.SkillTags.Contains("aura") || IsAuraName(skill.Name))

That should make them cast on normal aura slots.

"Multi-use" of currency though holding Shift is not supported by the API and there are no plans to support it due to technical reasons and complications added by trying to support it.

 

[vjxy123]

ty push.it works now.
should be better if cast vaal gem when there are rare monster nearby.

why the log keep spamming
[CanCast] We cannot cast [Vaal Haste] because CurrentSouls < SoulsPerUse?
did the EB keep pressing the vaal gem slot's key?

 

[WhereIsMyMind]

>did the EB keep pressing the vaal gem slot's key?
Yes, but the ExampleRoutine CR will fail through to another action.

>should be better if cast vaal gem when there are rare monster nearby.
This requires a little more work but the code looks like the below. You would need to remove the edits above, I suggest download a fresh copy of EB so that you get a fresh unedited exampleroutine, and put this in somewhere after the caching section of the CR. This is also hardcoded to use slot 8 for the vaal gem. The action is to self cast(?), so it will not work with a gem that needs a target/direction.

Below is untested, here only to give you an idea. I will not support this

if (cachedRarity >= Rarity.Rare && myPos.Distance(cachedPosition) < 70)
{
	Log.InfoFormat("[WIMM rareclose checking VAAL");
	var skill = LokiPoe.InGameState.SkillBarPanel.Slot(8);
	if (skill.CanUse())
	{
		Log.InfoFormat("[WIMM] rareclose CanUse VAAL");
		var err1val = LokiPoe.InGameState.SkillBarPanel.Use(8, true);
		if (err1val == LokiPoe.InGameState.UseError.None)
		{
			await Coroutine.Sleep(Utility.LatencySafeValue(500));
			await Coroutines.FinishCurrentAction(false);
			await Coroutine.Sleep(Utility.LatencySafeValue(100));
			Log.InfoFormat("[WIMM] rareclose Using VAAL");
			return true;
		}

	Log.ErrorFormat("[WIMM] rareclose but vaal code failed! Use returned {0} for {1}", err1val, skill.Name);
	}
}

wimm

 

[vjxy123]

if EB keep pressing the key to test the vaal gem's useable,from my view,it is very easier to get banned.
for the code part,I will give a try

 

[WhereIsMyMind]

The client does not allow the keypress, thus does not get sent to the server. When the client thinks the key can be pressed, then the request goes to the server and the server state checks that this is within the time bounds it expects. If the server agrees, then the keyed action is accepted.

So.. don't be concerned if the bot is spamming a skill that is on cooldown.

But this is a problem from your bot's point of view as it slows them down when they could be efficiently killing/grinding

wimm

 

[pushedx]

ty push.it works now.
should be better if cast vaal gem when there are rare monster nearby.

why the log keep spamming
[CanCast] We cannot cast [Vaal Haste] because CurrentSouls < SoulsPerUse?
did the EB keep pressing the vaal gem slot's key?

There is an aura debug setting you must have enabled. Check to see if the "DebugAruas" setting is checked in ExampleRoutine's settings gui.

The message is being displayed because the bot isn't using the skill, so EB isn't pressing the key, not that it'd matter since the client won't cast it anyways.