Leecarter

There's probably a way - find a mod that's doing what you're trying to do and see how they did it. 50% of programming is copy/paste.

Yup, kind of the point of the mod - no weapons. Same principals should apply though.

Sure. First you cast the weapon as a Form object. Pass (true) in GetEquippedWeapon() if you want the one in the left hand: form theWeapon = theTarget.GetEquippedWeapon() as Form Then you load up the shader (I've never used shaders, but I'm assuming they work the same) theEffect = *your scripts variable" Then call play: theEffect.Play(theWeapon) Again, I've never worked with shaders, but this is how I would do a VisualEffect or ImpactDataSet so *maybe* they work the same.

I do stuff like this multiple times in my mod's scripts. Download it and search the script source for "GetEquipped" and "Play". Should answer all your questions. http://skyrim.nexusmods.com/downloads/file.php?id=13281

Thanks! Even if you don't care to play the mod you may enjoy browsing the scripts.

I think it came out pretty well: http://www.youtube.com/watch?v=3gKkN9Af7vg

Yeah it's a config problem with your compiler, not the script itself.

I found a way to do it by over-riding the inheritance of ObjectReference, creating properties in the new higher class, and then injecting variables from the local player script into the new top level script. After the variables are injected by an event on the player (I used OnHit()) they will be available everywhere in any script using Game.GetPlayer().MY_NEW_VARIABLE. Incorporated this into my first mod here: http://skyrim.nexusmods.com/downloads/file.php?id=13281 There are 3 scripts, all beginning with "GM_".

I should clarify this a little more. I have a quest set up that contains the variable in a script property - added a quest property to the actor's script - populated the property for the actor with the quest in the CK. That works fine for accessing and persisting objects for the player, but I want something truly global. So let's say I want to access an object from *any* script. Maybe this isn't even possible?

I know there are global variables you can create in the CK, but they're limited only to 3 numeric datatypes. What I'm looking for is a way to make objects available globally. I've read this is possible by creating a quest that runs on start, then attach a script with the properties you want to make accessible globally. This directions I've found online to do this thus far haven't worked (or I did it wrong). For example, one of the things I'd like to have globally accessible is a VisualEffect property, but this could apply to perks, weapons, or whatever else you wanted to use as a property in your scripts. Has anyone here used this approach for creating global properties?

Not 100% sure I understand what you're asking. Everything I've seen so far with Papyrus is event driven, so I'm not sure you can create a script and have it run without something "telling" it to run. How often does that piece of script need to run?

Also, I noticed you forgot to set Guardian = "Warrior" in addSign1. Another possible refactor might look something like this:

Also maybe structuring it like this would help make it clearer? At work and just did this in textpad real quick, but just to get the general idea:

Hmm, total newbie at Papyrus and just a stab here, but I would guess it has something to do with the doOnce variable. doOnce is initalized as true. If it enters the first wrapping IF statement but then never triggers any of the nested IFs it will stay false, so the next time it's called it never passes the first condition. Is it possible it got called earlier and flipped doOnce to false?

Solution: echo pointed me in the right direction when he mentioned ObjectReference. Thanks. The way I'm understanding it, that perk scripts must extend Perk, and since Perk does not have access to OnHit() it wouldn't bind correctly (just like the error above said).