![]() ![]() I mean, everything you think should be easy is almost never that way. We could just put a 30% pvp nerf on vaporize, and then buff up scald, eb, flamewalker, SP, by 15% in pvp AND not changing the overall flow of the soul Q: So you basically need a find a way to deflate the burst and even out the flow of continuing damage without nerfing overall DPS? and just nerfing their top end burst makes them worthless so it’s a really hard problem to fix overall Primalists tend to load all that damage into a narrower window. This works fine in PVE where fights can last long enough.īut in PVP is dangerous if the damage is high enough Q: What’s the hype about Primalist? people saying they get one shotted and us prims saying it takes a lot of ramp up to reach thatīurst specs are balanced around their ability to ramp up, do a bunch of damage, and then cycle down. It happened a handful of times and you remember it because its jarringĢ) that isn’t contributing much to their chances to win a match even if they were doing it as often as the forums say So when the forums complain about “I’M CONSTANTLY GETTING ONE SHOT” the data says:ġ) no you aren’t. NA had a single spec that was about 180 from 1500, everything else was within 60 Yup, It also means we can sift out the hyperbole.įor example, in EU this week no spec was more than 60 points from 1500 (which in terms of elo is statistically insignificant), EU was pretty balanced overall. Q: So even if people find an op thing and don’t talk about it on forum etc, you can still track it right? So a spec that has a lot of players and is bottom of the barrel means that the data is relatively certain and that in comparison to the other specs appearing it performs worse in the time frame. We also see how many people are using the spec. So every spec that gets played gets added to that list at exactly 1500 (starting elo), and then the Spec’s elo is tracked as players play, regardless of who plays it. We actually have a reporting tool that tracks any given spread of a spec on an elo (which we reset weekly). Shoutout to Hepatitis for helping to compile portions of this! As usual, all details for future changes are subject to change, and should not be taken as 100% guaranteed to happen. The purpose of this post is to summarize the general thoughts of Rift’s dev team. ![]() Again, I will not call out dev or player names here. Since conversations like these can often be difficult to read, follow, and review, I will do my best to summarize several discussion points from the devs on Discord. You can join the Rift Community discord here: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |