#121
|
||||
|
Quote:
Reread the thread. They've been here. They've heard us. They don't care. | |||
|
#122
|
|||
|
They'll get around to it. They probably aren't extremely concerned with this issue since it literally only affects three items in the game, and developer bandwidth is already stretched pretty thin. It might be one of the most important issues for rogues, which is what I main, but developing game content like Chardok 2.0 etc. is still more important imo.
| ||
|
#123
|
|||
|
Seven months and no confirmation that they consider it a bug. Could a dev take 10 seconds to quote my post and say "It's a bug" please?
| ||
|
#124
|
|||
|
I know the staff is doing all this for free, and cutting them some slack etc. thank more complain less etc.
But after a while... its like really? I see new bug posts about trivial things like wrong spell graphics being responded to and fixed, lots of low hanging fruit being looked at. But the ones that are actually detrimental to players and theres a big push/interest in - stubborn silence. Its like they'd rather work on changes that make it harder for players. God forbid they prioritize fixes that would actually benefit players for once... dont even get me started on their fuzzy 'classic' logic they apply intermitently. 'Aoe cap to 25 because computers wouldnt have been able to handle it back then'... just say you want to stop chardok pulls... dont dance around the issue. Things like that just demonstrate lack of conviction. And thats why it feels like passive aggressive, uncommunicative, and out of touch staff. Ugh...I think i enjoyed playing more when i didnt read the forums... ignorance is bliss. On the upside - Cant wait for Path of Exile new update! Buying an xbox just to play their port! | ||
|
#125
|
|||||||
|
Quote:
Quote:
Quote:
Quote:
| ||||||
|
#126
|
|||
|
@paul
thanks for bump | ||
|
#127
|
|||
|
Bump
| ||
|
#128
|
|||
|
People reply to this thread like it was a new bug. If my previous replies were not clear, this has never worked as intended, since the modifications I made didn't affect it. Resolving the other issues brought this into the spotlight.
I was hoping for a real fix, i.e. code developers discover why Haste effects built into spells were not functioning properly, and go from there. Unfortunately, this didn't occur soon enough. So, I will look into suggestions posted here, such as removing Haste component from the spell, and adding a set Haste amount to the item itself. | ||
|
#129
|
|||
|
That is great news!
Thank you! | ||
|
#130
|
|||
|
thank you Nilbog !
__________________
Eratani / Cleratani / Eratou / Stabatani / Flopatani / Eratii
| ||
|
|
|