How could that be done with an ember though? That socket is noremove and nouncurse.
I have probably accidentally abused bugs before but this seems hard to justify as "I didn't know it was a bug". If your weapon is proccing sockets that are no longer in it it's a pretty big stretch to think it's a feature..
How could that be done with an ember though? That socket is noremove and nouncurse.
You shouldn't be able to with the ember, so people tend to pick a weapon that procs it already, or they attach it last. In this case, Kreyis comes preloaded with flame.
If it's able to be done then it should be allowed, if it's not supposed to be done then it should be fixed. Wasn't this an issue 20 years ago? Obviously it's allowed since it's been this long. And it's not just the unblockable damage, those procs also have effects:
freezing is - str, shock is lag, flame is blind and acid is + ac, add on top of that critical strikes, a pet and regular class damage output. Enjoy :)
I was going to wait for immortal input as to whether or not the weapon was forged like this or not. I was initially sceptical. I had never discovered a way or thought of bloodvowing any other socketable weapons, and then removing that socket to see if the proc remained. I always took a weapon, and once I had decided upon the socket I would put into it, I never thought anymore about it, let alone attempting to remove it for whatever reason. (I also assumed most end game sockets were no remove anyway)
The weapon itself is meant to be one of a kind, and potentially within the top 3 best weapons in the game. But if you read its stats, it's pretty much a holy damage cursed planar blade.
I don't know what would be more devastating for the player of Phobiant, to suffer a few scratches and grazes each round that may accumulate to 20 - 40 hp per ticket, with a chance of being mini stunned or losing some AC or being blinded. Or if I used an average 31 damage weapon, that isn't an exotic, and perhaps a weapon that he doesn't know, like a spear. Would taking a maim or two per round not accumulate more hp loss? Perhaps, or are you bound to the idea that because this damage is, for the most part unblockable, therefore it's considered overpowered? Most of the damage I am hitting you for is very minimal. I am rolling mostly hits and injures and on the rare high scale maims due to the weapon average being as it is.
I even asked you in game if you'd rather I wield something else till it is decided, but you said it wasn't just the blade that was the problem, and when I probed you on this, you said its not of my concern then quit.
Longevity in most games gives you rewards. In any MMO or fps you will not start off with the best EQ, stats, perks, etc... you will have to earn it. FL is not really different in this aspect so I don't agree that it is a deterrent by any means. Ivesianna started with a level 1 perkless character just like everyone else.
I think the 8 procs a round are a bit ridiculous myself especially with all the random side effects it can cause. It is a bit much but I don't believe it was the winning factor in any fights against Phobiant. Ivesianna is seasoned in her class fighting some of the best PKers regularly, with great equipment, and is an elder in her cabal.
Maybe one of you smart players who knows things about damage can tally up an approximate damage of the procs alone over this battle? Round per round. @Magick maybe? I would be interested to see how it weighed in.
Heh....Kreyis is av 25 Dale. Don't argue with the guy who has it...cause he will win usually, being that he has it and can identify it.
The only two innate procs it has are flaming and poison.
In the log above it was not only searing, but freezing, shocking, vorpaling (acid) and wrathing (blood vow.) So four extra procs, one due to socket, another due to blood vow. So two extra procs. Should it be looked at? Yeah. Are we looking at it? Yup. Is this curiosity the sole reason Ives is beating you down? Probably not.
So this should have been posted on the prayer forum.
This wasn't an issue 20 years ago.
This is the first time I'm seeing that multiple + more socket damage. This isn't the first time I've been told about it. I'm looking into it. Let's stop speculating whether someone cheated or if it's an intentional feature.
Thanks guys, nothing good can come from this thread.