Delete Volatile Plants from the Game
This piece of gargabe game implementation should be removed from the game immediatly. It is so heavly overtuned, more than anything else. I've died countless times to this sh*t because of too many effects overlapping at once and being unable to see them. It is also a f*cked up that these things still exist AFTER the mob is dead.
Will not play this game anymore until it is removed. ขุดครั้งสุดท้าย เมื่อ 3 มิ.ย. 2025 13:37:35
|
![]() |
Chaos resistance is for the pros. Go play CI. xD
HC SSF. What else? Ruthless when?
|
![]() |
It really is badly designed.
Even when you SEE them clearly, and do your best to avoid them there are many situations where you can get stuck in mobs and obstacles and you end up eating them anyway. That's not even mentioning how Rituals spawn in cramped areas all the time making it difficult to dodge volatiles. It's a badly thought out mechanic that should be removed because it's 1) incomplete 2) unfair 3) unfun. Seriously when is the last time you survived volatile plants and thought "wow I did it! I am a better player today!" NEVER. THere's literally never a moment where learning to dodge this stupid mechanic brings a sense of accomplishment. |
![]() |
While we are at it, could we also delete volatile craig? like WTF is this garbage mechanic.
|
![]() |
" fuckin craig, i knew he was no good |
![]() |
I don't hate these mechanics on principle, but there are so many ways to get stuck on terrain and eat a volatile orb you thought you told your character to dash through.
I think orbs and crags would feel more balanced if player collision were more forgiving, or if movement abilities had faster animation times. Although the latter creeps us toward PoE 1 territory and devs are no doubt trying to avoid that. Maybe best of all would be for them to just spawn less frequently. Right now if you avoid one wave of volatiles the next wave is already headed for you. |
![]() |
I can understand the problematic in rituals were we have most often cause of map design not much space to handle them, but in maps in general they are not a big issue I think.
|
![]() |