runtime database

Tired of minor Fallout 4 updates breaking your F4SE plugin? The runtime database helps compatible modules continue to work in OG, NG and AE without waiting for new address libraries.

Original address:

If you are looking for direct help, information, patches, unreleased

mods, pre-release mod updates, or just want to chat and share

Pictures and videos of your adventures, welcome to join us!

Welcome to support me and get more exciting modules!

Runtime database

a database. Original, NG and AE. Designed to accommodate updates.

New compatibility base for Fallout 4 F4SE plugin.

What is a runtime database?

The F4SE plug-in requires specific parts to be found in Fallout 4 in order to work. When Bethesda updates the game, these parts can be moved around, even if their actual purpose doesn't change.

This is also one of the main reasons why the F4SE plug-in suddenly fails after the game is updated.

Runtime databases are designed to reduce this problem.

Rather than just relying on where a specific game version was created, the runtime database is able to identify and locate game functionality that compatible plug-ins require when Fallout 4 launches.

This allows the same database and compatible plugins to be used across multiple different Fallout 4 runtime series

Running: • OG — Fallout 4 1.10.163

• NG — Fallout 4 1.10.984
• AE — Fallout 4 1.11.x, including 1.11.221 and 1.11.240

The runtime database automatically detects which runtime family you are using. You do not need to select or configure a database separately for the game version.

In the best-case scenario, future Fallout 4 updates will likely arrive and compatible add-ons will continue to work normally. No new runtime database or new version of each plugin required.

What's so special about this?

Fallout 4 currently has several significantly different runtime generations. Supporting vanilla, Nova, and AE with the same plugin usually requires additional work for each modder.

The runtime database provides a shared compatibility layer across three generations.

For players, this means:

• A runtime database installation covering vanilla, NG and AE
• No need to manually select the exact version

of Fallout 4 Database • Due to internal location relocation

Reduced plug-in corruption • Better compatibility with future updates

• Easier support for mod authors and mod lists

The goal is not just to support a current version of Fallout 4. The goal is to make compatible plugins less dependent on having the exact same version of the game.

How is it different from the address library?

A traditional address library is like a map created for a version of Fallout 4. If Bethesda tweaks a map, it usually needs to be re-created for the new version.

The runtime database is more like a search system. It knows what compatible plugins are looking for and can find it in the currently running game.

Simply put:

Address library: "The required functionality is at this exact location."

Runtime database: "This is a required function to find its current location."

It's this difference that allows plugins to survive minor Fallout 4 updates without being rebuilt or updated.

What will happen with future updates to Fallout 4?

Compatible plugins will attempt to locate all required devices via the runtime database when the game starts.

If the required parts of the game are still present and identifiable, the plugin will continue to work without updating.

If Bethesda fundamentally changes or removes something that a plugin depends on, the plugin or runtime database may still need to be updated.

The runtime database does not guarantee that every future update will be harmless, but it greatly reduces the number of changes that automatically break compatible plugins.

Who needs it?

This module mainly relies on the F4SE plug-in built by Runtime Database / CommonLibF4RD.

If other mods require a runtime database, install it using your mod manager and keep it updated.

R …