Impact Bug
Impact Bug
Impact is bugged to shit. At 10% it makes no sense that every fire mage fight involves 2-3 stuns from impact when its supposed to be averaging 1 stun per 10 attacks.
Please look into this.
Please look into this.
Re: Impact Bug
If the mage has Molten Armor/Molten Shields it will proc a lot.
Balls, Cube, Deems, Google [Bot]
Re: Impact Bug
Thats my point. I find it hard to believe it should proc that much, even with the molten armor talent spec.
Re: Impact Bug
I don't follow your reasoning on that one. If you use Molten Armor (and Molten Shields if necessary for the example), you'll have a 10% chance of stunning a target every time you use a fire ability against him, and every time he uses anything target specific against you, including auto attacks. So your point seems fairly weak.
But by all means, test it. If you find something off with it, report it.
But by all means, test it. If you find something off with it, report it.
Balls, Cube, Deems, Google [Bot]
Re: Impact Bug
Says the guy who plays a mage. I don't blame you for being bias since its your class but I think its worth looking into whether or not impact should be proccing as much as it should.
Re: Impact Bug
that is just bullshit.. you simply got raped by mage
have you tested it? nope? then why are you even making this threat?
i can make 100 threats about talents that im my opinion might be bugged
this goes also with people who keep saying that ressilience is bugged, mace stuns and so on.
tbc is really about RNG - deal with it
have you tested it? nope? then why are you even making this threat?
i can make 100 threats about talents that im my opinion might be bugged
this goes also with people who keep saying that ressilience is bugged, mace stuns and so on.
tbc is really about RNG - deal with it
Re: Impact Bug
Dude you need to read the context of what I said. I said its worth looking into. Does it need to be fixed right now at this very minute? No.
Do I care all that much about it? no not really.
Dont sit here and tell me that private servers dont have their share of bugs and that impact may or may not be bugged.
Hence why the only thing I said was ITS WORTH LOOKING INTO.
Do I care all that much about it? no not really.
Dont sit here and tell me that private servers dont have their share of bugs and that impact may or may not be bugged.
Hence why the only thing I said was ITS WORTH LOOKING INTO.
Re: Impact Bug
No. The guy who plays a mage says that the proc rate seems fine, while the guy who doesn't play a mage says that the talent is bugged with no proof to back it up. As said, test it and post a detailed bug report with some solid evidence, and I'm sure they'll look into it. If the talent would happen to be bugged, I wouldn't mind it getting fixed. I'd support it.Kylah wrote:Says the guy who plays a mage. I don't blame you for being bias since its your class but I think its worth looking into whether or not impact should be proccing as much as it should.
Unless something has changed recently that have messed with the talent, it's fine.
Balls, Cube, Deems, Google [Bot]
Re: Impact Bug
Its not my job to test shit. That's the developers job. They got elected to do that, not me. So no I'm not going to personally test it and see whether or not its bugged since. Its my job to bring things to light that may or may not be bugged.
Ill repeat my self for the 3rd time now and say its worth looking into.
Ill repeat my self for the 3rd time now and say its worth looking into.
Re: Impact Bug
The one and only developer we have here didn't get elected by anyone. He volunteered to spend his free time fixing the server. It's not his job, it's his choice. What you're saying isn't that 'it's worth looking into'. You're telling the developer that that his free time is worth spending on replicating an rng based mechanic that might be bugged according to one person who doesn't supply any evidence at all to support his claim.Kylah wrote:Its not my job to test shit. That's the developers job. They got elected to do that, not me. So no I'm not going to personally test it and see whether or not its bugged since. Its my job to bring things to light that may or may not be bugged.
Ill repeat my self for the 3rd time now and say its worth looking into.
I think he'll be the judge of what his free time is worth being spent on.
And if you haven't noticed it, there's a bug report submit form that you're supposed to follow when reporting bugs. One of the questions being asked in said form is 'how can you reproduce it?' Some sort of information other than 'it's bugged to shit' would most likely be appreciated by the dev. And if you want it being looked at, I'd guess you'd have to come up with something solid for him to work with.
Balls, Cube, Deems, Google [Bot]
Who is online
Users browsing this forum: Bing [Bot] and 1 guest