Huntress' Lullaby mechanic change
Okay hear me out. What if Huntress' Lullaby was an obsession perk?
When compared to other hexes, this perk is pretty weak. The reason for this lies in how situational it is since a person with good reflexes or eye-to-hand coordination can still nail 0 warning skill checks. Now I understand that it's still a strong perk and it can stomp on new players so here's my proposed changes.
You become obsessed with one survivor
Each time you hit the obsession you gain a token up to a maximum of 4 tokens
1-3 Token: Shortens the time between the Skill Check Warning sound and the Skill Check.
4 Tokens: No Skill Check Warning sound.
Every time a survivor that's not the obsession completes 2/3/4 great skill checks, lose a token
You can only be obsessed with one survivor at a time
Boom, Stake Out just became viable. Anyway, I removed the extra regression penalty due to how easy it is to gain tokens now. The reason why survivors who aren't the obsession are the ones who can make the perk lose tokens is to encourage the killer to still go for survivors who aren't the obsession.
Edit : After some discussions, I think I have another idea that might just be better.
You become obsessed with one survivor
Skill Check Warning Sounds are completely silent for the obsession
Each time you hook the obsession, for a period of 35/40/45 seconds, Skill Check Warning Sounds for all survivors are completely silent
You can only be obsessed with one survivor at a time
For this idea, I just want consistency in activation and Dead Man's Switch is technically that. You can choose which of my ideas are better.
Comments
-
This would literally just be another remember me and we all know how good thst perk is.
I think it should just not be a hex perk, maybe it’d be better then.
0 -
Okay
- There's no way to tier this perk as it stands (and they don't seem to want to remove that for now),
- You're really underestimating how many times 3 people can hit a great even with miss-timed skillchecks.
0 -
I'd be okay with it not being a hex only if there is some other way to reduce stacks. A 5 stack lullaby can definitely be a game changer. What if it was token based in a way where every hook gave you two tokens, and so the next two skill checks would consume a token but be silent?
0 -
Problem is, skill checks pop up pretty often while hooks don't. Plus your idea would just turn Huntress' Lullaby into an inferior PGTW since it has the same requirements with a lesser effect on gens.
0 -
You're not wrong, but with the extra regression from failed skill checks it'd have the potential to regress more gen progress than a pop. Perhaps 3 tokens per hook then?
0 -
1. I think it's in the same tier as Unnerving and Overcharge. They're all perks that mess with your skill checks and can be countered by experience. Plus if I'm not wrong, Otz gave all 3 of these perks 2 stars
2. I get what you're saying but if it were the other way around (The Obsession is the one that can remove stacks while everyone else can give stacks) killers will just end up tunneling the obsession. It's the same problem as old Dying Light
0 -
You're not wrong, but with the extra regression from failed skill checks it has the potential to regress more gen progress than a pop. How about 3 tokens per hook?
0 -
Potential is a dangerous word when it comes to designing perks. I think a better way would be to give it the work like Dead Man's Switch and making it consistently and reliably silence skill check warnings for a period of time. It won't have the same effect of gluing survivors to their generators as Dead Man's Switch does but at least you won't have to worry about losing your snowballing progress due to the hex being cleansed or survivors hitting great skill checks
0 -
Change it to be like Thanatophobia.For every injured survivor, reduced skillcheck notification time. All injured = no notification.
0 -
- Oh my bad. I worder that super wrong. I meant the perk levels that each of them have. Your version doesn't have any way to "level up"
- Doesn't it then become weaker than it's hex version?
0 -
- Oh that's what you meant. Yeah, I was wondering about that too
- I've made a secondary version but I'll take your idea into consideration. How about after 2/3/4 great skill checks from survivors who aren't the obsession, you lose a token?
0 -
I actually like that idea a lot. A timer system would definitely be more consistent. What do you think the activating condition should be?
0 -
Under the edit of the post I wrote how it should work. Basically, it activates when you hook the obsession, just like Dead Man's Switch
0 -
I feel like that would kill the perk. The effect isn't really strong enough to warrant such a restrictive activation condition. If you want to include the obsession aspect, I'd prefer if the obsession was always under the effect (so, silent skill checks for the obsession), and for everyone else it afflicts survivors for 45 seconds when they unhook another survivor. Or something along those lines.
0 -
That... Can actually work. I have yet to see a perk where being the obsession gives you a debuff since it either makes the killer not want to tunnel you or want to tunnel you. I like it
0 -
I like its current design. Your design seems so...needless.
I am currently only advocating for Lullaby to have percentage chances of randomizing what delay the skill check sound has and percentage chances for the sound to play with no skill check. Honestly, it should also work on all skill checks (because hexes are meant to be scary until broken and rn there's no real threat from Lullaby), but that's probably not going to happen any time in the near future.
0 -
To be fair, Remember Me might be okay if they didn't nerf the crap out of it.
0 -
Yeah that's the problem. I know this perk isn't gonna get stronger so I just want the activation to be slightly easier. I know this perk is decently strong but as a hex it's pretty weak. If it wasn't a hex, it would be too strong.
That's why I went with the Remember Me or Dead Man's Switch route since at least an obsession switching perks can remedy it. Undying doesn't even work with current Lullaby.
0
