Animate Guardian
this fix, its perfect and i love it thank you!
|
![]() |
@Staff
Please clarify what exactly constitutes the same area. Does that mean 'instance' or does it go by name of the actual area, e.g. Belly of the Beast in campaign? Under which condition is the lock reset, when can i reuse it again? Or will it remain locked forever there? Will the guardian be prevented from entering a certain map forever if it has died there once before in any previous instance? What happens when i try to resummon it while targeting an item, effectively changing the guardian and sacrifing items. Will that be possible? If not, the skill has just become much worse for leveling and just going by what drops on the way (effectively unusable anymore). Update I managed to test one thing at least: It is not possible to re-summon a killed guardian in the same area instance by changing its composition (targeting another item). I think this is a bad design as it effectively disables any kind of play that utilizes rares found 'on the go'. I also don't understand why we don't get a (read only) UI to see what is equipped to the guardian. The information does have to be stored either way. This should be an elementary part of the skill, now that it retains its items even more so than ever. Think about console players. There's no copy-paste of item properties to a text editor there. What shall they do, make pictures of the TV screen with a smartphone? What kind of skill actually requires external tools to be used according to its core design? Última edição por GaryBlack88#0544 em 20 de jun. de 2025 04:08:53
|
![]() |
my post from may/2024 are more actual now (ok one suggestion of my and many other ppl was concluded), but still have nice good ideias in this post... and now many ppl will use AG (with or without mercenaries going core in 3.27:
" - Thread with suggestions for PoE 1 get more fun and more QoL in next patches (3.27, 3.28...): thread/3812167 - Atlas tree thread improvement: thread/3812454 (English is not my native language, so I apologize for any mistakes!) Última edição por Rato86#5476 em 12 de jul. de 2025 14:39:13
|
![]() |