Icy_Nelyan wrote: »Not always you can block bow proc, for example when under CC or when in the middle of the fight against someone else, or well, because they shoot you from stealth/invisible close to melee range while you are not aware of them.
In addition most people play this game without sounds so it is not easy to hear the boom sound from the bow, not counting that, even if you play with sounds and effects, when you are in a fight against others there a many different sounds/effects that sometimes notice something specific is a bit hard.
And as a side note not all nightblades shoot their merciless resolve after they hit you with their ulti or only as an execute, I play a non-invisible mage like nightblade and I don't play that combo, I even use meteor ulti and not the class one to empower damage and still my bow melts people.
So "dodge it", or "block it" or "you cannot notice that when they fire it because of noise it produces" are the most useless and unhelpful comments a person may write ^^.
Icy_Nelyan wrote: »Not always you can block bow proc, for example when under CC or when in the middle of the fight against someone else, or well, because they shoot you from stealth/invisible close to melee range while you are not aware of them.
In addition most people play this game without sounds so it is not easy to hear the boom sound from the bow, not counting that, even if you play with sounds and effects, when you are in a fight against others there a many different sounds/effects that sometimes notice something specific is a bit hard.
And as a side note not all nightblades shoot their merciless resolve after they hit you with their ulti or only as an execute, I play a non-invisible mage like nightblade and I don't play that combo, I even use meteor ulti and not the class one to empower damage and still my bow melts people.
So "dodge it", or "block it" or "you cannot notice that when they fire it because of noise it produces" are the most useless and unhelpful comments a person may write ^^.
Dodging or blocking is literally the counterplay against Merciless Resolve, so the only useful comments are "dodge it", "block it" or if you cant do that "learn to play".
Major_Toughness wrote: »Why are you not blocking bow procs if you claim you know how to play against NB's?
Icy_Nelyan wrote: »Icy_Nelyan wrote: »Not always you can block bow proc, for example when under CC or when in the middle of the fight against someone else, or well, because they shoot you from stealth/invisible close to melee range while you are not aware of them.
In addition most people play this game without sounds so it is not easy to hear the boom sound from the bow, not counting that, even if you play with sounds and effects, when you are in a fight against others there a many different sounds/effects that sometimes notice something specific is a bit hard.
And as a side note not all nightblades shoot their merciless resolve after they hit you with their ulti or only as an execute, I play a non-invisible mage like nightblade and I don't play that combo, I even use meteor ulti and not the class one to empower damage and still my bow melts people.
So "dodge it", or "block it" or "you cannot notice that when they fire it because of noise it produces" are the most useless and unhelpful comments a person may write ^^.
Dodging or blocking is literally the counterplay against Merciless Resolve, so the only useful comments are "dodge it", "block it" or if you cant do that "learn to play".
Learning to play while under CC is pretty pointless, if you are able to dodge or block while stunned or when you are not even aware of the nightblades ready to shoot the bow against you, you probably aren't even human, still the comment is highly useless and unhelpful.
In addition, if while fighting against 5 or more enemies, you are able to predict all your target moves able to know what skill/spell they are going to fire in every moment, you are wasting your time on this game, you ahould spent your time better making tons of money and kickstart the humanity directly into the future.
1v1 is a way more different topic, but it wasn't what I was talking about.
So saying "dodge it" or "block it" is useless since, again, it can't be done sometimes.
These statistics aren't very reliable for several reasons:
- The PvP mode in which you play largely determines the classes encountered, thus distorting quantitative statistics.
- Character deaths typically involve more than one player, often the one dealing the most damage doesn't deliver the killing blow, leaving classes without finishers at a disadvantage. The amount of damage dealt is much more reliable (as in battlegrounds).
I'm not saying you're wrong, but these statistics are rather unreliable, especially considering the small sample size.
Major_Toughness wrote: »Why are you not blocking bow procs if you claim you know how to play against NB's?
I agree on that - Killcounter doesn't show any good statistics for many reasons.While I wont deny Nightblade is popular... A big reason it's high on your kill list is because bad Nightblades are everywhere and thus easy to kill. As for dying by nightblades? They do a lot of dmg and a lot of people just Xv1 with bows.
Though the point of nightblade being popular still stands I'm pretty sure these stats aren't that accurate number wise.
I don't know mate... I play without significant resistances and no vampirism out of spite, still having a chance to react against these arrows even if eating an incap beforehand. It just really not hard to predict and except these kind of attacks. If you are on 50-70% of health, there is no law against healing yourself if you feel like the NB have it's ultimate up. Really sounds an issue of expertise. Nothing wrong with it, but doesn't really make it impossible to defend against. In fact, it's relatively easy to avoid.
Also 33k resistance isn't that big of a deal, considering the amount of penetration and % based damage increases. 10k crit in that case is quite low and easy to shrug off.
StaticWave wrote: »Lol the comments telling OP and @Icy_Nelyan to "just block" are pretty hilarious. Here's what most of them don't get:
1) Top tier NBs play the class more like a pressure build instead of pure burst. Obviously, they'll combo bow proc with Off Balance or Incap debuffs when available, but when they aren't available, they will use bow procs on cooldown.
So what's going to happen in a 1v1 against a top tier NB is you have to block cast pretty much everything. If you don't, you're going to eat a bow proc every 5 seconds or so. When you get Off Balanced or Incapped, you will literally have to hold that block button or spam dodge roll until they expire. But that brings us to the 2nd point:
2) Top tier NBs will light attack > Concealed > bash every single GCD. That will drain your stam twice if you just hold block, or drain your stam once if you block cast. You can test that yourself if you doubt me.
So imagine trying to hold block so you don't get stunned by Off Balance and get your stam drained twice every second, or block cast and risk getting stunned into a bow proc because of latency. Next patch Incap gets 12s of duration too, so good luck trying to block cast thru 12s of taking 20% more dmg.
So in short, yes, telling people to "just block" is nonconstructive lol. There's a reason why NB is currently one of the strongest dueling specs in the game. The top NBs already know their combo is easy to avoid. That's why they aren't going to be predictable. They'll combine a bunch of combat mechanics together to create a high "APM" playstyle that converts the bursty nature of NB into pressure. Now add 1-2 procs on top of that, and you have yourself a class with pressure and unmatched burst.
StaticWave wrote: »Lol the comments telling OP and @Icy_Nelyan to "just block" are pretty hilarious. Here's what most of them don't get:
1) Top tier NBs play the class more like a pressure build instead of pure burst. Obviously, they'll combo bow proc with Off Balance or Incap debuffs when available, but when they aren't available, they will use bow procs on cooldown.
So what's going to happen in a 1v1 against a top tier NB is you have to block cast pretty much everything. If you don't, you're going to eat a bow proc every 5 seconds or so. When you get Off Balanced or Incapped, you will literally have to hold that block button or spam dodge roll until they expire. But that brings us to the 2nd point:
2) Top tier NBs will light attack > Concealed > bash every single GCD. That will drain your stam twice if you just hold block, or drain your stam once if you block cast. You can test that yourself if you doubt me.
So imagine trying to hold block so you don't get stunned by Off Balance and get your stam drained twice every second, or block cast and risk getting stunned into a bow proc because of latency. Next patch Incap gets 12s of duration too, so good luck trying to block cast thru 12s of taking 20% more dmg.
So in short, yes, telling people to "just block" is nonconstructive lol. There's a reason why NB is currently one of the strongest dueling specs in the game. The top NBs already know their combo is easy to avoid. That's why they aren't going to be predictable. They'll combine a bunch of combat mechanics together to create a high "APM" playstyle that converts the bursty nature of NB into pressure. Now add 1-2 procs on top of that, and you have yourself a class with pressure and unmatched burst.
I'm glad someone is here to say it, I'm by no means a top tier NB player but even I grasp this concept
Major_Toughness wrote: »Why are you not blocking bow procs if you claim you know how to play against NB's?
Sure in a 1vX or XvX situations is really easy block and rolldodge all damage you take...
You think in cyro all is 1v1 and you can do something when stunned and you can predict all movements? Literally nosense comment xd.
You must be the best player even in poker lol.
Major_Toughness wrote: »Major_Toughness wrote: »Why are you not blocking bow procs if you claim you know how to play against NB's?
Sure in a 1vX or XvX situations is really easy block and rolldodge all damage you take...
You think in cyro all is 1v1 and you can do something when stunned and you can predict all movements? Literally nosense comment xd.
You must be the best player even in poker lol.
So you died because of a CC from another player, who might not be a NB?
If you are outnumbered and getting CC'd, unavoidable at times I know, how is that a class problem. You were likely to die anyway.
NB and Sorcs are the most common classes in PVP if you do not see that then you do not PVP. People play the most effective classes not the least effective. DK is a strong 3rd option atm. (Arcanist still to new IMO)
All you have to do is look at the top 100 per class and look at the minimum AP to get into the top 100 and you quickly see the most popular classes.
acastanza_ESO wrote: »NB and Sorcs are the most common classes in PVP if you do not see that then you do not PVP. People play the most effective classes not the least effective. DK is a strong 3rd option atm. (Arcanist still to new IMO)
All you have to do is look at the top 100 per class and look at the minimum AP to get into the top 100 and you quickly see the most popular classes.
I actually have hard data here. Sorc is roughly tied with DK with Warden only a hair behind.
I created a new character at the beginning of U40 and have played almost 6 nights a week in Blackreach (or during mayhem side campaigns).
I parsed my killcounter data through last night for this new character, and computed unique characters. So this will encompass all characters that either I killed or killed me and each character is only being counted once.
The data totals 2650 unique encountered characters.
Keep in mind that the sorc numbers are boosted by all the new and returning sorcs from the last two nights.
You can clearly see that NB is still head-and-shoulders more popular than any other class. Sorc and DK are roughly tied for second. Then Warden at a clear third. Templar 4th. Arcanist 5th (this data should be outside the initial spike in Arcanist FotM on release popularity), and Necro dead last by a massive margin.
Sorry to tell you, that this are not really "hard data". (But they look nice - good presentation)acastanza_ESO wrote: »I actually have hard data here. Sorc is roughly tied with DK with Warden only a hair behind.
I created a new character at the beginning of U40 and have played almost 6 nights a week in Blackreach (or during mayhem side campaigns).
I parsed my killcounter data through last night for this new character, and computed unique characters. So this will encompass all characters that either I killed or killed me and each character is only being counted once.
The data totals 2650 unique encountered characters.
I restarted my statistics (PvP addon) a month or two ago and in this chart you can see how well balanced is the game around nightblades, the class that kills me more than a third (34.35%) of the time is nightblade meanwhile necros not even 2% of the times and well, templars just because of the op radiant oppression, if not they couldn't kill anything because jabs is a wet noodle.
The difference between classes is abysmal.
Don't think is because i dont know how to play against nb because I have 33k resistances and more than 50% crit resistance and merciless resolve hits me around 10k each time if I am not blocking
That said, ZOS, if you are gonna add more content to PvP in Q4, just fix your game first.
acastanza_ESO wrote: »NB and Sorcs are the most common classes in PVP if you do not see that then you do not PVP. People play the most effective classes not the least effective. DK is a strong 3rd option atm. (Arcanist still to new IMO)
All you have to do is look at the top 100 per class and look at the minimum AP to get into the top 100 and you quickly see the most popular classes.
I actually have hard data here. Sorc is roughly tied with DK with Warden only a hair behind.
I created a new character at the beginning of U40 and have played almost 6 nights a week in Blackreach (or during mayhem side campaigns).
I parsed my killcounter data through last night for this new character, and computed unique characters. So this will encompass all characters that either I killed or killed me and each character is only being counted once.
The data totals 2650 unique encountered characters.
Keep in mind that the sorc numbers are boosted by all the new and returning sorcs from the last two nights.
You can clearly see that NB is still head-and-shoulders more popular than any other class. Sorc and DK are roughly tied for second. Then Warden at a clear third. Templar 4th. Arcanist 5th (this data should be outside the initial spike in Arcanist FotM on release popularity), and Necro dead last by a massive margin.
Sorry to tell you, that this are not really "hard data". (But they look nice - good presentation)acastanza_ESO wrote: »I actually have hard data here. Sorc is roughly tied with DK with Warden only a hair behind.
I created a new character at the beginning of U40 and have played almost 6 nights a week in Blackreach (or during mayhem side campaigns).
I parsed my killcounter data through last night for this new character, and computed unique characters. So this will encompass all characters that either I killed or killed me and each character is only being counted once.
The data totals 2650 unique encountered characters.
First of all - I like that you at least look for unique encounters - that's much better then most ppl do when they look on kills/death only. This helps a lot to go arround many of cons of killcounter.
Because Killcounter has many cons - The biggest problem is that only killings are included.
Every stalemate fight - every succesful escape (cloak/streak) is not inside.
And ofc a high risk high reward class like NB will always be overpresented then a turtle class.
Just as an example - IF sorc were unkillable now - you would not see them...
And playing during MYM and counting kills only is bad on it's own, bc you will kill many PvEers much easier then PvPers and this makes kill based data even worse.
Then - it's only your playstyle and your class (and data from different build/class/playstyle could look different) - but as I said before - at least your way to look for unique occ is leveling out some cons...
I guess the data would be even better, if you only count unique player who are killed/killt you minimum X times. This would at least even out some more PvE player which only play for tier1-3.
Btw: I would recomment to cp/mv killcounter.lua in the "SavedVariables" folder to get fresh U41 data over time, bc U41 is a major change in my opinion...
And thats another problem of killcounter to get fresh data over time and not get only a mean from the hole duration.
As said - MYM included is anyway not the best time to get the "real" data - whatever the "real" data is
But here is the biggest issue, why your data is only a very narrow view and maximum "hard data" for "Blackreach PC/??".
(sitenote: Would be interesting where you play! I assumed you play NA - but from my data I would guess you have to play EU, because my data show a too different picture for blackreach....? But It would fit quite good for EU.)
I analyze the data since U35 with different ways (before I used only killcounter) of "Top100 data" and I do this for both CP campaigns on EU and NA. (I would like to see consoles too, but unfortunately....)
And over the time since U35 I could see so many differences between the campaigns and their population.
It is quite astonishing how different the campaigns and platforms are in relation to the population.
So - again - I like your way and the presentation and it's much better then just a random guess or whatever.
But it's an overestimation to think that this is the truth and that would be hard data for statements like:
"Sorc is roughly tied with DK with Warden only a hair behind."
From my data sorc is already (that means U40, bc I need time to get U41 data - minimum 3 month for a samplesize I trust)
more played then DKs. But - it doesn't matter if my data are better then yours or vice versa!
I agree on "You can clearly see that NB is still head-and-shoulders more popular than any other class" - I don't know if this will change enough with U41 to get sorc on top - but I doubt it. The advantage is to huge in my opinion and NB got nice buffs too.
import luadata
pvpdatafile=open('PvpAlerts.lua','r') #The Path To Your PvpAlerts SavedVariables
pvpdata=pvpdatafile.read()
pvpdatadict=luadata.unserialize(pvpdata)
pvpplayerdb=pvpdatadict
filter_value = 1710144000 #Last Seen UnixTimestamp for U41 Release
unit_class_counts = {}
# Iterate over each character's data
for character_data in pvpplayerdb.values():
last_seen = character_data.get('lastSeen', 0)
if last_seen > filter_value:
unit_class = character_data.get('unitClass')
if unit_class is not None:
unit_class_counts[unit_class] = unit_class_counts.get(unit_class, 0) + 1
# 1 = Dragonknight, 2 = Sorcerer, 3 = Nightblade, 4 = Warden, 5 = Necromancer, 6 = Templar, 117 = Arcanist
print("Aggregated Data:", unit_class_counts)
First of all - ty for your answer - I really like how you do your work and handled my input/criticism.acastanza_ESO wrote: »Some really good points here. It is actually Blackreach on PCNA. One caveat I missed that you also didn't mention is that my guild only plays AD so this would be better framed as a representation of the composition of EP+DC. If you fight against AD that may be contributing to a difference in the class composition.
That said, my guild leaves no survivors and doesn't run away so I would argue that it is a reasonably accurate composition of those enemy factions for that timespan.
The point about Mayhem is well taken. I hadn't actually been intending to do this comparison, it was pure coincidence that I started a new character with a fresh KillCounter when I did.
Wow - that is by far the best data I could imagine.acastanza_ESO wrote: »I actually do have a better way to collect this data going forward. Miat's PVP Alerts creates a database of characters that you encounter in Cyrodiil, it logs from both your reticle as well as the KillFeed. As it turns out, I'm the new maintainer for Miat's PvP Alerts and in the version on Minion I updated that player database creation function to include a last-seen datestamp. I did need to set it up to backfill the databse with the date you install the update for compatibility, but going forward it should be possible to query out a much more accurate representation of the class composition by parsing this data.
Major_Toughness wrote: »Why are you not blocking bow procs if you claim you know how to play against NB's?