Difference between revisions of "User:JRoush"

<p>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. </p>

<p>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. </p>

<p>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.</p>

<p>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.</p>

<p>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.</p>

<p>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.</p>

<p>  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.</p>

<p>  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.</p>

<p>  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.</p>

<p>  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.</p>

<p>  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). </p>

<p>  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). </p>