Get quick and convenient access to just the hints you need for Quake 4, without staying on our website. Just download a free trial
version of our UHS Reader software and
a copy of these hints. You will get the
same gradual hints you see here -- unlike ordinary cheats or a
walkthrough that can spoil your game.
You can also buy the full version of the UHS Reader
for Windows or macOS. For just $14.95, you get full access to hints for
hundreds of games and 1 year of free updates. You can also search, decode, or print an entire
game's worth of hints at once.
Ask the Author
If you have questions about a puzzle that aren't answered
anywhere in these hints,
you may contact the author.
Quake 4 Hints
How am I supposed to defeat two harvesters at once?
1 of 9: It sounds super-hard, but it isn't really.
2 of 9: Remember the fact from the beginning of this level that you can destroy a harvester by taking out two of its legs.
3 of 9: That's easy to do and survive when there's only one harvester firing missiles at you, but here there are two, making things a little more dangerous.
4 of 9: One thing you could do is drive up near them and then quickly back down the narrow path you came up until two large metal structures are blocking your view of the harvesters.
5 of 9: Shoot down any missiles that make it past those structures, then wait for the first harvester to try to follow you down the path.
6 of 9: If he doesn't get totally stuck, he'll at least be greatly slowed down, so take advantage of the opportunity to shoot his legs out from under him.
7 of 9: Then repeat with the second harvester. Easy!
8 of 9: If the harvesters don't ever try to follow you down the path, then alternate hiding behind the large metal structures and strafing left to blast the harvesters' legs with the cannon. It's hard to hit the legs' vulnerable spots from such a distance, but it is possible if you keep trying.
9 of 9: Or you can skip all that and just drive around the harvesters and through the building's door, since it's always unlocked. A handy programming oversight, perhaps?