I found that whenever he 'paused' on the other side he would just come back over to my side with an absolute ton of furies with him. Don't get greedy either, just take the easy hits and you should be fine. If you get to the top of the screen, pop your teleport and replace it.Įasy fight from here on out, just stay on those two right platforms. If done right, you should get the boss and zero or 1-2 furies( more can come, but we want 0-2 if you can manage go ahead), the boss will attack in a circle.
We want the pink "incoming boss attack bubble" to show up. Kill any incoming furies by moving closer to the right side of the screen. Kill the remaining furies on the bottom right platofrmmand redropmyour shadow.Īfter 45 seconds or so, inch left and up.SLOWLy. When he comes in, if he drops in the easy hit spot to do his pink attack, hit him 4 or so times and drop down and book it to the bottom right platform.DROP YOUR SHADOW!įrom the bottom right platform, wait for him to come at you, and if you can hit him once or twice, and book it to the top left platform. So he will just loop around the left sides platforms allowing you to hit him quite easily.
This glitch only worked a few times for me, but Alexander should move over to the left, and no skulls will follow him period. If he doesn't move back after at least 30 seconds, jump close to the middle spikes to attract him to the left. If this works properly, you won't see any skulls on the left and there will be a lengthy delay before Alexander even starts to move back to the left. Draw Alexander as close as you can to the far right wall of the right side, then quickly dash back over to the left. Dash over to the right side, kill as many skulls as you can just to clear some room and get some health if needed. Try to position him where you can attack him while he's shooting (this make take multiple retries until the AI cooperates).ģ. Jump to the top platform and wait for Alexander to advance towards you while getting in some hits in, and jump downĢ. But the strategy that worked for me was a tad bit simpler.ġ. A lot of strategies involve standing on the spikes or farming the small skulls. The psuedo-randomness to me, was what made him the most difficult.
RAM: Total: 15.57 GiB Available: 11.34 GiB OS: LinuxMint KERNEL: 5.15.0-33-generic ARCH: 圆4ĬPU: Intel Core™ i5-6600K GOVERNOR: performance Launch Command: WINEARCH=win32 WINEPREFIX=/media/alexander/Twery/HeroicLibrary_m2/Winebottles/wine32test-RogueLegacy WINEESYNC=1 /usr/bin/gamemoderun /opt/Heroic/resources//build/bin/linux/legendary launch 01f1e8046e9e433db190a611a0411579 -wine /home/alexander/.config/heroic/tools/wine/Wine-GE-Proton7-11/bin/wine -wine-prefix /media/alexander/Twery/HeroicLibrary_m2/Winebottles/wine32test-RogueLegacy Epic games versions of 'Rogue Legacy' and 'Salt and Sanctuary') Add logs I know it was working to create 32-bit prefixes in previous versions as I had created them this way for a couple of games that are only working in wine 32-bit (e.g. So the problem only appears to be when the wine prefix is created the environment variable is not respected. "wine: WINEARCH set to win32 but '/media/alexander/Twery/HeroicLibrary_m2/Winebottles/wine32test-RogueLegacy' is a 64-bit installation." However it is not doing that anymore and is always creating a 64-bit prefix despite a WINEARCH=win32 environment variable being set.Īfter the prefix is created the environment variable is being respected as subsequent game runs are correctly giving an error log e.g. In previous versions of Heroic (I think pre-2.3.0) one could set an environment variable on a game for WINEARCH=win32 and when the game was first run the wine prefix would be created as a 32-bit prefix.
0 kommentar(er)
