[α-467] foxhounds are broken
LeoBeliik opened this issue · 2 comments
exactly the same as #3547 but without the main bug:
· they pathfind to unlit furnace, and they try to sleep on top (they do the animation and fail)
· they do not pathfind to magma blocks, they only try to sleep is they happen to be on top of one (either from pushing them or casually walking there), like the furnace, they try to sleep, do the animation and fail.
· in servers, patting them sets you on fire for half a second (??)
· foxhounds can set you on fire thru shields
· while foxhounds can kill each other, they cannot damage you at all if you have fire resistance (they still should bite??)
· equipping armor to the foxhound while sitting, will make them stand up without changing the Sitting tag (so they are still sitting but they don't look like they are, I can't test the same with sleeping because they don't sleep)
· feeding them a tater don't give back an angry tater, it just poop a normal tater > #5329
Yes, dumb clipboard.. that's edited.
1- I don't think that's intended, in fact the wiki says "If put on top of a furnace" so I don't even know if they should pathfind at all, but it also says "They'll sleep on hot blocks like magma" thus, lit furni sounds correct
3- then the bug is that doesn't last enough nor it works in sp
6- so I guess the taters are broken? I'll check if the rest of taters work, if not I'll cross out this one and open a new issue for that specifically
I think you linked the wrong issue?
- the pathfinding to unlit furnaces seems intentional, but of course the sleeping animation thing is a bug
- in addition to lit and unlit AbstractFurnaces, they should pathfind to any block with a light level greater than 2. Magma blocks have a light level of 3
- this is intentional, you need fire resistance to pet them like for taming them. However the fire doesn't apply correctly in singleplayer either. It's supposed to set you on fire for 5 seconds
- I agree this is weird, they don't seem to respect shields at all, will look into it
- definitely a bug
- The stack has its angry component set, but
/give Dev quark:tiny_potato[quark:is_angry=false]and/give Dev quark:tiny_potato[quark:is_angry=true]seems to give the same stack ???