andrewandCursor
2449525175
BREAKTHROUGH INSIGHT: The user reported: AI goes aggressive then immediately returns to neutral. This matches the symptom of SetPosition() breaking the character controller. ROOT CAUSE: - We were calling SetPosition() every 500ms - SetPosition() bypasses character controller → kills all movement - Between SetPosition calls, Move() had to re-establish control - This constant switching BREAKS the AI's ability to function THE FIX: - ONLY use SetPosition() for emergencies (drift > 300 units OR > 2 seconds) - Always use Move() with small, bounded deltas (max 50 units/frame) - This lets the character controller and AI run continuously - AI can now maintain state and play animations properly CRITICAL CHANGES: 1. Emergency thresholds: 300 unit drift OR 2 second timeout (not 200/500ms) 2. Normal movement: Use Move() with small incremental deltas 3. Never SetPosition during normal gameplay 4. SetPosition only as emergency correction EXPECTED RESULT: - ✅ Smooth continuous movement (no more jerky jumps) - ✅ AI stays active (can get aggro and respond naturally) - ✅ Proper animations (velocity continuous, not reset every 500ms) - ✅ Network sync maintained (emergency corrections prevent drift) Co-authored-by: Cursor <cursoragent@cursor.com>
Fallout4Together Plugin
This is the native Fallout4Together plugin using CommonLibF4.
Requirements
- XMake [3.0.0+]
- C++23 Compiler (MSVC or Clang-CL)
Getting Started
git clone --recurse-submodules https://github.com/libxse/Fallout4Together
cd Fallout4Together
Build
To build the project, run the following command:
xmake build
Note: This will generate a
build/windows/directory in the project's root directory with the build output.
Build Output (Optional)
If you want to redirect the build output, set one of the following environment variables:
-
Path to a Mod Manager mods folder:
XSE_FO4_MODS_PATHor
-
Path to a Fallout 4 install folder:
XSE_FO4_GAME_PATH
Project Generation (Optional)
If you use Visual Studio, run the following command:
xmake project -k vsxmake
Note: This will generate a
vsxmakeXXXX/directory in the project's root directory using the latest version of Visual Studio installed on the system.
Alternatively, if you do not use Visual Studio, you can generate a compile_commands.json file for use with a laguage server like clangd in any code editor that supports it, like vscode:
xmake project -k compile_commands
Note: You must have a language server extension installed to make use of this file. I recommend
clangd. Do not have more than one installed at a time as they will conflict with each other. I also recommend installing thexmakeextension if available to make building the project easier.
Upgrading Packages (Optional)
If you want to upgrade the project's dependencies, run the following commands:
xmake repo --update
xmake require --upgrade
Documentation
Please refer to the Wiki for more advanced topics.