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 http://skse.silverlock.org, http://nvse.silverlock.org, http://fose.silverlock.org, and originally the http://obse.silverlock.org. 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.

Edit:
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 4 runtime 1.1.30: Use http://f4se.silverlock.org/beta/f4se_0_01_01.7z.
Fallout 4 runtime 1.2.33: Use http://f4se.silverlock.org/beta/f4se_0_01_02.7z.

whatsnew:

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 https://msdn.microsoft.com/en-us/library/windows/desktop/dd375731(v=vs.85).aspx.



As a first taste we do have a BA2 Extractor to unpack the new BA2 package format of Fallout 4. Download it at: http://f4se.silverlock.org/beta/fallout4_tools_0001.7z
It is a command line tool that will extract the contents of a given ba2 to a specified folder.

And here is a screenshot of F4SE running for the first time: http://f4se.silverlock.org/F4SE_Splash.jpg (Thursday Nov 12 midnight). We've got a long way to go, but we are off to a good start.

This is great news. I look forward to it.

Awesome. I have an idea for one of the first plugins.. double mouse cursor fix :/

Here is a mod idea. Better Housing placement.

I love you guys! Being capable of unpacking so I can fix the keybindings...I love you...

as always, you guys rock! thanks for the archive unpacker! Can't wait for the script extender (and FO4edit).. this is going to be fun

I hope that ba2 format will be documented somewhere.

How do you do that with just the archive unpacked?

I hate that throw grenades and melee attack are GLUED onto the same button.

Thanks guys

can't wait!

Much love to all of you for all the work you put in

Thank you for giving us such an early start with the ba2 archives.

in the readme of the extractor you state

"Please note that the values in the DDS header are not present in the original texture archive, and were chosen for compatibility rather than accuracy. Color textures are accurate, but DXGI_FORMAT_BC5_UNORM (normal maps) and DXGI_FORMAT_BC7_UNORM are definitely wrong."

so it is clear that something is not quite right with the normals .. but i dont exactly know what this means in terms of how to "fix" it. All of the extracted normals are "visually corrupt" for lack of better description. They all open just fine, but they have high amounts of pixelation and artifacting, and the typical color palette used in normals is not quite right (the colors more cloesly resemble a model space normal), which im sure you know. My question is, is this something that just needs to be altered in extractor program and will be updated as you all continue working on it, or is this something that modders will need to fix ourselves once we have extracted the files from the archive (for example, by manually editing the file headers)? Cheers

Unpack the archives, find the ControlMaps.txt (or whatever related file), go to Skyrim Nexus to download an example, and edit the controlMap.txt according to it.

You might need to use a HexEditor. The ControlMap.txt in MyGames can't be used...unless they've changed it from previous titles.

Thank you guys! Your work has always been invaluable!

And that was a fast release - was it that fast for FO3 and FNV? Was the vanilla script the same as the previous games? Any changes worth mentioning?

Oh god yes! Please add a setting to adjust the iron sights sensitivity. Oh, and a toggle for ADS would be awesome too.

As usual, modders doing BGS's work.

The (not longer existing) bsa format for archives was the same in FO3 & NV also DDS. So there weren't any (at least not much) changes needed to existing tools. But yes that was fast and great.

These are the people who we mod developers rely on. So please think about donations (with absolut no obligations clearly). When we don't want paid mods we should more thinking of establishing a donation culture. It works for youtube and streams. I do my bit (as acknowledgement for making the NIF Blender export tools for FO3/NV, none of my new armors and meshes would have been possible without them) very soon.

You guys!

Time to start exploring those BA2s... wonder if changes will be picked up automagically, or is some sort of ini tweak/archive invalidation required?

you guys are awesome

Thank youuuuuuuuuuuuuu!!! *Wags tail furiously*.

Badass

For anyone wondering how to use this unpacker, I'm quoting DServant from the Nexus forums...

ba2extract c:\OrgFiles\"Fallout4 - Interface.bsa" c:\OrgFiles

"Fallout - *"