Ahoy

As part of a dungeon making a unique weapon with a special power attached to it.

Simple script yet it won't work, not sure why, hoping you could help.

Scriptname ilsebonecallerabilityscript extends ObjectReference  {Spell Property 0ilseBonecallerAbility autoEvent OnEquipped(Actor akActor)	if (akActor == Game.GetPlayer())		Game.GetPlayer().AddSpell(0ilseBonecallerAbility)	endifEndEventEvent OnUnEquipped(Actor akActor)	if (akActor == Game.GetPlayer())		Game.GetPlayer().RemoveSpell(0ilseBonecallerAbility)	endifEndEvent}

Its super simple, I am not sure why it wouldn't be working, *shrug*

Try removing " } " from the end of the script.

compilation error.

...and the '{' from the beginning.

I did that as well, and again, returned a compilation error.

You can't name properties/variable with digits as the first character, so kill the '0'. http://www.creationkit.com/Identifier_Reference

ScriptName ilsebonecallerabilityscript Extends ObjectReference  Actor Property PlayerREF Auto ; 1,000 time faster than Game.GetPlayer(), literallySpell Property IlseBonecallerAbility AutoEvent OnEquipped(Actor akActor)	If akActor == PlayerREF		PlayerREF.AddSpell(IlseBonecallerAbility)	endifEndEventEvent OnUnEquipped(Actor akActor)	If akActor == PlayerREF		PlayerREF.RemoveSpell(IlseBonecallerAbility)	EndIfEndEvent

Hm, well I made the changes and it still doesn't work, also not using brackets to organize things will drive me crazy >.>

Hmmm... What I posted compiles. Post the current version? Brackets are for comments in Papyrus, so...

Oh the version you posted compiles fine, it simply doesn't work >.<

Sorry I should have been more specific.

Make sure, in the object which the script is attached to's scripts window, that the properties are filled. You'll have to remove the '0' from the EditorID of your spell too that it's name will match the property name or it won't auto-fill.

Yeah I had already done that, still no such luck, irritating >.<

ScriptName ilsebonecallerabilityscript Extends ObjectReference  Actor Property PlayerREF Auto ; 1,000 time faster than Game.GetPlayer(), literallySpell Property IlseBonecallerAbility AutoEvent OnEquipped(Actor akActor)        If akActor == PlayerREF               Debug.Notification("OnEquipped")                PlayerREF.AddSpell(IlseBonecallerAbility)        endifEndEventEvent OnUnequipped(Actor akActor)        If akActor == PlayerREF                Debug.Notification("OnUnequipped")                PlayerREF.RemoveSpell(IlseBonecallerAbility)        EndIfEndEvent

Check to see if the notifications show? This is attached to an apparel item?

its attached to a weapon, i'll test the debugs, but I am fairly sure its the scripting not the spell (already tried substituting it for a vanilla ability)

notifications didn't show blargh

Hmmm... Remove the script from the weapon and reattach it, then refill the properties making sure they're pointed where they ought to be. Both should auto-fill if you've removed the 0 from the spell's Editor ID.

Look at your properties. You're treating PlayerREF as an Actor. If you want to use a Quest alias, use ReferenceAlias; it's more reliable and good practice.

After doing that it started working, strange why it didn't work before, but whatever, it works now, and that is what matters.

Now I just have to deal with the fact that the player can simply unequip and re-equip to reuse the ability over and over...*sigh* but the scripting issue is over and done with that's what is important.

PlayerREF is an Actor... As JustinOther mentioned in the comment in his code, that is the most efficient way of referring directly to the player. There's no reason to use a ReferenceAlias for it here if you mean to always refer to the player.

Cipscis