Resists: Still a Problem

[Vicarious]

What math is there to be done? Sure I can count every spell I cast and try to find a percent of resists but the fact is with my stats as they are, not a single character (excluding the correctly specced rogues, druids, rets) without full raid buffs and a resistance flask should be resisting my fire spells any more than ONE PERCENT of the time, I'd say seeing multiple resists in a matter of 15 minutes proves that something's wrong there. As I've said before I'm pretty sure it's either resistance or spell penetration, the hit seems to work fine, especially since I see a lot less resists from rogues/druids/rets when I get 7% hit.

[Zapcraclepop]

no fix.

That is all we can look forward to, Vic. I applaud your tenacity that you've managed to hold fast onto, despite the constant deaf ears your words fall upon. I kinda envy you for that. Someday, maybe I'll regain my faith that this server isn't doomed.

-Spidercow out

[Cube]

Pretty sure people have done that at some point, man. This is hardly new. Iirc, didn't our old dev do this and stand by the fact it was 1% even when we'd see resist after resist after resist in a row? For all we know, it could be the RNG code that's fucking up. I never meant to imply the code was simplistic in any way, I know better after just producing source code for the shaman templates, which still, managed to fuck up repeatedly. Not that I'm a pro at code, I'll be to the first to deny that. Just agreeing to the fact the code is never as simplistic as we'd hope it to be.

I hope someone will step up to produce some figures then, because as it stands, it's better to play melee right now to avoid the issues.

Peace
-Spidercow out

But as you've stated yourself, something is different now. So whatever someone did at one point doesn't really seem to apply to the situation you're describing.

Basically what you guys are saying is that you cba to search for the problem yourselves, then you get close to offended when Itslovelol doesn't want to do it either. What the fuck?

[Zapcraclepop]

Basically what you guys are saying is that you cba to search for the problem yourselves, then you get close to offended when Itslovelol doesn't want to do it either. What the fuck?

Incorrect. People are providing data, which is being ignored utterly. It's not that we 'cba' to research it... It's that they ignore the findings. How are the players supposed to react?

Personally, it doesn't matter to me anymore. I don't even have the game installed anymore. I'm only replying in hopes of getting more to realize to futility of continuing to try and open their eyes. You'd have a better chance raising the dead. Two years, we all bitched about hit rating being broken. Two years they shrugged it off as RNG just taking a deuce in your face. Finally Henhouse examined the code and thought to have fixed it. But, I don't believe his efforts were successful. That's not an attack towards him, this code is probably a monster. However, it's clearly still not fixed. All we've asked is the code to be looked at, and this dev opts to instead refuse or just ignore us.

At one point, I was just like Vic. I fought long and hard in efforts of bettering this server, to the point where I applied for staff for just that reason. In all that time, you know what I realized?

It's pointless. Completely and utterly pointless. I wonder if that's why Seayan and the others just gave up and left. Some shit will just never be fixed. Like the LoS issues of Hyjal, the PvE content being more broken than American education, or the 6+ year bugs that still persist to this very day.

-Spidercow out

[Vicarious]

Pretty sure people have done that at some point, man. This is hardly new. Iirc, didn't our old dev do this and stand by the fact it was 1% even when we'd see resist after resist after resist in a row? For all we know, it could be the RNG code that's fucking up. I never meant to imply the code was simplistic in any way, I know better after just producing source code for the shaman templates, which still, managed to fuck up repeatedly. Not that I'm a pro at code, I'll be to the first to deny that. Just agreeing to the fact the code is never as simplistic as we'd hope it to be.

I hope someone will step up to produce some figures then, because as it stands, it's better to play melee right now to avoid the issues.

Peace
-Spidercow out

But as you've stated yourself, something is different now. So whatever someone did at one point doesn't really seem to apply to the situation you're describing.

Basically what you guys are saying is that you cba to search for the problem yourselves, then you get close to offended when Itslovelol doesn't want to do it either. What the fuck?

I'm not close to offended because he wants more info, I'm close to offended that a developer is apparently ignoring a problem with the server, a very large problem (that you can't deny exists, nor can he). I'm grateful we have a decent development staff that has been producing great fixes, and that's why I'm pretty annoyed that he'd basically tell us to fuck off with this major server problem, and not even bother looking into it himself, as a developer. Makes the whole staff look kinda shitty, despite their good work recently.

[Itslovelol]

https://www.smolderforge.com/forums/vie ... f=9&t=9475
http://en.wikipedia.org/wiki/Mersenne_twister

[Hartun]

the PvE content being more broken than American education

He doesn't like PvE, and several PvE dedicated guilds left SF for the same reason you stated... $>PvE

[Cube]

Incorrect. People are providing data, which is being ignored utterly. It's not that we 'cba' to research it... It's that they ignore the findings. How are the players supposed to react?

I see no data being provided here. You state that recently there's been a bigger than usual problem with hit, which is where you'd need to look. You can't go by research being done prior to this.

I haven't worked with Itslovelol, but I have worked with Exsurgo. And as long as I've provided him with some solid data, he's always been willing to look into the problems I've brought forth. We solved the haste calculation error a few months back with some simple math (and a code error sorted by Cola). Most of the work was done with a calculator. I found the error in the equation, and Exsurgo and Cola could easily apply it to the code.

[Vicarious]

https://www.smolderforge.com/forums/vie ... f=9&t=9475
http://en.wikipedia.org/wiki/Mersenne_twister

Mirok's shit is irrelevant to this problem, rogues don't build spell hit or spell penetration, of course LD is gonna resist a shitload. And I'm not sure what he means with the pet but casting on a felhunter is suicide since it's resist is retardedly high, and the other way around people will resist spell lock plenty since the felhunter has no spellhit and no spell penetration, like a rogue for example -.- .

A few times in the past and once recently I've set my gear up for 6.97% hit and 93 spell penetration, so against every single class individually there should be a 1.03% chance that they resist my spells (damage specific, non-binary), my stats negate all the die rolls you're considering. Yet, still, resists happen aplenty. I can say I notice it on more on certain classes, warriors and hunters mostly, but that could be coincidence. Unless it's a race bug, since night elves seem to resist more than others (could be coincidental of course).

[Apuclevercow]

If Owl could show us how he does with his recount to check resists, you could probably do your tests Vica.