Environment
- macOS Sequoia 26.5
- Balatro: (replace with your exact game version)
- Lovely: 0.9.0
- SMODS: 1.0.0-beta-1814a
Issue
Some mods that require a restart (at least First Round Joker and Lock the Deal) never get removed from Lovely’s blacklist.txt.
As a result, every subsequent launch prints:
INFO - [♥] 'first-round-joker' was found in blacklist, skipping it.
INFO - [♥] 'lock-the-deal' was found in blacklist, skipping it.
and both mods appear disabled in the Mods menu every time the game starts.
Steps to reproduce
- Enable First Round Joker and/or Lock the Deal.
- Allow the automatic restart.
- Exit the game normally.
- Launch the game again.
Expected:
- The mods remain enabled.
- blacklist.txt should be cleared (or the corresponding entries removed).
Actual:
- Both mods are disabled again.
- blacklist.txt still contains:
first-round-joker
lock-the-deal
Additional testing
I manually deleted:
~/Library/Application Support/Balatro/Mods/lovely/blacklist.txt
Then:
- Started the game.
- Closed the game normally.
- The file was automatically recreated.
- The same two mod IDs were written back into the blacklist.
This appears to indicate that SMODS is writing these entries but never removing them.
The author of both mods reviewed the logs and believes the problem is related to SMODS not clearing blacklist.txt, rather than an issue within the mods themselves.
Environment
Issue
Some mods that require a restart (at least First Round Joker and Lock the Deal) never get removed from Lovely’s blacklist.txt.
As a result, every subsequent launch prints:
INFO - [♥] 'first-round-joker' was found in blacklist, skipping it.
INFO - [♥] 'lock-the-deal' was found in blacklist, skipping it.
and both mods appear disabled in the Mods menu every time the game starts.
Steps to reproduce
Expected:
Actual:
first-round-joker
lock-the-deal
Additional testing
I manually deleted:
~/Library/Application Support/Balatro/Mods/lovely/blacklist.txt
Then:
This appears to indicate that SMODS is writing these entries but never removing them.
The author of both mods reviewed the logs and believes the problem is related to SMODS not clearing blacklist.txt, rather than an issue within the mods themselves.