Closed Olthoo closed 1 year ago
So, the ender dragon implemented by BentoBox is not ender dragon :D
That is because it would make it impossible to use in non-game mode worlds.
You need to use bentobox_ender_dragon
. You can check if it is available if you try to use /summon
command.
Any idea on how I can solve this issue ? advancements doesn't support minecraft:bentobox_ender_dragon nor bentobox_ender_dragon because datapacks are loaded before Bentobox, or could you maybe add a "grand advancement" in config ?
like so :
# The advancement to grant the player. The advancement has to exist on the server.
advancement: skyo:end/kill_dragon
Hmm, I could do that...
That would be cool ! In vanilla 2 advancements are related to the dragon, one for killing it (minecraft:end/kill_dragon) and one for resummoning it (minecraft:end/respawn_dragon)
So adding 2 entries in the config would be fine for 95% of users. I got ~10 customs advancements that call minecraft:ender_dragon so we're gonna try to make something on our side to "link" bentobox_ender_dragon to ender_dragon in player stats but that doesn't look easy haha Thanks again for your time and quick answers !
Description
Describe the bug
I use a datapack with a mix of custom and vanilla advancements on my server, but the dragon but dragons spawned by the addon are not recognize by said advancement, I think it's due to advancement looking for the entity minecraft:ender_dragon while the summoned is called minecraft:bentobox_ender_dragon, I tried to use that name in advancement but the advancement fail to load because this entity does exist in vanilla
Steps to reproduce the behavior
Expected behavior
Dragon killed by the player are register as enderdragon in the player's statistics
Screenshots and videos (Optional)
Environment
BentoBox Version (Mandatory)
Plugins (Optional)
Additional context (Optional)
here is an example of advancement checking for dragon