User:JRoush

Notes on Scripting

General Scripting

Adding or removing (possibly any modifying of) effects in an enchantment (or, presumably, a spell) that is currently affecting an actor results in CTD. Instead, we must cloneform the enchantment and use that instead. Previous testing gives me hope that the game might garbage collect unused formids.

Modifications to non-cloned forms (e.g. changes to name, etc) do not appear to stick upon reloading the game. Dynamically generated spells must be cloned, or else the base forms modified in script every time the game is reloaded.

Cloned forms are not removed when the mod is deactivated. Since there is no way for the average player to remove cloned spells from spell merchants, a "cleanup" script must be provided to do so. - makes the whole use of cloned spells unattractive -

GetOwner appears to work only on references (not items in a container). There is a stolen flag, I believe, but not sure how to set it.

Moveto and PositionCell don't transfer meshes. the 'usual' workarounds assume transfer to the current cell, and don't work for destination cells that aren't loaded.

Using GetIconPath on an object with no icon causes a CTD.

Menu Scripting

Traits of the form <user#> are parameters set by the game enigne. The visible manifestations (text, slider position, etc.) are usually set to derive from these inputs. As of OBSE v0017 modifying most traits from scripts will destroy derivative relationships; it appears that some values (e.g. quantity slider traits) are safe to modify. Modifying the <user#> traits directly one can "fake" user input; in particular spell/potion names and slider bar positions. Derivative relationships are reloaded when the menu is. Note that the HUD (and possibly the inventory) reloads only after exiting to the main menu; changes to the HUD will persist until then.

The Arrow + Enter keys can normally be used to navigate menus. I haven't found (or seriously looked for) a way to determine which tile is the focus of a keyboard event. It looks like the focus is *either* keyboard or mouse based, and transitions from one to the other are inconsistent or bugged. At any rate, OBSE v0017 GetActiveUIComponent* functions work only for tiles focused on by the mouse. Also, arrow+enter menu navigation is NOT based on mapped controls and cannot be disabled using Disablekey. It CAN be disabled by removing all traits of the form <xbutton>, <xleft>, <xright>, etc. from the menu in question, but not by simply setting them to zero in scripts. This is a problem because an errant keystrokes can apparently derail a ClickMenuButton call, which makes setting up long chains of automated click events unfeasible.

The GetCursorPos function is a bit dodgy. Returned positions are not consistent, and seem to depend on integrated movement history. This, combined with the lack of a function to get screen resolution, makes it impractical for use in menus (specifically, I couldn't use it to script in a custom slider bar).

Actor Value Mechanics (Revised)

There are six factors that contribute to an Actor Value:

• Base - the AV value from the Actor's base form - all instances of the actor share this value (e.g. all guards share the same Base Health). This factor is set by the designer in the CS. It is modified in-game by the SetAV console+script commands, and by 'recoverable' effects on Ability-type spells.
• Calculated Base - the contribution to an AV from other AVs and game settings. For example, the Calculated Base for the player's Health is fPCBaseHealthMult * Endurance. This factor is nonzero only for the player character - NPC and Creature health, to use the same example, do not depend on their endurance.
• Calculated Multiplier - a multiplier to the AV from other AVs and game settings. This factor is almost always 1.0; the exception is the Magicka Multiplier for the player character.
• Max Modifier - for Actors with middle process or higher. This factor is modified by 'recoverable' effects such as Fortify,Drain,Feather,etc on non-Ability-type spells.
• Offset Modifier - for all Actors. This factor is doesn't seem to be used by the combat or magic systems. It is modified only by the ModAV and ForceAV script commands (not the console versions).
• Damage Modifier - for Actors with low process or higher. This factor is modified by the ModAV and ForceAV console commands, by direct damage from combat, falling, lava, etc., and by 'nonrecoverable' effects like Damage, Restore, etc.

There are three different 'versions' of an Actor Value that play a role in Oblivion:

Calculated Base Value = (Base + Calculated Base) * (Calculated Multiplier)
    Maximum Value     =  Calculated Base Value + Max Modifier
    Current Value     =  Maximum Value + Offset Modifier + Damage Modifier

• Calculated Base Value - the "base" value returned by the GetBaseAV console+script commands. This value is used quite in basic skill checks