#"Combat medic" perk is bugged/works in a stupid way

1 messages · Page 1 of 1 (latest)

spice scroll
#

I was mining dino prints and blew myself up enough times to actually get low health. Normally it fixes itself with the combat medic perk, but this time I couldn't get it to trigger. Turns out that the game ostensibly doesn't consider a mob an "enemy" until it has hit you, so me being careful at low health and not taking a single hit meant it never triggered.

Very easily reproduceable. Happens every time I try it. Rhodonite wings sword in case that's important. It also brings me back to full health in one swing, but I don't mind that bug.

Steam, latest game version

frank pasture
#

Hello again @spice scroll! Thanks for sharing this.

Just to help us narrow it down a bit more — did this happen while you were in the Cave of Memories? And have you tried testing it in the Cavern as well to see if it behaves the same there? 😮

spice scroll
#

Yes cave of memories is where dino prints drop. No I haven't tried it in the cavern

spice scroll
frank pasture
spice scroll
#

No thank you, I do not see how this is related to anything stored in a save. Come back if you try to reproduce it and fail.

frank pasture
spice scroll
#

Sorry for asking but am I talking to an AI here? Isn't the video more than clear on this? Not to mention it should be reproduceable in all of 30 seconds.

I used explosives to drop my health to show the issue. Then you can clearly see the HP doesn't refill from hitting monsters until the point I let them hit me, in which case the next hit instantly refills the bar. It ostensibly doesn't count as being "in combat" with them until you get hit by them. It wouldn't matter where the damage came from (unless you're telling me your code saves that and somehow uses it in the combat medic calculation, but even so, I checked and explosives are unrelated).

I don't know your codebase, but I would assume that the perk checks a flag for whether you're "in combat with an enemy" or not, and that said flag isn't set until the enemy touches you. Not even sure anything else in the game uses that flag, but if it does, I would check those too. I always thought mastery gain from moster killing was slow, so that's one I would swing by the codebase of.

I'm not sure I get the confusion over such an ostensibly reproduceable issue, unless you've tried and cannot reproduce it. If so I'd make sure it's the same weapon, but at 1:07 in the video you can see the scythe also fails to heal. That would leave the chance of my save being permanently bugged with some flag that breaks it, but that seems very unlikely, your response has not indicated that (again, just seems like AI/copy paste responses), and the spaghetticode-implications of managing to create such a bug are somewhat scary.