Posted on: April 30, 2025
Gannv
Zweryfikowany użytkownikGry: 102 Opinie: 1
Wrathfinder: Path of the Quicksave
Game can be enjoyable, if you like experimenting with builds there are TONS of options, quest line is generic but serviceable, companions are enjoyable to interact with so nothing to complain there. Option to change from real time to turn based on the fly prove to be more useful that I initially give it credit (literally life saver in multiple cases) However, game is destroyed by terrible phasing. Fights that you will sneeze at are just next to the fights that will wipe your party clean. This is not helped by the fact that game has challenging optional encounters and multiple scripted fights that you survive thanks to cutscene just next to each other. There is no way of telling if you are destroyed by design, you are unprepared or you just opened wrong door. There are multiple of conflicting mechanics. For example game encourage you to be prepared all the time but if you do you will burn out before final encounter and if you rest to often game will punish you with corruption mechanic. Real time/turn based combat also collide with each other, in some fights things go not as intended due to you being in wrong mode. Crusade thing is just unnecessary roadblock you can turn it off but then you are missing on stuff but if you don't you are stuck with bad strategy mode. The worst thing is of how easy you can hard-block yourself: Long sequences without ability to withdraw, check Hard forced encounters that you can activate just by playing game as per usual, check Locking yourself from character development path because you missed single timed trigger, check. All above make for horrible first play, in my 30 years of playing games this is first time that I was saving so often it become noticeable. Lastly on the EULA thing. It has been hammer to the ground so let me add just one thing. I turned off "data harvesting" in options and created rule in firewall just to be sure. At the end of Chapter 1 I checked how many times .exe tried to breach the rule. It was 150+ times.
Czy to było pomocne?
