Skip to content

why are they not able to disable a perk only for a certain killer?

Comments

  • humanbeing1704 humanbeing1704

    Guess it’s not coded like that

    Either can only disable the killer completely or the perk full send

  • katoptris katoptris

    Cause it bvhr. You fix a bug then another bug show up in another character somehow.

  • LordGlint LordGlint

    @katoptris said:

    Cause it bvhr. You fix a bug then another bug show up in another character somehow.

    Move a rock 3 inches to the left and all of a sudden Huntress hatchets are thrown backwards

  • Iron_Cutlass Iron_Cutlass

    Because there is a possibility that the bug/glitch can occur on more than a single Killer, it's safer to just Killswitch the entire thing.

  • solarjin1 solarjin1

    Players love no where to hide. Most of the time a perk get disabled people don't even talk about it. I bet all them distortion heads are living it up right now

  • UndeddJester UndeddJester

    Killswitch I would have thought would simply be something like a property of the object like:

    TextName: Nowhere To Hide
AuraDuration: 5
AuraRange: 24
EventTrigger: killerGenKick()
Enabled: false  //here's your killswitch

    To killswitch a perk for a particular killer, you'd need some way of binding those properties together, which starts to get ugly fast. You'd need some way of saying:

    When Killer selects this character, and this perk is killswitched for that character, then disable this perk...

    You don't want your killswitch to require you to inject this instruction in the code, it has to already exist so that when you modify the property to killswitch it, the game just picks ot up and carries on... and this is something you have to do for every item/perk/character/event in the game.

    Branches (if statements) have big performance impacts on software. If you can avoid them, you should, and that's why there is so much money in (and companies are very guarded about their) branch predictions hardware. Even with it though, you don't want an "if" running on every event.

    E.g. What if blast mine gets a bug that causes permanent blindness if the killer kicks a gen while undetectable? How do you bind this together for a selective killswitch? Do you have to run this question on every single interaction in the game, which could easily slow the game performance to a crawl?

    The permutations of potential interactions are astronomical. Hope this gives some insight into why this is far more complex than you think.

  • Eleghost Eleghost

    probably should have just killswitched the onryo instead, would have less upset players probably.

  • NerfDHalready NerfDHalready

    @UndeddJester said:

    Killswitch I would have thought would simply be something like a property of the object like:

    TextName: Nowhere To Hide
AuraDuration: 5
AuraRange: 24
EventTrigger: killerGenKick()
Enabled: false  //here's your killswitch

    To killswitch a perk for a particular killer, you'd need some way of binding those properties together, which starts to get ugly fast. You'd need some way of saying:

    When Killer selects this character, and this perk is killswitched for that character, then disable this perk...

    You don't want your killswitch to require you to inject this instruction in the code, it has to already exist so that when you modify the property to killswitch it, the game just picks ot up and carries on... and this is something you have to do for every item/perk/character/event in the game.

    Branches (if statements) have big performance impacts on software. If you can avoid them, you should, and that's why there is so much money in (and companies are very guarded about their) branch predictions hardware. Even with it though, you don't want an "if" running on every event.

    E.g. What if blast mine gets a bug that causes permanent blindness if the killer kicks a gen while undetectable? How do you bind this together for a selective killswitch? Do you have to run this question on every single interaction in the game, which could easily slow the game performance to a crawl?

    The permutations of potential interactions are astronomical. Hope this gives some insight into why this is far more complex than you think.

    thanks a lot. idk how coding works, but if this is the case it makes sense.

  • Mr_K Mr_K

    It's not coded that way. Making it complex may produce bugs that might end up making the killer disabled the only route.

    You can go on without a perk. Try another build for awhile.

  • radiantHero23 radiantHero23

    @Eleghost said:

    probably should have just killswitched the onryo instead, would have less upset players probably.

    Not cool.

    But true.

    #bringbackSadako

  • katoptris katoptris

    @LordGlint said:

    https://forums.bhvr.com/dead-by-daylight/discussion/comment/3616616#Comment_3616616

    Move a rock 3 inches to the left and all of a sudden Huntress hatchets are thrown backwards

    Fix trapper 's traps and all of sudden pig's bear trap causes instant game over.

Categories