Before submitting the issue

• I have checked that the bug is not a duplicate or, if it is, it needs to be reopened
• I have checked that I am running the latest version of Better Beacons Mod
• I have checked the FAQ section for solutions
• I have read the contributing guidelines and I agree with the Code of Conduct

Loader, loader version and minecraft version

Please provide the loader, loader version and the Minecraft version on which you are running the mod. For example: Forge 47.2.0, Minecraft 1.20.1
Neoforge 21.1.93, Minecraft 1.21.1

Describe the bug

A clear and concise description of what the bug is.
Crashing when same dimension teleporting out of current beacon loaded chunks

To reproduce

Steps to reproduce the behavior:
1. 'Load beacon chunks'
2. 'Teleport outside of loaded beacon chunks via vanilla commands or waystone'
3. 'Crash with launcher error message'

The game crashed: ticking block entity
Error: java.lang.NullPointerException: Cannot invoke "com.cerbon.better_beacons.util.mixin.IBeaconBlockEntityMixin.bb_setPrimaryEffectAmplifier(int)" because "beaconMixin" is null'

Expected behavior

A clear and concise description of what you expected to happen.
Not Crashing

Screenshots

If applicable, add screenshots to help explain your problem.
N/A

Latest log

LatestLog.txt

Please paste the latest log here. You can find it by opening the folder where Minecraft is installed, searching for the "logs" folder, opening the "latest.log" file, and copying its content. 

Additional context

Tried reinstalling mod twice, no change
#24 I do have puzzleslib Installed however have been using the mod before Better Beacons, only started crashing today, no new mods added before crashing began
Please let me know if any additional-additional context would be helpful!

Having the same issue as you.
Using Better Beacons version 2.1.0, Minecraft version 1.12.1, PuzzleLib 21.1.27, Neoforge 21.1.117 and the modpack is at https://www.curseforge.com/minecraft/modpacks/pycolonies-neoforge

^

Just released 2.1.1. Should be fixed now. Please lmk.

Just released 2.1.1. Should be fixed now. Please lmk.

Hello, I don't really know if this issue happens in 1.20.1, but really hope you can check it too

Just released 2.1.1. Should be fixed now. Please lmk.

Fixed on 1.21.1 👍

Hi, version 2.1.1 fixed the issue. Thanks!

@CaoTrongThang There hasn't been an update to 1.20.1 in a year, so the 2.1.1 update the developer released wont work on 1.20.1. Meaning this bug may or may exist on there anyways, my suggestion would be update to MC 1.21.1 if you can.

@CaoTrongThang The issue should not exist in 1.20.1. If it happens to you please lmk.