satisfactorymodding / satisfactorymodding/SatisfactoryModLoader

"Cannot insert after hooks for statement" error message does not log the hook bp trying to apply it

Open
#390 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
344
Forks
225
PR merge metrics
No merged PRs in 30d

Description

Example:

[2025.09.06-17.46.54:693][  0]LogConfigManager: Display: Successfully loaded configuration from ../../../FactoryGame/Configs/InfiniteNudge.cfg
[2025.09.06-17.46.54:695][  0]LogBlueprintHookingCodeGen: Error: Cannot insert after hooks for statement in function Function /Game/FactoryGame/Equipment/BuildGun/BP_BuildGunStateBuild.BP_BuildGunStateBuild_C:ExecuteUbergraph_BP_BuildGunStateBuild because that statement represents an unconditional control flow jump
[2025.09.06-17.46.54:695][  0]LogBlueprintHookManager: Warning: Function /Game/FactoryGame/Equipment/BuildGun/BP_BuildGunStateBuild.BP_BuildGunStateBuild_C:ExecuteUbergraph_BP_BuildGunStateBuild failed to install some of the hooks. Function dumps for debugging are provided below:

https://discord.com/channels/555424930502541343/1036634533077979146/1413968407518380073

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the LogBlueprintHookingCodeGen path that emits "Cannot insert after hooks for statement" and trace the hook data available when insertion fails. Compare it with the LogBlueprintHookManager failure output and the linked example log. Done means the error identifies the blueprint hook that was being applied, without losing the existing function and control-flow details.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, unreal-engine
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.