Jedi Knight Bits

Jedi Knight came out just a year after the original Quake, and was already showing its age upon release. Its development team was wise enough to include support for hardware acceleration and mouse-look controls (complete with a neat if archaic calibration of the axes that allowed for some very sensitive camera movement), but the low- poly count was much harder to mask.

Guarded by a force field -- with a rather obvious power source -- this area leads into a twisting maze of vents that all have a different idea of where the gravity source is located. Confusing, but fun.

Jedi Knight still received very positive reviews, though, and rightfully so. It wasn’t perfect, and hasn’t aged particularly well, but I had a blast with it.

Here are some of the points that stuck out upon replaying it:

— The level design in Jedi Knight is fantastic, and probably its biggest strength. Of course level design was a bit of a different beast back then: areas tended to be much larger with fewer scripted events, the player had an inventory of keys and other usable items that facilitated environmental traversal, platforming puzzles were quite common (although usually disliked), movement was much, much quicker, etc.

Within that framework, though, the levels were a treat.

Despite the game’s low-poly count, its geometry was quite complex and varied. Textures were often repeated, but new ones trickled in periodically and every map had its own unique motif. The player was also constantly operating large-scale machinery that dynamically changed the landscape.

It all made for a nice combination of action, exploration and some occasional head-scratching. The only complaint I had with the levels were the large, industrial looking doors that were virtually indistinguishable from walls. Since these had to be opened with a button press, there were too many instances where the player could easily get stuck simply due to dodgy visuals.

It's actually not as dangerous as it looks, and you can bet there's a secret room underneath...

— In-between level cinematics consisted of live-action actors superimposed over CG backdrops. They were rather silly and pretty low-budget, but did a decent job of conveying the story while showcasing certain visuals that were not possible to render within the game engine.

— The player was able to carry 10 weapons at any one time, and many of them shared the same ammo source. The limited ammo made becoming a Jedi and obtaining a lightsaber all the more rewarding. Visually speaking the lightsaber wasn’t anything fantastic, but it had unlimited power and the added advantage of lighting up dark areas and deflecting smaller enemy shots.

— Jedi powers were earned as the player progressed through the game, and they could be focused on neutral abilities, the light path, or the dark side. The powers themselves were a nice addition to both the singleplayer and the multiplayer, and were sometimes necessary to progress through a level (or at least take a short cut).

Force Pull was a particularly fun one as it allowed you to snatch weapons out of the enemies’ hands or grab healing items from far away.

It's possible to blow up those barrels from this location, but due to wonky ray-tracing so common in older FPS games, my shots hit the wall.

— All the enemies responded to basic in-world physics, even after death, which made for some cool effects like a dead body sliding along the current of a pipeline.

— A lot of the audio was taken straight from the Star Wars movies, including the iconic sound effects and the famous scores by John Williams. These greatly enhanced the atmosphere and helped Jedi Knight stand out from other FPS titles of the era.

A TIE/sa Bomber hounding the player mid-way through the game.

— The way the game’s secret rooms were placed was quite clever as they followed a pattern that went against the common funneling/guiding techniques of level design, e.g., a small nook embedded into the wall just above the entrance to a room was very easy to miss if the player ran right in without looking up and behind.

Enemies were often utilized to help the player spot these locations as they would often be placed in seemingly inaccessible locations, but with enough sleuthing, the player could always discover a way to reach his foes. A tally at the end of each level also informed the player as to whether he missed any secrets.

The impetus to discover the secret areas was very good as well. Not only did these locations often contain health, armour and ammo, but finding all the secrets in a level rewarded the player with extra force powers.

Jedi Knight is available for cheap on Steam, although everyone should keep in mind that it’s a very lazy port/re-release. None of the GUI elements have been updated for higher resolutions, the title screen and in-game cinematics must be viewed in a windowed mode, and the game doesn’t come with its original music. There’s a fix for that, but make sure to check out the forums first to get a better idea if it’s worth your money.

, , , , , , , ,

  1. #1 by Jammenee on June 3, 2010 - 12:48 pm

    I loved the level design in Dark Forces and it’s sequel Jedi Knight. It required thorough exploration and experimentation and wasn’t quite as linear as people made it out to be at the time. Then again people complaining about linearity in FPSs back then were usually thinking of the levels not being suitable for multiplayer which was stupid to begin with.

(will not be published)