behippo Posted November 10, 2015 Share Posted November 10, 2015 (edited) Website: http://f4se.silverlock.org/ The Fallout 4 Script Extender, or F4SE for short, will be a modder's resource that expands the scripting capabilities of Falout 4. It will do so without modifying the executable files on disk, so there will be no permanent side effects. The xSE team has returned to try our hand at the next great Bethesda game. We have produced the Skyrim Script Extender (SKSE), New Vegas Script Extender (NVSE), Fallout Script Extender (FOSE), and originally the Oblivion Script Extender (OBSE). We can't wait to help produce tools for the best mods for Fallout 4. Now that Fallout 4 is released in the US we have started our work. We'll keep everyone informed as to our progress. This is an incredibly early release, so please keep in mind that there is only extremely limited functionality provided by this version of F4SE, that we can't offer technical support for it, and that literally anything about it can change in the future. This is being released primarily to test against a wider audience and hopefully help some people out at the same time. Fallout runtime 1.4.132: Use F4SE 0.1.8. whatsnew: 0.1.8: - support for untime 1.4.132 - more internal class decoding 0.1.7: - support for beta runtime 1.4.131 - more internal class decoding 0.1.6: - support for beta runtime 1.4.125 - internal tools updates - more internal class decoding (inventory, input, netimmerse skin) 0.1.5: - support for runtime 1.3.47 - initial game menu support and utilities - more internal class decoding 0.1.4: - support for beta runtime 1.3.45 - enable logging from scaleform. add bEnableGFXLog=1 to the [interface] section of your f4se.ini. create it if it doesn't exist. - hook global scaleform tint functions to allow interface mods to selectively modify tint colors/intensities - initial scaleform native plugin API - more internal class decodingBethesda has hinted that additional updates will be coming more shortly than normal, so please be prepared for another update on our end to be needed when that happens. Also, the embedded CustomControlMap.txt has changed again, so people using custom versions will need to update that as well (mainly by removing the up/down/left/right block). 0.1.3: updated for 1.2.37 runtime 0.1.2: - updated for 1.2.33 runtime 0.1.1: - fixed crash when resetting keybindings from ui 0.1.0: - everything - plugin manager - simple hooks for papyrus, scaleform, and the classic script system, but nothing useful for modders yet - customization of internal keymappings Copy CustomControlMap.txt to Data\F4SE\CustomControlMap.txt. Edit that file to set your bindings. The format is the same as Skyrim, it's a space-separated file. The first column is the name of the internal keybind. The second column is the keyboard scan code that should activate the bind in hex, or 0xFF if unbound. Use google to find a table of scan codes. The third column is for mice, the fourth for controllers. The next three columns control whether or not a control should be written to the user's config file. The final column specifies which input layer the bind is associated with - you will probably not want to change that. - currently-installed version of F4SE is shown in the Settings menu next to the game version - running GetF4SEVersion from the console will print the current version as well - log spam is written to My Documents\My Games\Fallout4\F4SE\When testing the control map, note that many of the control labels in the UI are hard-coded. Changes to the control map will be functional, but might not show up in the UI. Also, previously customized keys overwrite settings in the control map. You may need to delete My Documents\My Games\Fallout 4\ControlMap_Custom.txt or pick "defaults" from the in-game keybinds menu. This is a list of DirectX keyboard scan codes. As a first taste we do have a BA2 Extractor to unpack the new BA2 package format of Fallout 4. Download it at: fallout4_tools_0001.7z It is a command line tool that will extract the contents of a given ba2 to a specified folder. Edited February 29, 2016 by behippo Link to comment Share on other sites More sharing options...
MrsHandy Posted November 10, 2015 Share Posted November 10, 2015 Yes! Thanks to you all for getting right to work on the script extender! I, for one, am excited to see what becomes of it! Link to comment Share on other sites More sharing options...
Tilarium Posted November 10, 2015 Share Posted November 10, 2015 Thanks for confirming that it'll be worked on! The script extender is without a doubt the most usefull mod (or tool) for Bethesda games because without it we can't have so many of the other great mods that get made. Link to comment Share on other sites More sharing options...
DServant Posted November 10, 2015 Share Posted November 10, 2015 (edited) Thanks, works for me. Planning to do some animations soon. Edited November 10, 2015 by DServant Link to comment Share on other sites More sharing options...
CreepaCatcha Posted November 10, 2015 Share Posted November 10, 2015 Noob here, just drag the src folder into the fallout directory to install? Link to comment Share on other sites More sharing options...
DServant Posted November 10, 2015 Share Posted November 10, 2015 Noob here, just drag the src folder into the fallout directory to install?No. You can just extract the 7z, shift + right-click on the "0001" folder inside "fallout4_tools_0001", and select "Open command window here". Then you can run the executable in cmd like this: ba2extract.exe "C:\Steam\SteamApps\common\Fallout 4\Data\Fallout4 - XXXXXXXX.ba2" "C:\Steam\SteamApps\common\Fallout 4\Data\XXXXXXXX\". Replace XXXXXXX with whatever ba2 you want. Your steam folder is probably in a different location so don't use this verbatum. The destination folder can be anywhere too. Link to comment Share on other sites More sharing options...
CreepaCatcha Posted November 10, 2015 Share Posted November 10, 2015 Noob here, just drag the src folder into the fallout directory to install?No. You can just extract the 7z, shift + right-click on the "0001" folder inside "fallout4_tools_0001", and select "Open command window here". Then you can run the executable in cmd like this: ba2extract.exe "C:\Steam\SteamApps\common\Fallout 4\Data\Fallout4 - XXXXXXXX.ba2" "C:\Steam\SteamApps\common\Fallout 4\Data\XXXXXXXX\". Replace XXXXXXX with whatever ba2 you want. Your steam folder is probably in a different location so don't use this verbatum. The destination folder can be anywhere too. Cheers Link to comment Share on other sites More sharing options...
mcguffin Posted November 10, 2015 Share Posted November 10, 2015 Thx for the quick ba2 tool ^^However the 0002 version seems to not work for me. (windows7 64)It opens 3 instances of the process and nothing happens (Windows Explorer crashed one time, also) Link to comment Share on other sites More sharing options...
RoyBatterian Posted November 10, 2015 Share Posted November 10, 2015 I too am excited. Thanks for the ba2 extraction tool so soon. Will you be asking for a wish list again for commands? Link to comment Share on other sites More sharing options...
TomSawyer Posted November 10, 2015 Share Posted November 10, 2015 Praise the xSE team for all their work! Link to comment Share on other sites More sharing options...
Recommended Posts