Skip to content
This repository was archived by the owner on Aug 13, 2026. It is now read-only.

About

Satisfactory 1.2 mod: separate hotkeys for equipping the Jetpack, Hover Pack and Parachute

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

9 Commits

Folders and files

Repository files navigation

Pack Hotkeys

Hotkeys for the back equipment slot in Satisfactory 1.2, instead of opening the inventory and dragging items around.

Key Action
F1 Toggle Pack — equips the Jetpack, or swaps between Jetpack and Hover Pack when one of them is worn
F2 Equip Parachute

With an empty back slot (or the parachute on it), F1 puts on the Jetpack, falling back to the Hover Pack if you are not carrying one. If you do not carry the other pack, the current one stays on.

Important

Unmaintained. This was a weekend project, built because no updated mod covered the back equipment slot on 1.2. It works — see Releases for a ready-to-use Windows build — but it will not be updated when the game changes, and it is not published on ficsit.app, so the Mod Manager will not install or update it.

The repository is archived and read-only. Fork it freely — MIT licensed. If you want to publish it on the Mod Repository under your own name, go ahead, no need to ask.

Verified working on Satisfactory 1.2.4 (CL 502094) with SML 3.12.0, built against the 1.2.0 headers (CL 495413).

What it does

To equip a pack, the mod:

  1. checks whether that kind of pack is already worn — then nothing happens, or it is put away if bUnequipWhenAlreadyEquipped is enabled;
  2. makes it the active one if it already sits in the back slot inventory;
  3. otherwise moves the first matching item from the player inventory into the back slot, swapping out whatever was there.

Matching is done on the native equipment classes AFGJetPack, AFGHoverPack and AFGParachute, so modded packs deriving from them are picked up as well.

Installing

The Mod Manager cannot install this mod — it is not on the Mod Repository. Install by hand:

  1. Install SML 3.12.0 or newer, easiest via the Satisfactory Mod Manager (installing any mod through it pulls SML in).
  2. Grab PackHotkeys.zip from Releases.
  3. Unzip it so that the plugin descriptor ends up at <Satisfactory>/FactoryGame/Mods/GameFeatures/PackHotkeys/PackHotkeys.uplugin. The folder must be named exactly PackHotkeys, and it must sit under GameFeatures — this is a game feature plugin and will not load from Mods/ directly.
  4. Start the game. The keys appear under Options → Keybindings → Pack Hotkeys.

Typical install path on Steam: C:\Program Files (x86)\Steam\steamapps\common\Satisfactory\FactoryGame\Mods\GameFeatures\PackHotkeys

To uninstall, delete that folder. Nothing is written into your save, so removing the mod cannot break a world.

Note

The Mod Manager only manages mods it installed itself. It may remove folders it does not recognise when it syncs a profile, so re-check this one after using it.

Configuration

Keys are ordinary game keybindings: Options → Keybindings, category Pack Hotkeys. Rebind them there like any other control.

One behavioural option lives in Game.ini (<Satisfactory>/FactoryGame/Saved/Config/Windows/Game.ini):

[/Script/PackHotkeys.PackHotkeysSettings]
bUnequipWhenAlreadyEquipped=False

Assets

The mod is a Game Feature plugin. Besides the C++ module it ships four assets, all generated by Scripts/create_input_assets.py rather than by hand:

Asset Purpose
PackHotkeys (FGGameFeatureData) tells the game to scan the mod for FGChildInputMappingContext
Inputs/IA_TogglePack, Inputs/IA_EquipParachute the two actions, carrying the PlayerMappableKeySettings that put them in the keybinding menu
Inputs/MC_PackHotkeys FGChildInputMappingContext with mParentContext = MC_PlayerActions, holding the default keys

Note that the settings object must be created as a subobject of its action (new_object(..., outer=action)); building it with a plain constructor yields a transient object that is dropped on save, and the action then never shows up in the menu.

Parenting the context to MC_PlayerActions means the game applies and removes the bindings along with its own, so the keys do not fire while typing in chat or in menus.

To regenerate the assets after changing the script:

& "<engine>\Engine\Binaries\Win64\UnrealEditor-Cmd.exe" `
    "<starter-project>\FactoryGame.uproject" -run=pythonscript `
    -script="<repo>\Scripts\create_input_assets.py" -stdout -unattended -nosplash

Multiplayer

Inventory moves are authority-side, so the mod talks to the server through a Remote Call Object. In single player and as the host of a listen server this is all local and works as-is.

On a dedicated server the mod currently will not work: the RCO is registered from the local player's input setup, which never runs on a headless server. Fixing that properly needs a Game Instance Module asset, which in turn needs the Unreal editor — see Known limitations.

Known limitations

  • Dedicated servers are unsupported, as described above.

Building

You need the Satisfactory modding environment: Unreal Engine 5.6.1-CSS, Visual Studio 2022, Wwise and the Starter Project. Follow the official setup guide.

Then:

  1. Clone this repository into <StarterProject>/Mods/GameFeatures/PackHotkeys — the folder name must match the plugin name, and the GameFeatures parent is what makes Alpakit package it as a game feature.
  2. Regenerate project files and build the editor target.
  3. Package with Alpakit (Alpakit Dev installs it straight into your game).

The whole cycle also runs headless, without opening the editor:

# point these at your own install of the CSS engine and the Starter Project
$engine = '<engine>'
$project = '<starter-project>\FactoryGame.uproject'

# project files (once)
& "$engine\Engine\Build\BatchFiles\Build.bat" -projectfiles -project="$project" -game -rocket -progress

# editor target (once, ~10 min; also applies the WwisePatches pre-build steps)
& "$engine\Engine\Build\BatchFiles\Build.bat" FactoryEditor Win64 Development -project="$project" -progress

# build + cook + package the mod, optionally straight into the game
& "$engine\Engine\Build\BatchFiles\RunUAT.bat" -ScriptsForProject="$project" PackagePlugin `
    -project="$project" -clientconfig=Shipping -serverconfig=Shipping -utf8output `
    -DLCName=PackHotkeys -build -platform=Win64 -nocompileeditor `
    -CopyToGameDirectory_Windows="<path to Satisfactory>"

Note the editor target is called FactoryEditor, not FactoryGameEditor. The output archive lands in <StarterProject>/Saved/ArchivedPlugins/PackHotkeys/PackHotkeys-Windows.zip; to install by hand, unzip it into <Satisfactory>/FactoryGame/Mods/GameFeatures/PackHotkeys.

Close the game before packaging with -CopyToGameDirectory_Windows, otherwise the deploy step fails on the still-loaded mod DLL.

Compatibility

  • Satisfactory 1.2, CL 491125 or newer
  • SML ^3.12.0

Credit

The approach — resolving an item descriptor to its equipment class and moving it into the back slot — follows what Togglepack by derpierre65 does for its jetpack/hover pack toggle. The code here is an independent C++ implementation, not a copy of that mod's Blueprints.

License

MIT, see LICENSE.

About

Satisfactory 1.2 mod: separate hotkeys for equipping the Jetpack, Hover Pack and Parachute

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages