In a quest script, I can call:

Game.GetPlayer().SetAV ("Magicka", 200)

And when the script runs, if I do player.getBaseAV Magicka from console, it returns 200, even after save/load.

But then when I call

Game.GetPlayer().SetAV ("MagickaRate", 0.01)

the new Actor Value takes effect for the current game session, but does not "stick" past save/load; if I immediately do player.getbaseav MagickaRate, I receive 0.01. But if I save and load, MagickaRate goes back to the default value (3.00).

I know I could use a hidden perk or somesuch to accomplish this, but I'm curious as to why one change sticks through save/load and another does not.

SetAV has never persisted past a single session. If you want a permanent change, you'll have to use ModAV instead.

Cool, another way to make an onload check .

Please read my original post. SetAV persists just fine for Magicka (or health or stamina for that matter). Just not for MagickaRate.

Other values do stick it seems. The below works with "MagickaRate", but not "Health".

Bool Function bGetGameLoaded(Actor akActor = None)	If akActor.GetActorValue("EnduranceCondition")		akActor.SetActorValue("EnduranceCondition", 0)		Return True	Else		Return False	EndIfEndFunction 

Values that don't stick:

• Aggression
  
• Assistance
  
• BowSpeedBonus
  
• BrainCondition
  
• CarryWeight
  
• Confidence
  
• CritChance
  
• DamageResist
  
• EnduranceCondition
  
• EquippedItemCharge
  
• EquippedStaffCharge
  
• HealRate
  
• InventoryWeight
  
• LeftAttackCondition
  
• LeftMobilityCondition
  
• MagickaRate
  
• Mass
  
• MeleeDamage
  
• Mood
  
• Morality
  
• NormalWeaponsResist
  
• PerceptionCondition
  
• RightAttackCondition
  
• RightMobilityCondition
  
• SpeedMult
  
• StaminaRate
  
• UnarmedDamage
  
• VoiceRate

Also of interest:

[04/24/2012 - 11:40:50PM] error: Actor value "NormalWeaponsResist" does not exist.[04/24/2012 - 11:40:51PM] error: Actor value "EquippedItemCharge" does not exist.[04/24/2012 - 11:40:51PM] error: Actor value "EquippedStaffCharge" does not exist.

Probably means that some AVs are computed instead of stored -- explains everything.
Damn, the wiki is lacking... Looks like Justin already added some notes, nice.

Very curious. I resolved it by a workaround, but good to know.