Book of Heroes

Official PvP Beta Feedback Thread- ARCHIVED · page 14

all nice and dandy but as long as a beta isnt supported as a beta should; read: 2-4 updates a week and shitloads of tweaking then u should call it a develeopers alpha.

I've been fairly negative about the current state and seeing how slow the updates come out, the lack of partipation from venan-people (stories about "I read allmost everything" don't cut it), forcing specs to be succesfull (wake up: it's not wow with 10 classes and triple-specs), non-posted data about matches (it's a beta right? where I come from we scrum and help the dev's to tweak etc etc).

All in all I really think u should step up fast with the pvp-experience or just quit it. U did a great job on pve so going back to that solely is hardly a disgrace.

japster

ModeratorFri Aug 16, 2013 7:01 pm
Consolidated my various suggestions made privately to the developers and making them public for sharing. Mostly mages, but some have to do with jc/sw and general pvp suggestions/opinions as well.

1. Scale the power of knock backs and disables in accordance with the speed of the weapon. This will also allow 2handers to be competitive for both wm and justicar, and tunes the power of knockback combos with a 1hander. It also makes sense, since the strong knock backs were designed to allow 2handers a chance to mitigate their slow attacks. Giving the same long knock backs to quick weapons does not make sense.

2. Rework Deep Freeze and Snapcast. Maybe instead of it being a low percentage, allow it to have a guaranteed proc after X number of spells. E.g. Deep Freeze 3 will freeze an enemy after 8 ice spells have been casted on an enemy. This could be a debuff effect much alike to Karnak's Ice Blast that tracks the charges. Application of this charges cannot be resisted, but the final stun/freeze proc can be resisted. This would help eliminate randomness and allow it to be more strategic.

3. Similarly for Snap Cast, maybe allow a spell to be instant cast after 16 spell casts (so it's approximately equal to 6%, 1 in 16 spells)? So it could be like a snapcast charge? Perhaps for snapcast it could be a dual function, e.g. it can proc as usual per the current %, but if the snapcast charge hits 16, the next spell is instant cast. Anytime snapcast procs, whether by charge or chance, the snapcast charges reset to 0.

Deep Freeze could have a similar mechanic as well but Icy Grasp stun might cause coding to be tricky since the system will have to differentiate between an Icy Grasp stun that doesn't reset the charges, and a genuine Deep Freeze proc stun that would reset existing charges. Thus, Deep Freeze may be better off without a dual-system.

4. Allow Fireblast to apply burning effect at 100% chance, if the enemy is currently not burning. And if a justicar's Wound is not reworked, then Fireblast should be allowed to have two chances to apply burning as well. If Wound is reworked then of course Fireblast shouldn't get two chances. But as it is, it would be good if Mages had a guaranteed way to apply their dot on the enemy like a justicar or sw.

5. Seems strange defense enchant is at 1.5% a level while armor pen is at 0.8%. Either nerf defense or buff armor pen to be equal. It's almost common sense armor pen and defense should be natural and direct counters to each other. I don't see why armor pen is made so weak. And mathematically speaking with current mechanics, armor pen is still weaker than damage enchant unless the enemy stacks to about 65% overall damage reduction. And even then it's just marginally better. This seems to give armor pen a huge opportunity cost since it's only slightly useful against a very specifically setup justicar. Most other classes (even if fully geared for damage reduction), do not even come close to such values of damage reduction, and hover more closely around the region of 60% damage reduction on average. Do consider improving armor pen, or nerfing defense enchant.

6. If there's a way to code it, a sw should not be able to riposte and clear knockback times. One huge reason why JC struggle against SW is becase riposte cancels out a justicar's knockback entirely. Riposte should be coded to only reduce the timer of the existing action by the cast time of the ability at least. That way, knockbacks still have some effect.

E.g. if a toxic blade has a cast time of 0.7 and a justicar knockbacks a sw casting toxic after 0.33s with seismic, the sw should have a timer of 0.7-0.33+1.25=1.62. Justicar then uses 0.66s wound which sw dodges and procs riposte. Under this suggested riposte, sw timer goes from 1.62-0.66=0.96s, procs riposte, 0.96-0.7=0.26.

The suggested riposte system allows a justicar to have better chances against a sw and also causes a sw urgency and haste rating to work against him because the faster he casts, the less riposte time he reduces. Hence, this indirectly balances out urgency as well. I was contemplating sugggesting that urgency should be capped and cannot proc to refresh itself when it is already on but if this riposte suggestion is taken, then there is no such need.
japster wrote:Consolidated my various suggestions made privately to the developers and making them public for sharing. Mostly mages, but some have to do with jc/sw and general pvp suggestions/opinions as well.

1. Scale the power of knock backs and disables in accordance with the speed of the weapon. This will also allow 2handers to be competitive for both wm and justicar, and tunes the power of knockback combos with a 1hander. It also makes sense, since the strong knock backs were designed to allow 2handers a chance to mitigate their slow attacks. Giving the same long knock backs to quick weapons does not make sense.

2. Rework Deep Freeze and Snapcast. Maybe instead of it being a low percentage, allow it to have a guaranteed proc after X number of spells. E.g. Deep Freeze 3 will freeze an enemy after 8 ice spells have been casted on an enemy. This could be a debuff effect much alike to Karnak's Ice Blast that tracks the charges. Application of this charges cannot be resisted, but the final stun/freeze proc can be resisted. This would help eliminate randomness and allow it to be more strategic.

3. Similarly for Snap Cast, maybe allow a spell to be instant cast after 16 spell casts (so it's approximately equal to 6%, 1 in 16 spells)? So it could be like a snapcast charge? Perhaps for snapcast it could be a dual function, e.g. it can proc as usual per the current %, but if the snapcast charge hits 16, the next spell is instant cast. Anytime snapcast procs, whether by charge or chance, the snapcast charges reset to 0.

Deep Freeze could have a similar mechanic as well but Icy Grasp stun might cause coding to be tricky since the system will have to differentiate between an Icy Grasp stun that doesn't reset the charges, and a genuine Deep Freeze proc stun that would reset existing charges. Thus, Deep Freeze may be better off without a dual-system.

4. Allow Fireblast to apply burning effect at 100% chance, if the enemy is currently not burning. And if a justicar's Wound is not reworked, then Fireblast should be allowed to have two chances to apply burning as well. If Wound is reworked then of course Fireblast shouldn't get two chances. But as it is, it would be good if Mages had a guaranteed way to apply their dot on the enemy like a justicar or sw.

5. Seems strange defense enchant is at 1.5% a level while armor pen is at 0.8%. Either nerf defense or buff armor pen to be equal. It's almost common sense armor pen and defense should be natural and direct counters to each other. I don't see why armor pen is made so weak. And mathematically speaking with current mechanics, armor pen is still weaker than damage enchant unless the enemy stacks to about 65% overall damage reduction. And even then it's just marginally better. This seems to give armor pen a huge opportunity cost since it's only slightly useful against a very specifically setup justicar. Most other classes (even if fully geared for damage reduction), do not even come close to such values of damage reduction, and hover more closely around the region of 60% damage reduction on average. Do consider improving armor pen, or nerfing defense enchant.

6. If there's a way to code it, a sw should not be able to riposte and clear knockback times. One huge reason why JC struggle against SW is becase riposte cancels out a justicar's knockback entirely. Riposte should be coded to only reduce the timer of the existing action by the cast time of the ability at least. That way, knockbacks still have some effect.

E.g. if a toxic blade has a cast time of 0.7 and a justicar knockbacks a sw casting toxic after 0.33s with seismic, the sw should have a timer of 0.7-0.33+1.25=1.62. Justicar then uses 0.66s wound which sw dodges and procs riposte. Under this suggested riposte, sw timer goes from 1.62-0.66=0.96s, procs riposte, 0.96-0.7=0.26.

The suggested riposte system allows a justicar to have better chances against a sw and also causes a sw urgency and haste rating to work against him because the faster he casts, the less riposte time he reduces. Hence, this indirectly balances out urgency as well. I was contemplating sugggesting that urgency should be capped and cannot proc to refresh itself when it is already on but if this riposte suggestion is taken, then there is no such need.

Some good suggestions there but I'll like to add one thing regarding heavy shield. Only justicars can use it and it increases the block chance as well as block effectiveness without any affect on speed. I believe this should change so that it either does have an affect on speed or be available to all three classes.

If you wanna go with that system for riposte then justicars knockbacks shouldn't do any damage at all like SB.
japster wrote:1. Scale the power of knock backs and disables in accordance with the speed of the weapon. This will also allow 2handers to be competitive for both wm and justicar, and tunes the power of knockback combos with a 1hander. It also makes sense, since the strong knock backs were designed to allow 2handers a chance to mitigate their slow attacks. Giving the same long knock backs to quick weapons does not make sense.
I think this is a good idea. However I'd like it to be traded with DoT timers adapted to weapon speed too (or damage not scaling, either way). The damage bleeds inflicts from a 2h Justi is just crazy right now.

I'm not a big fan of snap cast/deep freeze (does deep freeze actually work in PvP? I still haven't seen it proc at all) appearing after a fixed number of attacks, especially since most of of the time I win or lose before 16.
I'd be more favourable to a higher probability with reduced effect.
Hmm

Maybe ben posted but i got no time to view all posts haha

1-
Can we see our enemy. : crit % Haste % Crit power % Block % Dodge %

... Resist % Etc !!! ?

And 2-
I wanna see some tournaments ( gifts at weekly / monthly even daily pvp rewards !! Like a quest for each one. A day

And to be like top 1000 - 500 - 250 - 100. - 50. - 10. - 5. At weekly leaderboard rewards
And also having a monthly rewards

Also guid fight another guild at pvp choosing 25 guild members or 50 memebrrs to fight each other with pvp matchmaking grants u pvp tokens and some other rewards if ur guild won aginst the other one ( like for example elixir
Or gs. Or. Potions or even gems lol :)

Some nice thing to add ( a guild competition ( u face ur own guild mates ( no tokens no pvp resolvers but in same kind of pvp way but free and its sheduled once or twice a weak by random venan pick to a time !!

What u guys think !!! 8-)
The matchmaking is nearly unbearable. Listen venan, I would rather wait a minute or two longer than face someone with 33% more or even less might than I have. I've read posts of lvl 30 toons with 20k might fighting 30k. This is neither fair nor fun for either of them. The same applies at lower lvls. If I fight someone when I have ~2k might and then have 3k and also are 4 lvls higher than me, they not only are stronger but also have more abilities at their disposal. It is nearly impossible for me to win. Until the system is addressed, PvP has become a feature I do not intend to utilize.
Is anyone else only getting 8-10 pvp tokens upon win/loss. I've spoke to a couple guild mates and some of them are receiving 40-50 upon win/loss. Is there a set standard, because at this rate I will never be able to purchase anything and I'm battling all the time.

Oda_Galen_Shoijikinachi

Sun Aug 18, 2013 2:17 am
This is somewhat a reiteration of my previous post. The "current spec" change doesn't fix the problem you had before. It just changes the problem.

Predominant scenario:
Players have a spec that they almost always want to use for non-PVP activity. They also have a spec that they almost always want to use for PVP activities.

Current problems:
Every time they enter PVP from another activity they have to switch specs manually. Before they leave they have to switch it back... It's the same actions every time. Failure to do so results in problems in some situations. (failed PVP, a dungeon that you have to abandon and loose e on, etc)

Solution:
Make a preferred PVP spec like you had before. When one enters a PVP raid use that spec in PVP. When they exit PVP switch back to the spec they were using when they entered. This makes it all automatic. No problems occur.
Looks like PvP tokens are based roughly on the might of your opponent. .005*might for a win, and about .003*might for a loss. So beating a 20k might toon nets you about 100 tokens, while a loss might get you about 60
Mithrid wrote:
Another statistic: Out of the top25 Overall score, why am I only one of 2 WM...the other being Joker at 16K might who likely is having better luck fighting more inexperienced players at those mights than my Fellow >20k WM's? (No offense Joker, I think its great you're there and I am not trying to diminish your work, Great Job! Just making a point for Darkhorse)
Hm, you was speaking about me?
I was 19k might, not 16k... And ofc it was easy for me to fight always 24k+ rpp especially with john 34,5k and others.
I don't think it was easy battles.

And I'll repost my topic:
NBW_Joker wrote:I'm not going to cry here.
And my wm is not noob wm.
My pvp stats currently 360-145 (1h wm 31k hp)
But anyway clever wm can only win stupid justi and SW, almost no chance with same pvp experienced J-SW. Only with a too much big luck we have a chance...
Frozen shard gives slow in haste.
There are 2 statuses of our slow - so why with no resisting 1 status is not working properly? Sometimes have to cast 3-5 times with resisting chance of the opponent to make it work as it should be.
The biggest problem of wm - low chance. We 100% depend on the probability theory... 30% shield chance, that can work 0-1 times in the battle, or about 20 times... Anyway it's almost useless vs SW, cause they easily ruin this status with their stun/slow/knockback bomb/fast piercing attacks.
Next problem is 75% chance of burning... Which of your workers made this chance so much low? Easily counting 25% of unluck of the chance + 27% of status resist... Too much often I can't burn opponent almost all battle, not speaking of stacking it 3 times...
Other wise SW's slow has a low cooldown (to cast it not thinking about our status resist) and good timed damage...
Our insinerate and ice lancer is nothing with the cast time, cooldown and damage (almost always critical (SW) - I didn't play justi or SW and rly can't understand why they have crits in 80% of attacks... Cause our stat crit max about 40% from items) of all SW's skills...
Their bomb knockback seems can't be resisted by anything... I really can't understand that.
Our passive with 3, 6, 9% freeze chance - could be usefull, but there is no need in it with our burning passive that ruin all freezes... Without this burning we can't do anything.
Anyways wm is weakest class in the game and you can't tell me otherwise.... There are lots of SW's and justi with 400/50 pvp stats, and no wm with much more then half loses in relation to wins.
So I think the only thing should be changed - 100% chance of burning passive, chilled working properly way with both statuses and lower cast time of incinerate and ice lancer...
Sorry for my English, it's not my native language.