It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I've tried and failed to find solid criticism on Silverman's Build engine and Build engine games. Most of this is no doubt likely due to the fact that these games are old and a healthy amount of stuff from that time has gone unarchived. The other part is likely due to the fact that people just aren't having the discussions and for all sorts of reasons.

I don't come from a very technical background and I'm not a programmer, however I've played some of the build engine games in their heyday and now in DOSBox through the GoG releases. In their heyday I played the hell out of Duke Nukem 3D and Shadow Warrior. More recently I've been playing Blood, a game I always wanted to play but simply couldn't find in the late 1990s.

The issues that I've come across recently are also issues that I encountered when I first played these games in the 1990s, revolving around (1) enemy fire/AI and (2) aiming with the mouse. When I was younger I thought I sucked terribly at these games despite how much I played and enjoyed them because of these issues and, true enough, I certainly wasn't the FPS player that I am now. When I look back at how I played then compared to how I play now I'm almost embarrassed at how bad a player I was. Back then I didn't pay enough attention to learn how to meet the game on its own terms, now is a different story.

(1) Enemy Fire/AI

In the Build engine games I've played I've noticed that enemies have the uncanny ability to fire at the player as soon as they enter a room provided they are looking at that area, it's as though there's an invisible string tied to their ranged weapons that pulls the trigger as soon as a player crosses the threshold. This is incredibly frustrating when coupled with the use of hit-scan based weapons, something that is very common in these games and has the tendency to result in immediate, unmitigated damage to the player.

I'd like to say that the player knowing the level well enough will mitigate or nullify the damage through their ability move quickly and deftly, but this is not the case. Some enemies, such as the pig cops in Duke Nukem 3D, a healthy amount of the ninjas in Shadow Warrior, and all of the cultists in Blood fire without any delay upon recognising the player.

I like to reflect this back against the Doom engine games where, even in the Steam releases -GoG, twist some arms over at Zeni-Max so we can all enjoy some id Software games without dealing with Valve!- things played out differently. Enemies like the former humans (pistol, shotgun, chaingun) and the spider demons (boss and regular) in the Doom games had a noticeable 'triggering phase' where they began to acquire the player on sight instead of the knee-jerk firing that is present with hit-scan attacking enemies in the Build engine games. The earlier Doom and subsequent Quake engines did not suffer from this issue.

Ultimately, the player is forced into an uncomfortable position that is made worse by (2) and the rarity of life essence.

(2) Aiming with the mouse

The Build engine features an auto-aim feature, seemingly so that players more familiar with Doom engine games are still able to attack targets in the same manner. In Doom a monster could be on a level that appears above the player but so long as the player is aiming at the monster they will still hit it. The auto-aim feature works the same here and I wouldn't suggest turning it off due to the sluggishness of mouse movement. (I'm certain someone can go into the .cfg files to alter these parameters but I'm not so inclined or able to do that. Truth be told, one shouldn't have to do that.) This is a sluggishness that, again, when reflected against the earlier Doom engine games, is something that I did not encounter.

While auto-aim is helpful its inherent weaknesses are that it cannot distinguish between closely grouped enemies and it seeks to aim at the centre of the enemy. The first part presents as a real issue in a game like Blood where the flaregun puts a DoT attack on the target and choosing to attack multiple enemies with as little movement is possible turns into an exercise in stretching 'as little movement as possible' into 'I'll just circle-strafe the bastard'. The second part presents an especially difficult issue when it comes to walls, chairs and doors. Ducking was something that was new with Build engine games and enemies loved to hit the floor and this played havoc with the auto-aim feature. Walls, of course, were an obstacle in and of themselves because it was impossible for the player to shoot the upper-arm or elbow of the enemy that wasn't completely concealed by the wall.

Conclusion

I've really enjoyed both Duke Nukem 3D and Shadow Warrior and, for what it's worth, I'm having fun with Blood. But these games share an awkward space next to the FPS games that came just before with the Doom engine and the games that came at the same time and after with the Quake engine. There was undeniable innovation with the Build engine but there were also surprising mechanical issues that made me feel like I had less control of my play than those other games.
Post edited November 10, 2013 by TheBitterness
Very intelligent post. In Blood, I don't think it is so bad because in Blood, many of your enemies, have to get close to you to hurt you and the cultists don't do so much damage. But it has been a long time, since I last played Blood...
Post edited November 10, 2013 by
I was a bit afraid to click on the post, as threads with names like these are from time to time mainly meant to stir up trouble, but I'm glad to see that my worries were unfounded. And yes, I wholeheartedly agree with you about those issues. In particular point 1 was a problem with these games, as so many enemies also use hitscan weapons. Had enemies instead used projectiles like the imps from Doom, then the enemy shooting behavior would not have been such a big deal, as then damage would still have been avoidable, but with hitscan weapons it is not really down to the player's skill to avoid damage during the initial encounter.
And this part is actually a large part of the reason why I found DOOM to be the better game. You could always avoid damage (except for those rare few moments where you had to jump down into something dangerous without a hazmat suit).

I remember there being some criticism against the Build engine games back in the days, but it did not focus on the problems that you listed, but rather gaming magazines and people in general complained about the build engine being outdated once Quake was released, and that mainly being due to the graphics not looking as good.
Wasn't Build programmed by a teenager when he was still in high-school? Or am I thinking of some other 3D engine
avatar
Crosmando: Wasn't Build programmed by a teenager when he was still in high-school? Or am I thinking of some other 3D engine
Ken Silverman was 18 when he started his work on it (he started working on it in 93, the first game using it was released in 96). Quite a talented young man, I have to say. The build engine was a big upgrade from previous 3D engines, so it is quite impressive that someone fresh out of high-school was able to make something that complex.
Don't be too hard on Duke3D controls. Early FPS used to be played primarily with just a keyboard (or joystick!). I don't think it was until the big multi-player arena fps came out, and keyboarders got slaughtered by mouse-lookers that that started to die out.

The original DOS Quake was configured to play just like DOOM. The mouse defaulted to moving you a few steps forward or turning you a few degrees to the left/ right. You actually had to hold down a button to enable mouse look. It was that foreign a concept in '96.
avatar
Crosmando: Wasn't Build programmed by a teenager when he was still in high-school? Or am I thinking of some other 3D engine
avatar
AFnord: Ken Silverman was 18 when he started his work on it (he started working on it in 93, the first game using it was released in 96). Quite a talented young man, I have to say. The build engine was a big upgrade from previous 3D engines, so it is quite impressive that someone fresh out of high-school was able to make something that complex.
I agree. The guy is obviously, a genius.
avatar
TheBitterness: snip
As for the AI:
While I agree that the enemies' aiming is too precise in all the Build Engine games (particularly the hitscan weapons, especially in Shadow Warrior) I cannot complain about a lack of a delay. Frankly I always felt that there is enough of a delay (and IIRC particularly the pig cops seem to always enter a firing stance for a short moment before shooting, even if a line of fire has been present for a longer time period). And I am pretty sure that enemies in all these games sometimes start moving upon spotting the player, before firing the first shot even if a line of fire exists.

Also: I wouldn't blame this aspect of AI behaviour on the engine. I doubt that the engine itself provides any limitations of this kind and that it would have been simple to change the AI behaviour accordingly.

As for the aiming:
I partially agree, the Build Engine is basically a 2.5D engine after all and the vertical aiming is simulated with a few tricks so frankly free aiming is almost destined to be somewhat flawed there but IMO the games aren't doing worse than Doom at all. The massive aim assistance seems a little out of place with mouse aiming being active but it's just something you have to get used to, I don't feel that it's really a flaw. Considering the engine's limitations I think they solved it the right way.

As for the sluggish mouse aiming: there is an issue that seems to keep the games from registering mouse input from both axes at once, there exists a fix for that, though, which IMO fully solves the problem.
Post edited November 12, 2013 by F4LL0UT
Shooting Delay: This doesn't seem to have anything to do with the Engine and is just a game design issue.

Aiming: This comes from a feature that Build added that it never should have: Look Up/Down. Both this and doom were design for keyboard use and had fixed POV textures. Doom has the auto aim because you could not shoot up/down any other way. Later remakes added mouse look, but because the game design never required this it works OK.

Duke3D however had a keyboard look up/down from the start, which really sucked. It made the textures break, it was hard to use, and mean level designers could assume you can look up/down, which means you *have* to.
- The cheapness of the AI can be offset with good level design including architecture and supplying adequate health to the player. If the difficulty level you're playing on doesn't give you enough health, ratchet down the difficulty level. That's what it's there for. You can't blame the game for your unwillingness to do this.

- The AI reacting immediately has to do in part with the portal VSD algorithm that the Build games use. I haven't looked at the code to confirm this, but just knowing a good amount about that technique, I would make an educated guess that as soon as the player's view crosses the threshold of a new portal/sector with unactivated enemies in it, they become activated and fire ASAP.

- I never found any difficulty with the auto-aiming aspect. Eduke32 allows you to turn it off under Options->Player.

While later FPS games such as Quake required and enabled greater precision, I never felt like I couldn't control the character in any Build games. On the contrary. I felt like an electrocuted cat running across velcro. Probably the reason you couldn't find much criticism for the games is that 1. They're awesome, to this day 2. Games to compare them to only came out, for the most-part, after and 3. Your personal preference flies in the face of what most people think of them. IE - You fight the game more than play it based on your criticisms. Most other people don't seem to have these issues with it, myself included.
avatar
F4LL0UT: Also: I wouldn't blame this aspect of AI behaviour on the engine. I doubt that the engine itself provides any limitations of this kind and that it would have been simple to change the AI behaviour accordingly.
Actually, Duke at least provided that completely through scripting via the .con files. Shadow Warrior/Blood/et al all implemented it in actual code rather than expose it to the end-user, sadly.
Post edited November 12, 2013 by Firebrand9
One plus about Duke Nukem 3D (and some of the other BUILD-based games) is that the included Level Editor happened to be one of the easiest to use out there for a FPS. I know because that was the first Level Editor I have ever used for any FPS (first used it around 8/9 years old, though I didn't use some of the features till a bit later). Probably the trickiest features to use are Sector Effectors, but even without them still makes it a relatively easy editor compared to the other level editors for FPS games.

Heck, I remember the older Doom level editors (like DeU, ADE II (based on DeU), and WinDeu) being not as user friendly. One of the issues was you had no way of viewing the level ahead of time. 3D mode wasn't even introduced till much later (introduced with Doom Builder 1/2). Also, you had to download a level editor for several games, though some games like Duke Nukem 3D, Shadow Warrior, Half-Life (which includes a level editor that was originally designed for Quake 1/2), Unreal Tournament (not sure about the original Unreal) provided such an editor.

While BUILD might have been behind the Quake engine, it does have a charm that makes it nice. :D
avatar
Firebrand9: [see direct quotations below]
Seriously, I either need to figure out the BB Code or GoG needs forums that allow for easier quotes. Just, damn, man. XD
----

"The cheapness of the AI can be offset with good level design including architecture and supplying adequate health to the player. If the difficulty level you're playing on doesn't give you enough health, ratchet down the difficulty level. That's what it's there for. You can't blame the game for your unwillingness to do this."

It's not a matter of the difficulty setting relative to enemy/player health and enemy damage, this is purely related to how these games function at their core. It's problematic at best when the player must take extra shots at the enemy because of the auto-aim feature or mouse sluggishness, this is something that only knowing the level really well and being unduly over-prepared for can help remedy. It's a more serious issue when point blank shots or direct shots with nothing interfering with hitting the enemy do not register all of the damage that they should. I've encountered this a number of times from Duke Nukem 3D to Shadow Warrior to Blood, however I find it to be the most problematic in Blood.

Should the player ratchet down the difficulty to overcome a legitimate mechanical issue? No, they certainly shouldn't and the criticism is something the player should appropriately level. With that being said, should the player ratchet down the difficulty for an enjoyable play session? Yes, they should. Left 4 Dead 2 is a great example of this, where core mechanical errors make playing on Expert less than satisfying even though the player has the skill to play it. Examples that come to mind are homing Tank rocks, hit-box issues (even when playing Offline, Single Player), terrible Survivor AI and other issues.

The game should not have to be ratcheted down in difficulty to be enjoyed but if they want to enjoy the game they need to be willing to work with the problems the game gives them. I play these games at the medium difficulty setting because of the game's issues not my ability and this allows me to enjoy these games despite the criticism I level.

"While later FPS games such as Quake required and enabled greater precision, I never felt like I couldn't control the character in any Build games. On the contrary. I felt like an electrocuted cat running across velcro. Probably the reason you couldn't find much criticism for the games is that 1. They're awesome, to this day 2. Games to compare them to only came out, for the most-part, after and 3. Your personal preference flies in the face of what most people think of them. IE - You fight the game more than play it based on your criticisms. Most other people don't seem to have these issues with it, myself included."

Three points.

First, don't do what seem to be personal attacks such as the lines I emphasised with italics. That seems like a personal attack, however if that wasn't your intention I'd ask you to be a bit more careful with your wording in the future. Use terms like 'seems like' to indicate that you may be reading something wrong or into a given argument, allowing your argument to retain strength in case you are wrong and also allowing you to not fall into (or incite) mud-slinging.

Second, these games are indeed awesome. Like I said, I played the absolute hell out of Duke Nukem 3D and Shadow Warrior in high school. It seems to me that the reasons for not finding the criticism that I've levelled, even at the time, is in part because folks were more interested in lambasting the content without attempting to understand the content. 'You can kill strippers in that game, it promotes violence against women!!!' While you can do that, yes, it's not encouraged by 3D Realms and the game punishes you for doing so. How? It spawns extra enemies. Lesson of the day: shooting strippers will cause alien hordes to come pwn your ass. The other part is likely that they were caught up in the new technology of other games like Quake.

Third, I'm glad some people don't seem to have an issue with controlling their character in the Build Engine games. Perhaps this is because they've gone through the .cfg files and tweaked them or perhaps it's how the software runs relative to their own software/hardware configurations. Whatever the case, what I've noted is likely not just a personal issue but instead a real issue that some players were able to easily navigate on their own through a combination of tweaking the game, their play, or both. The Build Engine games are not games that the player can just blast through, rather they exemplify the Latin phrase which translates to 'hasten slowly'...because if you don't you're going to get your head blown off very quickly. The problem is that a player can do just that and still encounter mechanical issues that force them to play the game's mechanics more than playing the game, which is what you aptly describe as "fighting the game".

I hoped it was clear from my OP that these issues take away from but do not deplete my enjoyment of the Build Engine games. These games do possess real problems and they are certainly worth playing because, as you've said, the games are awesome. I don't think we should forget either of those points.
Post edited November 13, 2013 by TheBitterness
Mouse aiming in the Build Engine game is weird, you can use bMouse to make it better, which helps a lot, but it still doesn't come close to what a proper source port can do.
http://swisscm.duke4.net
There is the eDuke32 port for Duke 3D, but sadly there is no port for Blood and the two ports for Shadow Warrior have their own share of problems.
avatar
TheBitterness: First, don't do what seem to be personal attacks such as the lines I emphasised with italics. That seems like a personal attack, however if that wasn't your intention I'd ask you to be a bit more careful with your wording in the future. Use terms like 'seems like' to indicate that you may be reading something wrong or into a given argument, allowing your argument to retain strength in case you are wrong and also allowing you to not fall into (or incite) mud-slinging.
I'd ask for a more fair and reasonable criticism taking into account a vast number of factors but I somehow doubt that'll happen. There's no way it can not be personal as it's your interpretation vs the rest of the world at large. You can choose to take it as a personal attack if you want, but I'm simply pointing out the final flaw in your argument which is how you choose to perceive these aspects of the game. Terminology such as 'seems like' are not intended as weasel-words, simply observation based on evidence you're providing. At this point you've provided means for a self-fulfilling prophecy, but I digress.

I refute your points on almost all merits as do the majority of fans of these games. The games have the features you mention but terming them as problems rather than just the way the engine/games were implemented or idle complaining is unfair to the games, their creators, and the engine programmer (Ken). Furthermore, you compare against games that have had the past 15+ years between then and now to cater to the players. I can go on and say Doom (or any other game) has problems because (fill in the blanks) but at some point it just becomes ridiculous, because where does it end? It's the way the game is; take it or leave it.

You say you need to ratchet down the difficulty and obviously feel a sense of resentment at needing to do that which is what I originally suspected. The game doesn't come down to your level in any way other than the difficulty you select; you must come up to its. This is just how it works. I've beaten these games on max difficulty and they were worthy challenges. I wouldn't even call myself a great player, but I made the best use of the capabilities the game gave me, manned up, and brought them to my feet. This is the way of things. Do you expect everything to be perfect as you define it? I don't consider that to be reasonable, rational, or realistic.

All games give you a set of tools in terms of game features and character control. If you don't like the way they feel or operate the first course of action isn't to blame the game or the engine. Look in the mirror. A player may just need to adjust their preferences to the game. Sometimes games are genuinely flawed (ET), but in the case of Build Engine games the evidence points to the contrary. If you get in a car and don't like how it drives, don't buy or drive the car. This isn't rocket science.
Post edited November 13, 2013 by Firebrand9