Weird energy interaction..

[edge2054]

I'm in the middle of trying to rework anomalies and I've come across a hangup.

The issue is that I want to interrupt the anomaly code with a getTarget call. When getTarget is called an extra turn is used.

Code: Select all

	if self:knowTalent(self.T_PULL_SKEIN) and rng.percent(self:callTalent(self.T_PULL_SKEIN, "getTargetChance")) then
		x, y = self:getTarget(tg)
	end

If I comment out that second line everything runs fine and uses the appropriate amount of energy (talents fail to run, anomalies go, self:useEnergy() is called in the anomaly code).

These talents are forceUse and {ignore_energy=true}. The only thing I can think is that the talent coroutine is getting interrupted by the getTarget call somehow. All of this is getting called from preUseTalent similar to how it is in head. I've tried setting it to game:onTickEnd and it doesn't seem to help.

Does anyone have any ideas on what the problem is?

[edge2054]

Alright, so setting anomalies t.no_energy as true is a work around but I'm not sure temporal form needs that buff So if anyone has any better ideas how to approach this let me know.

[edge2054]

Alright, after a bunch more experimentation is seems that forceUseTalent(self.T_BLAH, {ignore_energy=true}) only works for talents that aren't targetable or that have a target that's forced. I have no idea why but I tested it with several talents.

[katt]

I noticed in the character guides that the option to boost a talent tree (by spending a category point on it) doesn't seem to be used very often, in general. The only tree I've seen this recommended for is pugilism (brawler). I guess it's because of diminishing returns? Is there no other talent tree worth boosting?

[Nagyhal]

edge, what a juicy find!

I'll look at it tomorrow if no one's found the cause already.

Bear in mind my aim will be to educate myself about the processes at work, with any fixes being a secondary, unintended benefit . If I think I can do it though, I'll give it a try.