The Hordes

The Hordes

5M Downloads

PlayerRevive Incompatibility

DogeKingChris opened this issue ยท 12 comments

commented

I've already made CreativeMD aware of this, but when you go into bleeding state by dying to infection, the infection disappears. I tried fixing this by adding "hordes:infection" damage type to the list of bypasses, but it did not work. Either that damage type is not used or something is wrong on PlayerRevive's part

commented

Also, if I use /damage @s 100 hordes:infection, it keeps the infection. Only dying to the infection effect reaching stage 5 doesn't work.

commented

If there's a different damage type, then please tell me

commented

Which version? Is the bypass list a tag?

commented

1.20.1 forge latest, and no

it uses damage types

commented

@SmileycorpMC what is the name of the damage type inflicted that makes the player die from the infection? PlayerRevive has a list configuration where you can put in the damage types which lead to death (meaning the player will not enter the bleeding state).

commented

@SmileycorpMC what is the name of the damage type inflicted that makes the player die from the infection? PlayerRevive has a list configuration where you can put in the damage types which lead to death (meaning the player will not enter the bleeding state).

It's hordes:infection, is there anything I need to do my end to make it an option enabled by default?

commented

Well the problem is mainly that when I do put hordes:infection in the bypass list, it doesn't make infection bypass the bleeding state. If I do /damage @s 100 hordes:infection, it works. But, if I let the infection naturally reach stage 5, it doesn't work.

commented

Seems like I did not actually check for the registry name of the damage type. Released a new version which should fix this issue (hopefully).
@SmileycorpMC I added hordes:infection to the bypass list by default.

commented

Nice glad to hear. Thanks for the help. I guess this issue can be closed then. God bless you!

commented

Thank, I'll leave this open and do some testing with the new version when I get a chance to see if there's anything else messing with it.

commented

works great for me now

commented

Solved