That last point makes fighting the many flying robots an absolute pain in the neck as you have to exit ADS, run to a better vantage point, and then aim again. Each of the five weapons is slow and unwieldy, aiming down the sights slows you to a frustrating crawl, and you can’t point your weapons very high in the air at all. It's all surprisingly elementary for how complex some of the circuit mazes appear to be at first, and it’s downright disappointing that they never present any kind of challenge.īut of all the gameplay disappointments in Recompile, combat is by far the worst offender. You need only hop on a few buttons in a random order to solve them through process of elimination. In fact, if you’d rather not spend the time to figure out each puzzle, that’s completely fine. If you’re a fan of redstone circuits in Minecraft, you’ll feel right at home following wires in these logic-based distractions, though they never get complex enough to be called obstacles. When you’re not jumping on platforms, you're jumping on buttons instead as you noodle your way through very simple circuitry-themed puzzles. Its platforming and controls aren't actively bad by any means, but they also don't do much to challenge or excite you either, ending up feeling passable but forgettable as a result.
You start out with a standard jump, but unlock multi-jumps, midair dashes, and even gliding along the way – all the familiar stuff you’d expect to find in a metroidvania platformer without any surprises. Most of the time you’ll be hopping around big empty levels in incredibly run-of-the-mill platforming that’s been done better in dozens of other games. The encounter itself is unfortunately pretty bland once you reach it, but Recompile at least manages to transform the time spent uncovering the secret history of its setting into the key to reaching its conclusion along the way, which isn’t something I’d ever seen done before.Īlthough the story is quite good and kept me intrigued the whole way through, the stuff you’re actually doing between those text logs isn’t quite so inspired. Even better, you’re actually rewarded for collecting as many of the text files as possible, as they’re required to complete the final boss encounter for reasons I won’t spoil here. ~//Work/compile/ps4/libps4/crt0.s:3:1: error: unknown directive ~//Work/compile/ps4/libps4/crt0.s:1:19: error: unexpected token in '.section' directive Iinclude -ffreestanding -nostdlib -nostdinc -fno-builtin -D_PS4_ -I~//Work/compile/ps4/libps4/include -target x86_64-scei-ps4-elf -DPayload=0x926400000 -o build/util.c.oĬlang ~//Work/compile/ps4/libps4/crt0.s build/config.c.o build/debug.c.o build/elfloader.c.o build/main.c.o build/protmem.c.o build/util.c.o -O3 -Wall -m64 -L. Iinclude -ffreestanding -nostdlib -nostdinc -fno-builtin -D_PS4_ -I~//Work/compile/ps4/libps4/include -target x86_64-scei-ps4-elf -DPayload=0x926400000 -o build/protmem.c.oĬlang -c source/util.c -std=c11 -O3 -Wall -pedantic -m64 -mcmodel=large -I. Iinclude -ffreestanding -nostdlib -nostdinc -fno-builtin -D_PS4_ -I~//Work/compile/ps4/libps4/include -target x86_64-scei-ps4-elf -DPayload=0x926400000 -o build/main.c.oĬlang -c source/protmem.c -std=c11 -O3 -Wall -pedantic -m64 -mcmodel=large -I.
Iinclude -ffreestanding -nostdlib -nostdinc -fno-builtin -D_PS4_ -I~//Work/compile/ps4/libps4/include -target x86_64-scei-ps4-elf -DPayload=0x926400000 -o build/elfloader.c.oĬlang -c source/main.c -std=c11 -O3 -Wall -pedantic -m64 -mcmodel=large -I. Iinclude -ffreestanding -nostdlib -nostdinc -fno-builtin -D_PS4_ -I~//Work/compile/ps4/libps4/include -target x86_64-scei-ps4-elf -DPayload=0x926400000 -o build/debug.c.oĬlang -c source/elfloader.c -std=c11 -O3 -Wall -pedantic -m64 -mcmodel=large -I. Iinclude -ffreestanding -nostdlib -nostdinc -fno-builtin -D_PS4_ -I~//Work/compile/ps4/libps4/include -target x86_64-scei-ps4-elf -DPayload=0x926400000 -o build/config.c.oĬlang -c source/debug.c -std=c11 -O3 -Wall -pedantic -m64 -mcmodel=large -I.
Clang -c source/config.c -std=c11 -O3 -Wall -pedantic -m64 -mcmodel=large -I.
0 kommentar(er)
