I'm attempting to create an OnHit event that applies to every actor in the game (and those added my mods). In the wiki, it says you cannot apply a script to an actor added by a level list, but you can get around that by applying the script to an effect that is applied to a spell that is applied to a race.

It seems in order to do that, the script on the effect must use "extends ActiveMagicEffect"... which is fine except that I don't believe it allows me to use "WornHasKeyword"... but "extends Actor" will let me use that.

So is there a way for a script that extends ActiveMagicEffect to call a script that extends Actor upon the actor that has the magic effect applied to it?

Any suggestions are welcome! Thank you!

The phrase "call a script" isn't correct - using the right terminology it's meaningless - so I'm not really sure what you're asking.

Hopefully you'll find it useful to know that an http://www.creationkit.com/ActiveMagicEffect_Script will receive events events from the http://www.creationkit.com/Actor_Script to which it's attached. So you can, for example, successfully use an http://www.creationkit.com/OnHit_-_ObjectReference event as a native event in a script that extends ActiveMagicEffect.

Cipscis

Thank you... I'm quite new to scripting

Yes, I changed from extending an Actor to extending an ActiveMagicEffect because of this issue stated in the wiki...


But when I went to save the script, it gives me these errors...

"WornHasKeyword is not a function or does not exist"

and...

"type mismatch on parameter 2 (did you forget a cast?)"


It saved without error when extending an Actor, but simply changing it to extend an ActiveMagicEffect causes that. So I'm guessing that "WornHasKeyword" or casting a spell doesn't work under an OnHit event that is within a script that extends an ActiveMagicEffect. Does that make sense?

Ah, that's because you're trying to call those functions without specifying an object on which to call them, so the compiler assumes that you're calling them on the "self" object, for which those functions don't exist because it's a different type.

You'll want to use an http://www.creationkit.com/OnEffectStart_-_ActiveMagicEffect event, and extract the information in the "akTarget" parameter. This is the http://www.creationkit.com/Actor_Script on which you want to call those functions.

Cipscis

Ah, thank you very much!
Good Sir Cipscis, what would I do without you???

If I may ask one thing...
Where would I need to put the OnEffectStart event in my script, and where would I need to end it? Before or after the OnHit event begins?

Also, in order for the "WornHasKeyword" function to work properly, will "Event OnEffectStart(Actor akTarget, Actor akCaster)" automatically set all of the information needed, or will I need to actually need to return any specifics from the event?

I do apologize for being a bother. If there's an example script somewhere that does something similar, I'm sure that would help without causing you or anyone else to have to write out a new example

Thank you again!

Events aren't quite like the old scripting system's blocktypes. An event is really just a function, with the only non-semantic difference being that events can't have return values. Some events, however, like http://www.creationkit.com/OnEffectStart_-_ActiveMagicEffect, are native events, which means that the game engine itself will call them on the appropriate objects at the appropriate time.

Since non-declarative code can only be placed within function definitions (including event definitions), native events will always be the entry points to your code. Because events are really just functions, you can put their definitions in any order in your script and it won't change a thing.

You should be able to call http://www.creationkit.com/WornHasKeyword_-_Actor on the "akTarget" parameter inside your OnEffectStart event - the game passes the correct information in when the event is called natively. The only other thing you'll (almost certainly, but depending on how you're doing things) need is a Keyword property for this function's "akKeyword" parameter.

Cipscis

Thank you so much! I got the main script to work!
I do have yet another question, though.

My script is set up in this format...




What I'm wondering is how and where I need to place the "consequences" if a strike is successful. I would like to apply damaging spells/effect on the scripted actor. But I would need to point to the actor again instead of the magic effect, correct? Would I need to use "OnEffectFinish" in order to do so? Would there be any reason not to do so? What would an alternative be? Is there anyway to pass the akTarget into the main script from the OnEffectStart event?

I fear I'm lost on syntax in that, haha! This is my first script ever

I tried to point to OnEffectStart's akTarget inside the OnHit event by using...

"akTarget.WornHasKeyword()"

and also...

"OnEffectStart(akTarget).WornHasKeyword()"


That's why I moved everything that used that function into the actual OnEffectStart event.


EDIT:

Would http://www.creationkit.com/GetTargetActor_-_ActiveMagicEffect() work?
I suppose not if every actor had the same effect?

Unlike most programming languages, Papyrus isn't picky about where you declare things...you can declare a variable at the end of the script, and use it at at the beginning, and so on.

Kageseigi, I found something interesting while messing with detect life, the script I put on it was called for every actor. So if you need to call a script on all the actors around you, you could use a magic effect that has the OnHit event in it. I don't know however if the successful-strike-or-not is going to work since by that time you've already hit them.. You also have to consider the complexity and extra load thats going to be created by running this script on multiple actors.

Event OnEffectStart(Actor caster, Actor target);This condition is only needed if you are giving the effect by hitting them with something, and only want it to run once  if target.HasMagicEffect(thisLifeDetectSpell);the life detect effect would be running on them while they're in the area of effect and shouldnt run twice    GotoState("nullstate")    Dispel()  elseif    ;your code  endifEndEventstate nullstate;define all your events in here null in case they get throughendstate

^^^ this is complete pseudo-code I have to look up every function before I use it because Papyrus has weird grammar >


Anyways, hopefully you can get something out of that mess

edit: Actually you probably don't even need that check to see if the effect is active, and it might it to dispel itself over and over if used...