Read out the EffectList

[Garan]

Originally Posted by moebius92

Actually, the loop variable of a for loop always has a scope that is local to the for loop itself. So I think Kunter's okay in this case.

True. Loop was a bad example.

[Kunter]

function Disease()
	for effectnumber=1, EffectList:GetCount(), 1 do
		if EffectList:Get(effectnumber):IsCurable() then
		Turbine.Shell.WriteLine(EffectList:Get(effectnumber):GetName());
			if (EffectList:Get(effectnumber):GetName() == "Effectname here") then
				return 0.5;
				break;
			end
		end
	end
	return 0;
end

I'd rewrite the function, I hope I get better results now, the WriteLine command is only to log the Buffnames.

[Kunter]

Ok, tested the plugin today, works fine, if Jackdaw is ok with it I will publish it in a few days.

[Snoopy81]

There is 2 ways to catch an effect on the player...

- 1st one as above is to scan "EffectList = LocalPlayer:GetEffects();" at regular intervals (ie: onTimer or on Refresh )

- 2nd, I'd say a cleaner way is to catch events AddCallback(EffectList, "EffectAdded", MyEffectChangedCallback); and "EffectRemoved"

[Kunter]

Originally Posted by Snoopy81

There is 2 ways to catch an effect on the player...

- 1st one as above is to scan "EffectList = LocalPlayer:GetEffects();" at regular intervals (ie: onTimer or on Refresh )

- 2nd, I'd say a cleaner way is to catch events AddCallback(EffectList, "EffectAdded", MyEffectChangedCallback); and "EffectRemoved"

http://www.lotrointerface.com/downlo...ffectWarn.html

I used this:

EffectList = Turbine.Gameplay.LocalPlayer:GetInstance():GetEffe cts();

and this

AddCallback(EffectList,"EffectAdded", --function to handle event--);

So pretty much the same. EffectWarn works very fast and by the time 5 evenings at Saruman show that it is reliable (anyhow for me).