[Bug]: Explode Base event still active despite being disabled in settings #123

Open
opened 2025-07-26 18:31:56 -05:00 by NLYomo · 2 comments
NLYomo commented 2025-07-26 18:31:56 -05:00 (Migrated from github.com)

What happened?

Explode Base event still takes place, even when this is disabled in /tbs config SERVER & /tbs config CLIENT.
It seems like the disable option is being ignored, which keeps the Explode Base in active state and blows up the house. (TBS ver. 1.10.1, selected 1.9.7 since dropdown doesn't have the newest version yet)

Version

1.9.7

What operating system(s) do you experience this issue on?

Windows

What Minecraft version were you on?

NeoForge 1.21.1

Relevant log output


### What happened? Explode Base event still takes place, even when this is disabled in /tbs config SERVER & /tbs config CLIENT. It seems like the disable option is being ignored, which keeps the Explode Base in active state and blows up the house. (TBS ver. 1.10.1, selected 1.9.7 since dropdown doesn't have the newest version yet) ### Version 1.9.7 ### What operating system(s) do you experience this issue on? Windows ### What Minecraft version were you on? NeoForge 1.21.1 ### Relevant log output ```shell ```
Shaolim132 commented 2025-08-03 21:18:44 -05:00 (Migrated from github.com)

Enable the event again, then disable it (I think i solved this bug by doing this)

Enable the event again, then disable it (I think i solved this bug by doing this)
tangbathaian commented 2025-08-18 03:39:55 -05:00 (Migrated from github.com)

Disable the place_empty event

Disable the place_empty event
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Writers-of-the-Script/Issue-Tracker#123
No description provided.