Developing SDK Mods

Work in progress

Setting up your Workspace

  1. Create a new folder to develop your mods within. The mod manager supports loading from multiple mods folders, so you can keep the mods you’re developing separate.

  2. Open up OakGame\Binaries\Win64\Plugins\unrealsdk.env, and add the following lines: 
    • OAK_MOD_MANAGER_EXTRA_FOLDERS=["C:\\path\\to\\new\\mod\\folder"]

      This is a json list of paths to extra mod folders, you can append more - though note it must stay on a single line.

    • UNREALSDK_LOG_LEVEL=DWRN

      This sets the default log level to developer warning. This will print some extra log messages to console, which are relevant for developers, but which we don’t want normal users to worry over.

    • PYUNREALSDK_DEBUGPY=1

      This enables debugpy support, which will let you properly attach a debugger.

    Note that the mod manager download contains this file, so when updating you need to be careful not to overwrite it/to restore it afterwards.

  3. Download the latest version of debugpy, and extract to one of your mods folders such that it’s importable. The mod manager initialization script will automatically import it and start a listener.

  4. Extract the default .sdkmods, so you can see all the raw python source files (and so your IDE can parse them).

    Mods are generally released as a single .sdkmod file, since this helps prevent a lot of mistakes casual users might make while installing, but this is unsuitable for development.

    .sdkmod files are all just renamed zips, open them in any archive program and extract the inner folders back into the mods folder - go from sdk_mods/my_mod.sdkmod/my_mod/* to just sdk_mods/my_mod/*.

    Note that if you have both an extracted folder and a .sdkmod with the same name, the folder takes priority.

  5. Point your IDE at the other mods folders, so it can follow imports. This should be the base sdk_mods folder, and the sdk_mods/.stubs folder for the native modules.

    • In vscode, add to the python.analysis.extraPaths option.

  6. Configure your debugger for remote debugging, attaching to localhost:5678.

    • In vscode, use the Python: Remote Attach template.

    After doing this, launch the game and make sure you can attach.

After finishing setting up, try take a quick read through the base sdk mod files and the stubs. They are all filled with all sorts of type hints and docstrings, which should help explain a lot about how the SDK works.

Adding to the Mod DB

The DB primarily sources info from your mod’s pyproject.toml. With a well configured pyproject, all you need to do is point the DB at it, and everything will be extracted automatically. To do this, add a file for your mod to the _mods/ dir of this repo, and add the front matter variable pyproject_url, pointing at an auto updating link.

---
pyproject_url: https://raw.githubusercontent.com/apple1417/oak-sdk-mods/master/abcd/pyproject.toml
---

You can overwrite your mod’s description simply by adding some extra content to the page. You can use this to embed images or videos, which wouldn’t be suitable for the in-game mod description.

You can overwrite some of the other info on the page by setting various front matter variables.

Field Front matter pyproject.toml
Title title tool.sdkmod.name, project.name
Author(s) author project.authors[n].name1
Latest Version version tool.sdkmod.version, project.version
Supported Games2 supported_games tool.sdkmod.supported_games
License3 license tool.sdkmod.license, project.license.text4
Requirements dependencies project.dependencies
Misc URLs5 urls project.urls
Download Link download tool.sdkmod.download
Description The page contents project.description6

1 Multiple authors are concatenated in the order given.
2 An array of strings, with valid values of BL3 and WL (case insensitive). If not given, defaults to all games.
3 A table with keys name and url. Prefer linking to a summary site, rather than direct to your LICENSE.
4 Used as the name, with no url.
5 A dict where keys are the names and values are the urls.
6 HTML tags are stripped, rather than just being escaped.

Updating Info

While this site is statically generated, every time a mod page is loaded it fetches the pyproject and updates the page with any changes, the values fetched when the site is generated are only used as defaults (note that front matter overrides still take priority). This means you generally don’t need to touch the db again, changes will be picked up automatically.

There are a few exceptions to this, which are not automatically updated:

  • The title used in the sidebar and tab title (the header on the mod page does get updated).
  • project.name, which is used for matching dependencies to their mod page.
  • The data powering the searchbar.
  • The fields which are always displayed will not be set to unknown if you completely delete their section in your pyproject, the old data is preferred. Requirements and Misc URLs are already hidden when not in use, so the updates will delete them.

If you make significant changes to your pyproject, it may be worth kicking off another build to update the static versions of these. Do note that this data is updated anytime the site is generated, someone else adding an unrealated mod will update yours.