This wiki is a copy of the original Oblivion CS wiki created and maintained by the UESP.net. See CSwiki:Copy Notice for more info.

Difference between revisions of "Category:Oblivion Script Extender"

Jump to navigation Jump to search
formatting, added an example for using the -editor tag.
imported>Raziel23x
(Update)
imported>DragoonWraith
(formatting, added an example for using the -editor tag.)
Line 33: Line 33:
#Copy obse_1_1.dll, obse_1_2.dll, obse_1_2_416.dll, obse_editor_1_0.dll, obse_editor_1_2.dll, and obse_loader.exe to your Oblivion directory.
#Copy obse_1_1.dll, obse_1_2.dll, obse_1_2_416.dll, obse_editor_1_0.dll, obse_editor_1_2.dll, and obse_loader.exe to your Oblivion directory.
#Run oblivion by running obse_loader.exe from the Oblivion directory.
#Run oblivion by running obse_loader.exe from the Oblivion directory.
#Scripts written with these new commands must be written via the TESConstructionSet launched with obse_loader. Open a command prompt window, navigate to your oblivion install folder, and type "obse_loader -editor". The normal editor can open plugins with these extended scripts fine, it just can't recompile them and will give errors if you try.
#Scripts written with these new commands must be written via the TESConstructionSet launched with obse_loader. Open a command prompt window, navigate to your oblivion install folder, and type "obse_loader -editor". The normal editor can open plugins with these extended scripts fine, it just can't recompile them and it will give errors if you try.
 
Example Target box for a shortcut to the editor:
"C:\Program Files\Bethesda Softworks\Oblivion\obse_loader.exe" -editor
 
This would be what the Target box would say if you had a default install of Oblivion.
|-
|-
!style="background:#ffdead;border-bottom:1px solid;"  width="100"  | Suggestions for Modders
!style="background:#ffdead;border-bottom:1px solid;"  width="100"  | Suggestions for Modders
Line 41: Line 46:
When your mod loads, use the command GetOBSEVersion to make sure a compatible version of OBSE is installed. In general, make sure you're testing for any version later than the minimum version you support, as each update to OBSE will have a higher version number. Something like:
When your mod loads, use the command GetOBSEVersion to make sure a compatible version of OBSE is installed. In general, make sure you're testing for any version later than the minimum version you support, as each update to OBSE will have a higher version number. Something like:


if GetOBSEVersion < 5 then
if GetOBSEVersion < 5 then
  MessageBox "This mod requires a newer version of OBSE."
  MessageBox "This mod requires a newer version of OBSE."
endif
endif


Another alternative that is even more user-friendly is releasing your mod as an OMOD, and adding a script to check the version when installing the mod:
Another alternative that is even more user-friendly is releasing your mod as an OMOD, and adding a script to check the version when installing the mod:


IfNot ScriptExtenderNewerThan #.#.#.#
IfNot ScriptExtenderNewerThan #.#.#.#
    Message "Requires Oblivion Script Extender v#### or greater"
  Message "Requires Oblivion Script Extender v#### or greater"
    FatalError
  FatalError
EndIf
EndIf


|-
|-

Navigation menu