Difference between revisions of "Talk:Object Mod"
imported>Google12 m (Provided evidence on what happens when multiple mod associations are provided.) |
imported>Google12 m (Added results of my unsuccessful priority tests) |
||
| Line 1: | Line 1: | ||
The editor dialog image has a non-neutral background. Should be fully cropped or the creation kit background color.--[[User:Scrivener07|Scrivener07]] ([[User talk:Scrivener07|talk]]) 2016-07-17T21:20:39 (EDT) | The editor dialog image has a non-neutral background. Should be fully cropped or the creation kit background color.--[[User:Scrivener07|Scrivener07]] ([[User talk:Scrivener07|talk]]) 2016-07-17T21:20:39 (EDT) | ||
Regarding Target Object Mod Association Keywords. I added the information regarding what happens when multiple keywords are provided based on the following observation. I had an OMOD targeted to a piece of lite armor and it worked fine. I later added a second keyword for heavy armor, hoping it would make the mod available to both but instead, it became available to neither. I removed the lite keyword, which made then item available to the heavy armor and applied the omod to the heavy armor. I | Regarding Target Object Mod Association Keywords. I added the information regarding what happens when multiple keywords are provided based on the following observation. I had an OMOD targeted to a piece of lite armor and it worked fine. I later added a second keyword for heavy armor, hoping it would make the mod available to both but instead, it became available to neither. I removed the lite keyword, which made then item available to the heavy armor and applied the omod to the heavy armor. I then re-applied the lite keyword. In game, the mod remained attached to my heavy armor but when i checked in the workbench, it was grayed out (meaning it was no longer available). [[User:Bug64]] 2017-01-08 | ||
I'm not sure what priority does. At first I thought it controlled the order in which OMODs are applied, but i did a test where I applied 2 conflicting OMODs to a piece of armor. Only the first one took effect. I changed the priority both ways (mod1>mod2 and mod2>mod2) but there was no impact. I also checked to see if it impacted the order in which the OMODs appeared at the workbench, but no change their either. So, not sure what it does. [[User:Bug64]] 2017-02-07 | |||
Revision as of 17:52, 7 February 2017
The editor dialog image has a non-neutral background. Should be fully cropped or the creation kit background color.--Scrivener07 (talk) 2016-07-17T21:20:39 (EDT)
Regarding Target Object Mod Association Keywords. I added the information regarding what happens when multiple keywords are provided based on the following observation. I had an OMOD targeted to a piece of lite armor and it worked fine. I later added a second keyword for heavy armor, hoping it would make the mod available to both but instead, it became available to neither. I removed the lite keyword, which made then item available to the heavy armor and applied the omod to the heavy armor. I then re-applied the lite keyword. In game, the mod remained attached to my heavy armor but when i checked in the workbench, it was grayed out (meaning it was no longer available). User:Bug64 2017-01-08
I'm not sure what priority does. At first I thought it controlled the order in which OMODs are applied, but i did a test where I applied 2 conflicting OMODs to a piece of armor. Only the first one took effect. I changed the priority both ways (mod1>mod2 and mod2>mod2) but there was no impact. I also checked to see if it impacted the order in which the OMODs appeared at the workbench, but no change their either. So, not sure what it does. User:Bug64 2017-02-07