Respawn priority bug

[SuperBeacon]

Description of Issue

"anchor" and "bedLocation" are ineffective when in the same list as "homeLocation" and "spawn"; "homeLocation" and "spawn" have higher priority than "anchor" and "bedLocation".

Example1:
    PriorityOrder:
    - anchor
    - bedLocation
    - homeLocation
    - wodSpawn
    - spawn

After setting anchor and bedLocation, the player still respawns at homeLocation upon death.

Example2:
    PriorityOrder:
    - anchor
    - bedLocation- worldSpawn
    - spawn

After setting anchor and bedLocation, the player still respawns at spawn upon death.

Version Information

CMI: 9.8.4.19 CMILIb: 1.5.8.9 SerVer: Paper-1.18.2

Errors

Relevant Config Sections

Relevant Plugins

No response

Agreements

• My server is supported by CMI.
• My version of CMI at the time of this report is up to date.
• I have searched the github and asked around before making this report.

[Zrips]

In which world are you testing this? As anchor only works in nether, while beds can't be used there, inverse is true in overworld, where you can't use anchors while beds are valid option, so one will be picked over the other in all cases, so based on which world you are setting these options simply pick the one which is valid for that world

[SuperBeacon]

I tested the bed in the Overworld, but even though I set the bed priority higher than home, the plugin still prioritizes respawning at home. Verion: Paper-1.18.2