CommunityPatch - AntiCheese Poll

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Want to gather opinions on some points

Brand Enemy/Gouging Strike/True Love's Kiss

Currently these have infinite duration. And can be used to kill the an array of bosses on their own, while the player is away.

Not a cheese. No need to change

It's a cheese. Yet, leave as is

It's a cheese. Let them have a fixed duration, e.g. 120s

It's a cheese. Let them have a fixed duration, e.g. 120s, but increased damage (+20%?)

It's a cheese. Let them have a fixed duration, e.g. 120s (which can be prolonged by 6s everytime the enemy takes damage from a melee attack)

Other:

Clear selection

Wall of Draining

It could be used to prolong ongoing buffs on wizard by a lot. Including situations where enemies didn't have finite buffs.

It will get it's applicationPrerequisite updated to hopefully no longer drain from infinite buffs.
Do you think it requires additional changes?

No additional changes needed

instead of draining 1s and extending buffs on self by 1s per tick; drain 2s from enemy, and extend buffs on self by 0.5s per tick (per affected enemy). (same as in BPM)

instead of draining 1s and extending buffs on self by 1s per tick; drain 2s from enemy, and extend buffs on self by 1s per tick (per affected enemy)

instead of draining 1s and extending buffs on self by 1s per tick; drain 1s from enemy, and extend buffs on self by 0.5s per tick (per affected enemy)

Other:

Clear selection

Barring Death's Door

Currently BDD gives immunity do failling unconscious. It can be extended and also used multiple times per combat. It has good synergy with Death Godlikes, yet in certain situations let's you ignore such aspects like having to weight-in [glass-cannon with hard-cc] vs [sturdy] approaches, positioning.

Providing that Salvation of Time will be synced with BPM implementantion

Leave BDD as is. Just clear effect on end of combat

Leave BDD to similarly as it is. Clear it's effect on end of combat. And limit it to once per combat

Leave BDD to similarly as it is. Clear it's effect on end of combat. And make it so affected character cannot be affected by BDD again for 30s

Leave BDD to similarly as it is. Clear it's effect on end of combat. And make it so affected character cannot be affected by BDD for the duration he was affected by it. E.g. BDD lasted 8s, and after that target cannot be BDD'ed again for 8s

(Current Approach) Leave "death-prevention" effect on Potion of Final Stand. But change BDD abilities to damage-absorbing-shield, like in BPM?

Leave "death-prevention" effect on Potion of Final Stand. But change BDD abilities to damage-absorbing-shield, like in BPM. Also add a 12s cooldown during which affected character cannot receive BDD shield again

Other:

Clear selection

Grave Calling (Chilling Grave)

Currently it's relatively easy for a lvl 7+ berserker/beckoner to trigger 6-18 Chill Fogs at the start of combat and deal 180+ dps for 15+ seconds in 2.5m AoE. Hardly any character can deal such dps, and especially at early-mid levels

Also berserker is not even a requirement here. Just need to kill 2 skeletons with Grave Calling to start the chain reaction, before they despawn

Not a cheese. No need to change

It's a cheese. Yet, leave as is

It's a cheese. Add an internal cooldown of 6s to Chill Fog trigger.

It's a cheese. Add an internal cooldown of 10s to Chill Fog trigger.

It's a cheese. Limit Chill Fog trigger to once per combat

It's a cheese. Limit Chill Fog trigger to twice per combat

It's a cheese. Limit Chill Fog to proc only when killing hostile vessels. And ignore confuse/charm/dominate when determening party allegiance

It's a cheese. Limit Chill Fog to proc only when killing non-summon vessels

It's a cheese. Let Chill Fog proc trigger only when killing non-summoned vessels

Other:

Clear selection

Boltcatchers (gloves)

Currently Boltcatchers as part of their Storm Blows proc internally trigger a AttackMeleeGameData. This in it's turn can contribute to crit-chain loop propagation if it itself crits

Note: it's penetration will be made scalling in CP.Extra (synced with BPM)

Not a cheese. No need to change

It's a cheese. Yet, leave as is

It's a cheese. Make the proc hit, but to not be able to crit

It's a cheese. Make the proc hit, but to not be able to crit. But also increase it's base damage

It's a cheese. Make the proc hit, but to not be able to crit. But also increase it's penetration (in addition to extra scaling from BPM)

Other:

Clear selection

Whisper of the Wind (weapons)

make it work only with melee weapons (it will become disabled, if any ranged weapon is equipped)

make it work only if there is a melee weapon in main hand

leave it as is (even if only ranged weapons are equipped)

Other:

Clear selection

Whisper of the Wind (cost)

Leave it's cost at 5 Wounds

Increase to 6 Wounds

Increase to 7 Wounds

Leave at 5 Wounds. But temporary increase cost to 7 for 6s after usage

Other:

Clear selection

Unbending Trunk (expected healing)

At the moment Unbending and it's upgrades heal for more than it is declared in their descriptions.

For example vanilla Unbending Trunk is stated that it heals for 33% of damage taken
- but due to an extra 0s tick it actuallys heals for 53% of damage taken. (at 10 INT, +0% healingTaken)

Notes:
- healingTaken mainly comes from food, Amira's Wing (rod) and Furrante's Breastplate, so it's hard to stack it over +30-40%.

- if Unbending Trunk would heal for only 33%, it would actually feel quite low; since it doesn't heal damage taken from DoTs, only from damage instances that go through hit resolution

Make it heal for 45% (at 10 INT, +0% healingTaken)

Make it heal for 60% (at 10 INT, +0% healingTaken)

(BPM) Make it heal for 75% (at 10 INT, +0% healingTaken)

Other:

Clear selection

Unbending Trunk (implementation)

Vanilla implementation of Unbending is flawed

When fighter takes damage, he gets affected by a ApplyOverTime HoT that has 5s (unfixed) duration with a 3s interval. ApplyOverTime divides 33% between the ticks, but it is not "aware" that there is also a 0s tick, resulting in 20% + 20% + 13% = 53%.

Additionally when fighter takes damage it seems that 0s tick happens for all HoT instances on the Fighter.

In order to minimize the 0s tick effect there are 2 approaches:
- increase the total duration AND set the interval from 3s to 1s

- change it from ApplyOverTime HoT to separate heal events that happen after some time sets, like: 2s, 4s, 6s

Change Unbending HoT duration from 5s (unfixed) to 12s (fixed). AND change interval from 3s to 1s (BPM approach)

Change Unbending HoT from ApplyOverTime to 3 separate instances that heal for 1/3 (of expected healing) at: 2s, 4s and 6s

Change Unbending HoT from ApplyOverTime to 4 separate instances that heal for 1/4 (of expected healing) at: 2s, 4s, 6s and 8s)

Other:

Clear selection

Concelhauts Draining Touch

Concelhauts Draining Touch - summons a special melee weapon (with x1.6 base damage than sabre) that on on succesful hit applies Weakened to the target, heals the wizard for 20% of damage dealt AND dissapears after that

The bug is: if you don't have it learned, and cast Draining Touch from grimoire, and switch to another grimoire, this summoned weapon will not dissapear after first succesfull hit (as intended) but will last till combat end

Not a cheese. No need to change

It's a cheese. Yet, leave as is

It's a cheese. Change it's base damage to be equal to that of a sabre. And grimoires that have it could provide +50% with it. I.e. the bonus dissapears if you switch grimoire

It's a cheese. Just remove it from grimoires. Players will just learn it on level up. Note: this is not retroactive

Use both previous options ^

Other:

Clear selection

Resonant Touch

Resonant Touch is set to a 25 stacks cap in CP.Basic

There was a suggestion to make it auto-release/explode when reaching that limit

Note: if you know how to implement it would be awesome for you to share :)

Good idea. Let Resonant Touch auto-release/explode when reaching 25 stacks

No. No need for auto-release/explode

Clear selection

Dawnstar Blessing

Dawnstar Blessing currently provides a very big HealingDone bonus of +50%

Leave it as is

Change it +55% which decreases by 5% for every character level past lvl 4 until it reaches +15% at lvl 12; and it remains +15% after that

Other:

Clear selection

Blood Sacrifice (health threshold)

Currently Blood Sacrifice can be used with no limit (aside from health)

Leave it as is

Make it only usable while above 25% hp

Other:

Clear selection

Blood Sacrifice (cast speed)

Currently Blood Sacrifice has 0.8/0 cast/recovery time

Leave it as is

Change it to 0.8s/3s cast/recovery (BPM approach)

Change it to 0.8s/1s cast/recovery, and 3s cooldown

Other:

Clear selection

Blood Sacrifice (penalties)

BPM adds the following penalty for using Blood Sacrifice:

Added a -100% healing received for base 6s when using Blood Sacrifice, to make it more tricky to use.

No need for penalty

Yes, need some penalty. After using Blood Sacrifice, wizard gets a 5% penalty to HealingTaken for 60s (fixed) (staking up to 20 times)

Yes, need some penalty. After using Blood Sacrifice, wizard gets a -1 CON penalty for 30s (fixed). Blood Sacrifice cannot be used if wizard has 3 or less CON

Other:

Clear selection

Immunity to Disengagement attack (Gipon Prudensco and Nomad's Brigandine)

This effect is one sided: it allows you to engage, yet be immune to dissengagement attacks

Moreover the way it is implemented, incoming dissengagement attack results in a miss.

This miss can trigger Riposte and Offensive Parry (from WotEP).

The cheese part here: you can run back and forth and trigger a lot of dissengagement attacks that will miss you, and trigger a lot of counter attacks. This can be also abused in Turn-Based mode when there is no turn time limit.

Not a cheese. Leave as is

Is a cheese. Yet leave as is

Is a cheese. Change the effect to "Immunity to Engagement". (this completely aleviates the cheese; but will make it harder to tank)

Is a cheese. Change the effect to "-33% damage taken from DIssengagement attacks". Still can be abused with BDD tho

Is a cheese. Change the effect to "+30 defenses vs DIssengagement attacks". Still can be abused with BDD tho

Other:

Clear selection

Submit

Clear form

Never submit passwords through Google Forms.

This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report

Forms