Zarant

They use the TBC formula, which basically translates into a 9% hit cap. If you are below 305 weapon skill each point gives 0.4% hit each and then at 305 weapon skill the hit formula changes, resulting in a 6% miss chance and each subsequent skill point after the 305 threshold reduces the chance to miss by 0.1% each. Also, the dual wield miss penalty is exactly 19%.

It didn't, setting agreements and colluding to kill world bosses never yielded a single ban for any of the guilds involved back in the day, however, I'd say that not even 1% of the population even cared about that. I'm sure if blizzard faced the same issue back in the day, if they decided to act on it, they would have responded to it with proper game design, not handing out bans. This whole thing stems from thoughtless game design, the people who populated the database were just trying to recreate Un'goro as close as possible to the way it was on retail without any thought about the implications of their decisions. I don't necessarily blame them beacause from a game designer perspective, it's very difficult to predict player behavior. Right now the only reason the cartel can control the territory is because the respawn locations and timers are just set up in a deterministic way, anyone can figure out exactly where and when the next devilsaur is going to spawn, making it significantly easier to control every single one of them.

When I played on retail, the top alliance/horde guilds from my server were definitely colluding and taking turns on world bosses, if they had some kind of cartel level organization I have no idea, but teaming up just made sense in that context, they could either engage in 3+ hours battles with each other, or they could just take turns and help each other to clear the competition. Blizzard never did anything about it.

I have a decent amount of lean wolf steak stockpiled, but I have no intent in turning them in for the war effort, first because I play alliance and second, because I farmed all that crap slowly over time so I could use them during raids. I have no intent in giving that away just to fulfill some unrealistic demand, farming consumables is boring and it's a huge time sink as it is, i have no intention to make it worse. I could say the same for firebloom, i know a few alliance mages that had a couple hundred stacks stockpiled for future content. edit: nvm i had tender wolf steak not lean wolf steak, the low level food requirements are just ridiculous anyway, no one stockpiles that crap, 450,000 roast raptor wtf

I found out that the assumption from the OP is correct, by bringing the attack power to 0 reduces mob damage by 30%. Mob damage is calculated through the following formula: Damage = BaseDamage * (0.7 + 0.3*AP/BaseAP), This formula only works if a mob has non 0 AP, otherwise its damage won't scale with attack power at all. And I'm pretty sure that demo shout doesn't stack with demoralizing roar.

Now that the project went open source pretty much everything is transparent at this point, most bosses have 290 ap on this server, i will have a look on the attack power formula for mobs some time later and post my findings.

Before the patch 1.9 thunderfury had a 30% proc rate and it could proc off melee attacks AND spells, including poisons and the aoe NR debuff. So even being a MH only weapon, it was bis for rogues.

I can say that the elysium team managed to keep the same blizzlike feel when blizzard nerfed TF on 1.9, which made people complain on the forums and resulted in pretty much all rogues banking it until the 1.12 buff.

It wasn't randomly changed, someone opened a ticket on the bug tracker a couple months ago and the issue was marked as confirmed for a long ass time. Regarding the thunderfury itself, the nost devs made a design choice a long time ago to stick with the 1.11 version of the sword, being usable in the offhand with a 25% proc rate. It wasn't coherent with their progressive itemization philosophy but they arbitrarily decided to add an exception to the rule. On this server TF is currently on its 1.9 state with ~15 percent proc rate.

Are you taking into account the defensive stance modifier? Also, if it deals physical damage there is a chance of being affected by armor. I have data from some strat runs i did, if you consider the average damage being 25 and the average damage reduction from armor being 35%, you have 25*0.9*(1-0.35) = 14.6, which is pretty close to 13, considering that 147 is not a significantly large sample size. One way to test it for sure is by having a druid with tank gear beating on you in caster form w/ 5 sunders (next to 0 armor) and then beating you in bear form to see if armor contribution is taken into account.

Crusader is just slightly worse for fast weapons if you're tanking since revenge is the only special attack that can actually proc something on this server and you only use it every 6 seconds. I never did the math comparing crusader to other enchants, since lifestealing and +5 damage enchants benefits from having fast weapons, but just saying that crusader is shit for fast weapons isn't true on the current state of the game.

Critical strikes can't push misses and glancing blows out of the attack table, however, the felstriker buff itself have 2 different modifiers, one adds 100% crit chance and another adds 100% hit chance, the latter removes the miss chance out of the table.

On top of the 100% crit buff, felstriker also gives a +100% hit chance buff, so crit cap isn't an issue when it procs.

Most of your damage comes from white hits, and unlike rogues, most of your damage from special attacks isn't affected by your top end damage. I would use maladath on the main hand for single target fights.

There is no point in arguing over this, as far as the hit formula goes, there are multiple sources that contradict themselves and based on my experience with other vanilla servers, i can tell that every server uses a different formula. If you want to be thorough, you can either ask a developer with access to the source code or you can gather empirical data yourself, anything else is just pure speculation.

If you have 4-5 players attacking the same target, no mage spamming polymorph can ever stop you from killing that.

This is vanilla wow and socializing is a key aspect of this game, you obviously can't farm a low supply/high demand crafting material by yourself. So instead of crying like a baby, have you ever considered asking your friends for help?

I don't have any kind of reliable source to back up a bug report, I have no clue how it is supposed to work, i can't tell if the current behavior is product of a bug or just a "feature", and to be honest, looking for proof and confirmation is somewhat time consuming, I'm not willing to do it at the moment.

I don't have any kind of reliable source to back up a bug report, I have no clue how it is supposed to work, i can't tell if the current behavior is product of a bug or just a "feature", and to be honest, looking for proof and confirmation is somewhat time consuming, I'm not willing to do it at the moment.

I did some extensive testing w/ thunderfury recently on this server, with about 3800 swings i found out that the proc rate is around 17%, the thunderfury proc itself is considered an ordinary non-binary spell, it does have an intrinsic 17% chance of being resisted against level 63 targets, it can be partially resisted, its crit chance is increased by exactly 10% w/ ony buff and it cannot crit without any spell crit buff. Also thunderfury can proc from most special attacks except shield bash, shield slam, execute and sunder armor. I had no opportunity to test bloodthirst because I don't want to spend 100g just to test that. Thunderfury is not that good, you made a lot of assumptions in your calculations and I'm curious to know where this 70NR figure comes from, do you have any kind of reliable source? The elysium team changed a lot of stuff, pretty much all the knowledge gathered by empirical data on the old nost server might be inaccurate at this point. I really don't know if its intentional or not, without reliable sources no one can distinguish a bug from some design choice made because of the lack of data concerning core game mechanics.

Well, previous experience shows us that you can get banned even if this particular thing isn't explicit mentioned in the ToS.

If you have some kind of way to simulate a static 1 minute fight you don't really need to care about it, you just run the simulation a million times and figure out the average number off attacks per minute. I guess that's what the monte carlo method is all about, but if you manage to do that, the crusader uptime information kinda loses its meaning because you could extract much more useful information from that. Most spreadsheet models are all about ballpark math and thus, only accurate for really long fights.

Modeling crusader uptime is kinda difficult not only because of the overlap issue, estimating the average number of attacks per second is not easy, it includes a lot of other variables, like flurry uptime and extra rage spent with heroic strike and hamstring.

Modeling crusader uptime is kinda difficult not only because of the overlap issue, estimating the average number of attacks per second is not easy, it includes a lot of other variables, like flurry uptime and extra rage spent with heroic strike and hamstring.

I did nothing but white swings + hamstring with a shield. And I'm pretty positive it can proc off hamstring and other special attacks. I used DPSMate to track it, i just divided the number of fatal wound procs by the sum of all the hits+crits from all my white swings + specials.