Playtime Protector is a UE4SS Lua mod that adds:
- God Mode (blocks damage based deaths)
- No Attack (best effort enemy pacify)
- Optional Fail Blocker for scripted “you lose” sequences
This is for single player use and testing. Use at your own risk.
Note: This README is for the UE5 chapters (3, 4, 5). For Chapters 1 and 2, use the UE4 SAFE build.
This repo contains the mod files and a sample mods.txt you can copy a line from.
README.md
.gitignore
Mods/
PlaytimeProtector/
Scripts/
main.lua
mods.txt.example
This repo does not include UE4SS.
Note: UE4SS expects Mods/<ModName>/scripts/main.lua. On Windows, Scripts usually still works, but scripts is the safest choice.
- UE4SS installed for the chapter you are playing
- Install per chapter (each chapter has its own game folder and
Binaries\Win64)
- Find the chapter’s
Binaries\Win64folder.
Example (Chapter 3):
C:\Program Files (x86)\Steam\steamapps\common\Poppy Playtime\PoppyPlaytime_Chapter3\Playtime_Chapter3\Binaries\Win64
-
Install UE4SS into that folder so UE4SS files sit next to the chapter’s
*-Win64-Shipping.exe. -
Copy this repo’s mod folder into the chapter.
Copy:
Mods\PlaytimeProtector\
To:
...\Binaries\Win64\Mods\PlaytimeProtector\
After copying, you should have:
...\Binaries\Win64\Mods\PlaytimeProtector\scripts\main.lua
- Enable the mod in the chapter’s
mods.txt.
- If
...\Binaries\Win64\mods.txtalready exists, do not overwrite it. Open it and add:
PlaytimeProtector : 1
- If it does not exist, create
mods.txtin...\Binaries\Win64\and add:
PlaytimeProtector : 1
A sample file is included at:
mods.txt.example
- Launch the game normally.
Open UE4SS.log in the same Win64 folder and confirm the mod starts. You should see something like:
Starting Lua mod 'PlaytimeProtector'
Note: On screen messages are not guaranteed to display in shipping builds. The log is the reliable signal.
- F1 Toggle God Mode
- F2 Toggle No Attack
- F3 Toggle Block Damage (damage hook behavior)
- F5 Toggle Fail Blocker (off by default)
- F7 Dump likely enemies to UE4SS.log
- F8 Dump AI pawns to UE4SS.log (best way to learn real enemy names per chapter)
- F9 Toggle Aggressive No Attack (can break puzzles and scripted sequences)
Tip: If you do not see any on screen text when toggling, that can be normal. Check UE4SS.log for the mod output.
Uses SetCanBeDamaged(false) plus Unreal damage hooks to zero damage. This helps when the chapter uses the normal Unreal damage pipeline.
If a death is a scripted fail state (cutscene kill, forced game over trigger), God Mode may not help.
Best effort pacify:
- disables enemy collision
- disables overlap events on enemy components (covers many grab volumes and hitboxes)
- tries to stop controller movement and unpossess
Works when the “attack” is driven by an actual enemy actor and overlap or collision logic. May not stop cutscene driven kills or trigger driven deaths.
A hammer for scripted deaths. It destroys actors whose names match the fail keywords list.
Use it only in the problem section, then turn it off again after you pass. It can break progression if left on.
Treats most AI controlled pawns as enemies. Useful when enemy names differ across chapters, but it can also hit puzzle actors or non hostile NPCs.
- Load the chapter
- Press F8
- Open
UE4SS.logand find the AI pawn list - Add a tight, distinctive substring from the enemy pawn name into
ENEMY_KEYWORDS - If an ally is getting hit, add a substring into
FRIENDLY_KEYWORDS
Avoid super generic keywords like BP_, Pawn, Character, AI, Controller.
Check UE4SS.log for mod load lines. If UE4SS did not load, verify you installed UE4SS into the correct chapter Win64 folder. Each chapter has its own.
That death is likely scripted, not damage. Try Fail Blocker for that section.
The killer may be a cutscene trigger or a separate actor not matched by keywords. Use F8 to find the real actor names, then tighten ENEMY_KEYWORDS.
- Remove:
...\Binaries\Win64\Mods\PlaytimeProtector\ - Or set:
PlaytimeProtector : 0inmods.txt - Remove UE4SS files if you want a completely clean install