Here’s one of those games I wish I knew existed back when it was new. Just take a look at it! Star Wars Droidworks, Developed and published by Lucas learning in 1998 for Macintosh and Windows PCs. Yeah that’s right, Lucas Arts had a spin-off edutainment arm for a while. Headed up by former edutainment veteran, Susan Schilling, who’d just left MECC after the SoftKey buyout. Lucas Learning’s first title was DroidWorks here But it was quickly followed up by the likes of Star Wars: Pit Droids, Star Wars Math, and Star Wars: JarJar’s Journey. Now, alright, they weren’t all destined to be classics, but DroidWorks managed to stand out. I mean, just look at this fantastic packaging with all its indulgently embossed holofoil cardboard goodness. The front, the back, the sides, the end pieces, and the fold-out cover are all ridiculously shiny and reflective, to the point of distraction. It actually kinda makes it hard to read the advertising copy. But whatever, man, this is Star Wars. So you can probably guess 90% of its contents right off the bat. Speaking of contents, inside the box the first thing you get is an ominous red paper telling you how annoying it is to get the game running on an iMac. Yeah, I almost forgot, DroidWorks was one of the applications designed to launch alongside Apple’s iMac. They were pushing edutainment pretty hard! Steve Jobs: “Some math and some history software. Again, edutainment and educational coming back to the Mac.” You also get the game itself and a colourful CD-ROM. Alongside a dual case manual that’s also printed in full colour. And I approve. It’s quality stuff all around when it comes to the packaging and the box contents. And I wish I could say the same about the game itself. But yeah, time to quit stalling and jump right in! DroidWorks launches with a typical Lucas Arts launcher of the time, followed by some logos. And the obligatory, but always welcome, Star Wars opening crawl. [Star Wars theme] C-3PO: “This young Rebel makes an excellent Jawa, don’t you agree, R2?” [R2-D2 beeps] C-3PO: “R2 is right. Now that your disguise is in place, we should begin immediately.” So apparently Imposter-3PO and Low-Res R2 have captured some height challenged Rebel and dressed them up as a Jawa. And this is the character you play as. Not that it matters since you’ll never see them again. But yeah, the whole point is that you’re a Jawa in disguise off to thwart the Empire’s plans by the way of droid construction. Jawa: “Greetings, I am Wimateeka! So more (?) kind leader of this Sandcrawler. I hear you’re an excellent droid builder!” Yeeaahhh, Jawas speak English now. Err, sorry, Galactic Basic. Personally, I find it a bit off-putting. But I guess it’s more player friendly than reading a bunch of weird noises with subtitles. After this unsettling Jawa realisation sets in, you’re dropped right into the droid workshop to prepare for your first training mission of which there are eight to complete before embarking on your main objective. There are two types of droid to construct: walking and rolling. And between them, there are unique parts and capabilities like speech, welding, sensors, lighting, jumping, lifting, grabbing, and even medical abilities. As you play the game, you’ll unlock more parts. And in the end, there are 87 parts to choose from. You can only pick one of each type, and there are strict limitations as to the combinations and where they can be placed on the droid. But at least you can customise them even further with names and paint jobs to prevent things feeling samey. And I’ve gotta say, building Star Wars droids is a childhood dream come true, man! I always wanted to do this as a youngling. So even without playing the rest of the game just being able to mock up retro sci-f abominations is awesome in of itself. I mean like, nobody needed to see what it would look like if beloved Star Wars characters had a terrifying and regretful lovechild, but here you can! And it is fantastic. Once you’ve determined your droid’s appearance and approved of their dancing abilities, it’s off to the map screen and the mission briefing. Jawa: “Your droid needs to through the door at the top of the cliff.” Here you’re given an idea of what kind of hurdles to expect. But the only real way to tell precisely what kind of droid capabilities that you will need is by giving it a shot yourself. You can either start the mission straight away, or jump into the testing chamber of your Sandcrawler and try things out sans galactic consequences. This is also a good place to familiarise yourself with the controls and interacting with the environment which, err, well it isn’t great. However, before we get to the suck, lets talk about the acceptable. Once you’ve left the construction mode, DroidWorks takes place in a low poly, three dimensional environment. One that might look familiar if you’ve played other games in the Sith engine, like Star Wars Jedi Knight: Dark Forces II, and Mysteries of the Sith. From here, you’re tasked with figuring out how to accomplish your objective, and seeing as this is an edutainment game, the idea is that you’re supposed to learn scientific principles along the way. Most of this happens by way of the game’s information and data expert, or InDeX. Mmm, that late 90s weird capitalisation. This is a slightly interactive encyclopedia of sciencey things, and while some if it is fictional inner universe stuff, it’s all explained in a manner that also relates to real world physical properties and scientific laws. So each mission will rely on exploring the way these principles work by way of the in-game physics engine and environment interactions. An admirable goal, indeed! But there’s a problem. Unless you use very specific computer hardware that’s slow enough, the physics engine and environmental interactions are completely and utterly broken. I’m not just saying that either. Games are buggy sometimes; that’s just how it goes. Programming’s hard, you know. The thing is, when you’re entire product, one that’s built specifically as an educational experience, that relies on aspects of the game that are clearly screwed up, it simply fails at its main objective of being an effective learning tool. So like running into some physics glitches in Battlefield is one thing, but running into physics glitches in a game that’s all about teaching you physical interactions is something else entirely, y’know? I don’t know if it’s a result of retrofitting the Sith engine, or they ran out of time, or what, but DroidWorks suffers form a variety of constant infuriating physics problems on every retro PC setup I’ve tried. It reminds me a bit of the problems of Lego Island in terms of how picky it is with CPU speed. The simulation screws up if it’s allowed to run at a frame rate higher than of about 15. Just one example, driving up a slight incline with treads is a total crapshoot (???) Occasionally it’ll work, but most of the time it won’t. A legged droid could jump over it, but many of the missions force you to use treads so you’re stuck. Until you figure out that pressing certain buttons on the UI will temporarily reset the physics system, which then forces your droid over the hill. I mean, that’s fine until there’s another one and then you do it again, and again, and again, and yeah, this is really not a feature. This is a bug. I have never seen a game where you have to exploit the help companion to drive up a ramp. Help Companion: [repeated] “These are information tapes. They provide you with important information relating to your droid.” Err speaking of that companion, that is one bizarre choice for her accent. I’m not entirely sure what they were going for there. It’s like Daisy Duke mixed with Elly May Clampett. Help Companion: “One launch battery now in your inventory!” Not a complaint, more of an observation. But y’know, those– those two, y’know, err– Gold Five: “Stay on target…” See, now I can’t get the idea of those two being my companion at the same time– Gold Five: “Stay on target…” [clears throat] Right, as I was saying, even if you can deal with the wonky physics, the aggravation continues with several puzzles that rely on pushing objects, and there’s just no graceful way to do this. You bump into things until they sorta move in the direction you want them to, and hope that you don’t clip through them or accidentally move them up against a wall because then you have to restart the whole scenario. But good luck with moving things around, seeing as the camera itself is abysmal. A terrible trait to have in a game that relies heavily on environmental navigation. The camera is always fixed on your droid, and there’s no way to look around without physically moving yourself. And to top it off, this happens to be the most sensitive and jarring set of controls in the game. Then there are of course the areas that despise you for no reason. And you’ll get stuck without any method of resetting your position. You’ve got no choice but to quit, and try to avoid that next time. And sure, in a way that’s the point of DroidWorks. It’s a game all about problem solving and you accomplish this by doing your research out in the field, and then going back and designing a more fitting droid. But when so many of these problems are unpredictable glitchy garbage, it quickly becomes far more of a chore than any kind of valuable teaching opportunity. Still, it’s not as if it’s a total loss. It’s not. The rest of the gameplay is pretty darn fun. And it seems plenty of folks thought so too back in 1998, seeing as it won a crapload of awards. It’s got a lovely Star Wars atmosphere going on, with familiar locations and sound effects, and even some character interactions to participate in. Droid 1: “Well, hello there. What are you doing here?” Droid 2: “I was sent to fix the corrosion on the water pipes. I was just about to get started and, well, wouldn’t you know it, wham!” When it’s at it’s best, DroidWorks is a charming, enjoyable little game. And maybe when I was a kid, I would’ve forgiven its numerous physics short-comings cos, dang it, it’s Star Wars, and it’s creative, and it’s technically educational so I could play it with less of a chance of parental reprimanding. But as an adult, I can’t really say it’s worth much of your time. There comes a point in the game where you’ve figured out what elusive specifications are perfect for each picky mission. Yet even then, it straddles a fine line between being trivially easy to complete and being an unforgiving monster of physics, glitches, bottomless death pits, and purposely deceptive navigation. Then once you’ve finished everything up, you get a cut scene and a certificate. Hooray(!) Who cares. That DroidWorks. In theory, it’s absolutely awesome wish-fulfilment with some dandy educational goodies and sandboxy stuff thrown in for good measure. In retrospect, it’s not something I think I’ll ever play ever again. And if you enjoyed this episode of LGR Edutainment Month, and perhaps you’d like to see some of my others. There’s new videos every Monday and Friday, so subscribe if you would like to. And as always, thank you very much for watching LGR!

100 thoughts on “Star Wars DroidWorks: Robot Abomination Simulator”

  1. Wow. There's a blast from the past. I used to love Droidworks back when my best friend from middle school had it. Here's hoping someone creates an open source clone of it so that future generations can also enjoy this forgotten gem. Though hopefully without a lot of the game-breaking bugs.

  2. I never had that many issues when playing this game back in the day. Got it from the public library. There was occasional terrian issues but nowhere near that often.

  3. They should remake this because creating your own star wars droid sounds like one the best ideas for'a game.

  4. Glitchy garbage it was not (to the right person). I'm rather blown away by the bugs you're experiencing- it ran excellent on the iMac G3 I had as a little one, but that was the ONLY experience I have of playing this game. I never bothered to emulate it.
    Most of the games I used to enjoy aren't really playable from the disks I have because the disk drive on that iMac liked to draw rings on the CDs and ruin them (RIP Duke Nukem 3D and X-WING Collector's CD-ROM). Knowing that, I don't really want to risk doing it some more.

    I finished every level except for the one level that was very dark- because there was a pit you had to jump over to reach the exit and I never knew that some legged droids could jump. (I literally found out that this was possible as I watched this video.)

  5. OH MY GOD ITA DROIDWORKS!!! I REMEMBER SEEING THIS AT A HUGE PUBLIC LIBRARY IN THE BIG CITY AND WE RENTED IT WHEN I WAS LIKE 5 OMGG dude id make like weird R2D2s n shit o
    Woah

  6. 2:02 Hey, I think that's Tom Kane! Looks like he was narrating the opening crawl even before The Clone Wars!

  7. Ah I had such a good time playing this as a kid. I remember restarting missions because I got the boxes in a hole and I actually remember having to learn about levers and pulley systems from the game. Huh, never struck me as a learning game as I played it. I could never finish the games though because the assassin droids scared me! Only ever finished the intro missions. Anyway, I'm sure you would have loved it if you played it as a kid back in the early 2000's

  8. Here's to hoping you cover more of the classic Star Wars games. I don't think you've done any of the Jedi Knight ones yet.

  9. Hmm, can't say I had any troubles with glitches when I played this game. Or I simply didn't notice at the time. It definitely had its wonkiness though.

  10. The Sith engine! Some great games there. Recognized some Jedi Knight assets in this one, haha. That was the engine that got me into level design. Good times.

  11. Old video true, but two cents anyways… I actually replayed the game entirely one or two years ago myself, for the physics issues, I had tried to play several times every time forgetting that I could never get over that first ramp on mission one, (Didn't know about the hint exploit), but what I did end up using was a CPU dampener (Essentially ran a program designed to use "X"% of the CPU at all times leaving less for a game like Droid works.) Instantly fixed the physics bugs and the game ran perfect, best experience of nostalgia of reliving my days playing it back on an XP machine.

  12. God, I loved this game as a kid. I don't think I ever finished anything past the second mission, but I spent a ridiculous amount of time just building droids and running around the training facility.

  13. Had this game as a kid and loved it. Ran it on my iMac and never ran into a single bug, so I'm pretty sure the technical difficulties you ran into were the fault of the computer and not the program.

  14. Wow, i can't believe i found this/this video.
    I've practially been searching for this for years once i remembered i played this as kid, AGES ago

  15. I loved this game when I was little. It ran fine for me me, so I think your issues were due to running it on more advanced systems than intended. I was on an old, Apple computer running virtual PC at the time

  16. Lucas Arts games were so good, Disney killed everything after buying the rights and giving the whole video game franchise to EA to make just ONE game (one that is just a cookie cutter shooter) instead of several amazing concepts that go into all the genres (like old lucas arts did).

  17. I always looked at this game in my local Babbage's but never got it since I knew our PC was too slow to run it. Probably why I was drawn to console games.

  18. I had this game as a kid, and I don't recall it having any notable physics bugs. I think it's the way-too-common problem where old games just don't run properly on systems that are even slightly different.

  19. I used to love this game and still have the CD’s but not the box. Shame to hear that trying to get it to run smoothly now is an issue as it would have been fun to play with my kids.

  20. Huh. Weird. This game seems like it would have been a fantastic opportunity to teach kids about robot programming. But instead they went for clunky physics instead. I think it would have worked a lot better as a programming teaching tool.

  21. Ha I loved this game, although I didn't experience many glitches at the time…I definitely remember the trouble with getting up some ramps though.

  22. I used to love this game.
    Never tried it on newer hardware… but never had an issue back when I played it.

  23. you can get around the cpu speed limitation by abusing the screenshot button. The best way, however, is to go in to the power options of your computer and limit the max cpu speed to that of a 1998 computer.

  24. Droid Works and Gungan Frontier were my two star wars PC guilty pleasures, and I'd absolutely love to see both of these updated. Hell, throw in Tie Fighter and X-Wing to the "Remake for modern systems" bundle and you've probably saved the spirit of human goodness.

    Thanks for the review and the nostalgia.

  25. I was fortunate enough to play this when it was new and I was in the target age range. So rose-tinted glasses and whatnot.

  26. Hahaha, oh lord, the nostalgia brought back by watching you struggle to get up those inclines is too much. I adored this game as a child.

  27. I had Gungan Frontier in 99 (I was 6!) and it came with a demo of Droidworks. It had one mission, the one that teaches you the mechanics of gears, and a fraction of the parts available for droid building. But goddamn, I played the hell out of it. Probably played it hundreds of times more than Gungan Frontier.

  28. i loved this game as a kid! didn't have the physics issues either (although I definitely got stuck a lot). always liked how the farmers in droidworks were the pedestrians in dark forces 2

  29. Bought it when it first came out, and played it once. I was going to mine the GOB files for textures to include in DF2JK for level design, but the legal mumbo jumbo at the end of the manual kept me from doing so. Oh well.

  30. Attention iMac Owners!
    Star Wars® Droid Works™ is A Memory Intensive Game, and requires at least 17.721K free memory available to run.

    If you're experiencing memory problems, the easiest way to get more memory is to turn on Virtual Memory.
    To Turn on virtual memory, click the Apple icon in the upper left corner, choose control panels, then choose memory. Click on the "On" button next to the virtual memory selection and restart your computer.

    The README file on the DroidWorks CD-ROM has step by step instructions on how to configure memory, as well as other suggestions for optimizing your system. Please check the README file for more help or
    visit our online technical support section at www.droidworks.com

  31. From my understanding, this is a hardware issue. The game was never intended to be played on machines with CPUs clocked at over 100 MHz, and the physics break down at high clock speeds on modern machines (and apparently emulation doesn't solve the issue). I don't recall having any of these issues when I played the game as a kid. But you're saying you played on various retro setups, so that leaves me scratching my head. Either way, failing to note that makes the review seem a bit unfair, I think, because this sounds like a compatibility problem, not an intrinsic aspect of the game as it was originally made.

  32. I remember playing this very enjoyable game. When we got a newer computer the physics didn't work right, it was impossible to go up all but the shallowest of slopes.

  33. Weird, I just had a basic ass walmart bought windows 98 machine with no special features or cards and the game worked fine

  34. I LOVED playing this game as a kid. I got my copy through a scholastic book sale along side with star wars pit droids. I can't remember how many hours I spent playing this game in all it's glitchy glory.

  35. I'd love starwars to make a new droid factory game even if it is meant to be educational like this one. With todays gaming technology it should be successful enough to warrent expansions containing new levels, parts, and physics obstacles.

  36. Did you by any chance try this game on an iMac G3 or similar Mac computer? I played this game a ton as a kid, gone back to it in recent years and I know the Mac version is nowhere near as glitchy as this review is making this game out to be.

  37. I remember having a demo for this game included in another Lucasarts game I played as a kid. I played the hell out of that demo, but my parents never got me the game. Still a bit sad about it.

Leave a Reply

Your email address will not be published. Required fields are marked *