Category Archives: Rambling

Cloudbursting

I know it’s been ages since I’ve posted. I’ve been in a bit of a limbo when it comes to gaming for a while now, with several games I’ve been working through at a glacial pace that I really want to finish before moving on to anything new, all of which will be covered here once I complete them. For now though, let me tell you about a new toy of mine.

A few months back I got the itch to start looking at handheld PCs. I have a friend with a Legion Go and at least a couple with Steam Decks. In reality, I probably have very little actual use for one, and I have a history of regrettable purchases related to handheld consoles and the like. I simply don’t play them. Still, it was a fun hole to fall into: consuming innumerable videos, Reddit threads, and Steam Community posts on the subject, and spinning off into unexpected areas, like the vast array of cheap yet impressive emulation focused handhelds that have flooded the market in recent years. In the end, despite the numerous advantages of the Windows based handhelds, given the price, my 20 years of investment in Steam as a platform, store, and community, and various other (mostly minor) quality of life things, I was fairly settled on the Steam Deck OLED.

That said, the one thing that kept coming up was the other platform, store, and community I’ve invested heavily in over the years – Xbox. While I consider myself a PC gamer first and foremost, I also do a ton of console gaming as a means to get away from my PC for a while, relaxing on my couch in front of a nice, big TV. I mostly reserve console gaming for single player games, with more traditional PC genres like FPSes and strategy games, and lets not forget MMOs and other online games, being played on PC. That said, when it comes to my (massive) backlog, I intend to play a great deal of those games on Xbox. I already own many of them, for one, but I also somehow still hold the tiniest flickering flame of the once great torch I carried for building up my Xbox achievement score. One obvious solution was streaming from my Xbox to my Steam Deck over my local network. Could it be done? Well, absolutely! There are third party apps that can do it quite well, apparently.

Playing Halo Infinite on My Stoop
“Playing Halo Infinite on My Stoop”

The more I thought about it, the more this became one of the most likely ways I’d use my Steam Deck and, frankly, it seemed a little overbuilt (and overpriced) for that purpose alone. I’d also read about how Xbox games wouldn’t use the full screen due to the Stream Deck’s odd 1280×800 resolution which got me thinking that the ideal would be a handheld with a 1080p screen so that The Xbox Series X (or PS5, for that matter) could stream to it full screen in their most commonly used resolution.

That’s when I ran into the Logitech G Cloud. Now, I’ve heard of this thing before. I’m sure it was mentioned on at least one of the gaming podcasts I regularly listen to because of their supposed partnership with Microsoft for the G Cloud to be something of an Xbox competitor to Sony’s first party solution to this problem, the PlayStation Portal. I’m not sure that’s quite how it ended up, but the more I learned about it, the more interested I became. Here’s a quick rundown:

  • Built and supported by Logitech, who are far more experienced with hardware and much more reputable than the majority of players in the space, outside of the major ones like Asus, Lenovo, and Valve, of course. Accordingly, it feels relatively high quality when it comes to build and materials.
  • The controls are quite good. The layout closely resembles the standard Xbox controller. The analog sticks are decent, the buttons and triggers feel good, it has a subtle but fully functional rumble, etc. Input lag is close to non-existent too. About the only complaints I’ve heard is that the D-pad leaves a bit to be desired, not being great at registering diagonals, and some people hate the deadzones in the analog sticks.
  • Additionally, the whole thing is very ergonomic. Most every reviewer mentioned how good it feels to hold. It’s also really light, which is an advantage none of the big boys have. You could definitely hold this thing above your head while laying in bed without giving yourself an unplanned arm workout, and that is one of the use cases I had in mind.
  • Another point of comparison that is often brought up is battery life, and the battery life of the G Cloud, being basically a glorified Android tablet, and one that is mostly streaming rather than running games locally, is stellar.
  • Being an Android device, it has a lot of flexibility in terms of available apps, customization, etc. Of course, Logitech provides a custom interface which simplifies and consolifies the whole thing somewhat too. One of the most likely use cases for a device like this, outside of streaming, is loading it up with emulators, and there’s quite a few available for Android. This thing might not be the most powerful handheld by any means, but it’s enough to emulate most consoles up to PS2 quite well.
  • As mentioned, while it’s not OLED, the screen is quite nice. 1080p native, relatively large at 7”, vibrant. It can also get bright enough to allow you to play outside on a sunny day.
  • The biggest negative is perhaps the price, which is typically $300. Given the price of handhelds, and Sony’s Portal being only $200, I think that’s a little high given its capabilities and intended use. That said, it regularly goes on sale for $250 or less, and finding them used is fairly easy as well.

I’d suggest TechDweeb’s video on the G Cloud for a better summary. The fact that a dude who probably literally owns every handheld available is so enthusiastic about this thing speaks volumes.

So, I got one! Being an iPhone and iPad user for ages now, it was a bit of a mindfuck setting up a new Android device, but beyond that, it was easy to get going. I tested out Microsoft’s Xbox streaming app, which worked fine, though it only runs at 720p. I also tested out Microsoft’s Cloud Gaming app, which worked far better than I’d have expected, despite also having a similar 720p limitation. Now, I honestly don’t have that much interest in cloud streaming, but given how well it works, I could see myself using it if I were on a relaxing vacation where I had a lot of downtime, assuming I had a good WiFi connection and an even better Internet connection, of course.

Finally, I bought myself XBXPlay from the Google Play store which is a third party take on the normal Xbox streaming app, but supports 1080p and has a lot more options for tweaking your experience. It works incredibly well. While it’s a bit of a bummer I had to go to a third party for a superior solution, I have no complaints. I can now play Xbox Series X (and all of the previous Xbox One, Xbox 360, and Xbox games it supports) while my SO is tying our main TV, in my bed when I just need to relax, or outside on my porch on a nice day. With the Xbox’s remote startup and shutdown, I could also open some ports in my firewall and stream remotely too, if I wanted to. Very cool.

Now, I haven’t dabbled with PC streaming at all yet, but in theory I should be able to get similar performance by using Steam Link or perhaps better yet, Moonlight + Sunshine. The truth is that I don’t have the same use-cases for PC streaming. Generally, if I want to play a PC game I just go on my PC, which is rarely tied up. I don’t play a lot of PC games using a controller; if I’m super compelled to use one, I’m probably just going to play the console version of the game. I’m sure one of these days I’ll have some reason to diving into it. I’d imagine getting an MMORPG to work on this thing could be fun, for instance.

Metal Gear Ac!d, anyone?
“Metal Gear Ac!d, anyone?”

To expand a tiny bit on the subject of it being an Android device, as mentioned, it’s powerful enough for a lot of emulation, but it’s not up to the task of anything super intensive, like more demanding PS2, GameCube, or Vita games and beyond. It’s also not going to be able to smoothly play later, more demanding Android native games. Now, given this thing’s widescreen format combined with its apparently lacking d-pad, I can’t see myself emulating a lot of 8-bit and 16-bit classics on it either, even though it’s otherwise totally up to the task.

There’s a sweet spot that I found incredibly intriguing though – the Sony PlayStation Portable. The PSP had a 16:9 widescreen display and it had an analog stick (the infamous “nub”) as its main input, so it seems like a perfect match for the G Cloud. The G Cloud is also powerful enough to emulate it using the awesome Android PSP emulator, PPSSPP, being able to 4x upscale most games to its 1080p native resolution. I went from not being aware of or all that interested in many PSP games, to spending days on end cramming a 64 GB SD card with almost its entire library of games, and let me tell you, the PSP had a ton of interesting ports and genuine exclusives, especially to someone who has very little experience with the PlayStation ecosystem like me. Now, I honestly don’t know when I’ll actually get around to playing any PSP games, but this does at least mean I’ll be adding Metal Gear Acid and Acid 2, along with MGS: Portable Ops to my upcoming Metal Gear retrospective playthrough.

In conclusion, success! My original Xbox local streaming use-case seems to have been thoroughly satisfied, and the bonus use-case of opening up a whole new world of games with a high quality PSP emulation experience is also a total win. That said, I should mention that there are indeed other competitors in this space (Android handhelds with similar form factors) such as the Ayn Odin and Odin 2, the Anbernic RG556, and the Retroid Pocket RP4. Some of them are much cheaper, and some of them even more expensive, but more powerful. While I’m happy with my G Cloud for now, this is a space I’m going to keep an eye on for the future… you know, unless I just end up buying a Steam Deck. 😉

Sierra On-line Books

I read and listen to a lot of books related to computer and video games, and having just finished one such book, I figured I’d make a post devoted strictly to books about the history of one of the most fondly remembered classic game companies, Sierra On-line. Fondly enough for me to talk about three different books, at least!

I’ve posted several reviews of vintage computer games over the years, and often gone into my personal history of some of these games. Sierra On-line is one particularly big component of that, as during their heyday they were without question one of my favorite developers (and when you throw in another of my all time favorites, Dynamix, one of my favorite publishers too!) Sure, LucasArts is widely agreed upon to be the victor when it comes to the fanboy favorite argument of which of the two companies made the best adventure games, but in the 90s Sierra held much more territory in the diskette and CD-ROM boxes of my personal game collection; the Space Quest series in particular being an all time favorite.

Three Books about Sierra On-line

Hackers: Heroes of the Computer Revolution by Steven Leary is surely one of my favorite non-fiction books; when I eventually stumbled upon it I honestly couldn’t believe I hadn’t read it much, much earlier in life. It covers a lot more than gaming, but of relevance here is the last third or so of the book which focuses on the shift of personal computer software development, while still somewhat rooted in enthusiast hacker culture, to a more commercial direction in the early 1980s. In particular, it mostly focuses on Ken Williams and Sierra On-line. Keeping in mind that this book was first published in 1984, this was a very contemporary look at what was then a fairly young version of Sierra, having only just released the original King’s Quest.

Of course the story of the founding of On-line Systems and the development of Mystery House is covered, but then Hackers moves into chapters devoted to Sierra’s close bonds with their peers, such as Brøderbund and Sirius Software, its “summer camp” like culture, and its gradual shift away from that and “hacker” ethics in general, along with all kinds of now legendary stories including the deal with IBM to develop for the PCjr, Richard Garriott joining Sierra, the noncompete lawsuit against Atari, and a whole lot more. The style of these later chapters is a bit different than those earlier in the book, feeling more like embedded journalism pieces than chapters in a book about computer history. Crucially, Hackers really provides a different take on who Ken Williams was and how he ran Sierra at the time than what I was familiar with. This is extremely fascinating stuff and absolutely essential for providing some eye opening accounts of those typically skimmed-over early years of the company.

I’m sure there had to be some, but I don’t know of anything else significant outside of blurbs posted in Sierra’s own manuals, guides, and magazine until 2018, when The Sierra Adventure was published. I was stoked. At long last someone put together a book about the history of the venerable Sierra On-line! The author, Shawn Mills, is a writer for Adventure Gamers and one of the founders of Infamous Quests, a throwback adventure game developer best known for Quest for Infamy and a couple of notable Sierra remakes. Respectable bonafides!

The Sierra Adventure isn’t quite the exhaustive chronicle of the history of the Sierra On-line and every last one of its products that many might be looking for in such a book. Instead, it attempts to approach the subject almost entirely from interviews with former employees. Quite a lot of notable people contributed the quotes that make up the bulk of the book’s content, though Ken and Roberta Williams themselves, still keeping a distance from all things Sierra at this point, are rarely quoted. Even still, there is enough here and I think the author put it together with enough love to make it a worthwhile read. I have to say, I was a bit annoyed with how the book starts, devoting its first chapter to flashing just a bit forward to talk about Sierra’s first couple brushes with death and how the company survived them before going back and starting at the beginning with On-line Systems and Mystery House in the next one. This kind of literary device often works quite well, but here it just came across like some kind of a bizarre editing snafu. A relatively minor gripe, I admit.

In 2020, founder and former CEO, Ken Williams himself, wrote and published Not All Fairy Tales Have Happy Endings. Part autobiography, part industry insider insight, Not All Fairy Tales Have Happy Endings is the story of Sierra On-line from the unique perspectives of Ken, and to a lesser extent, Roberta. While I did sometimes find the writing in need of a bit more editing (for example, Ken often repeats himself, especially from chapter to chapter) I quickly started to get in tune with Ken’s “voice” and ended up really enjoying his take. By the way, I originally listened to the audiobook version, and when I later got a printed book I was surprised to find it full of interesting full color pictures. Very much an upgrade!

Without a ton of detail, the book sometimes feels like just a bunch of strung together anecdotes, though it was all strung together reasonably well despite its numerous interludes. It certainly succeeded in satisfying my biggest hope for the book by filling in a lot of gaps about Ken and Roberta and the unique company culture that produced the games I loved so much. I was perhaps most intrigued by the conflict between Ken’s cold and detached approach to business: only wanting to work with “A players” and chasing monetary success, at times to the detriment of the company, with his more personable and generous side: hiring random locals to grow into very specialized positions and running the company like a big, fun family, and how that stuff all changed as he eventually ceded more of Sierra’s management and control to others as the company grew. I don’t know that Ken sees this as a “conflict” himself but, especially given Sierra’s eventual decline, it stood out to me. Speaking of which, this book gave me far more insight into the death of Sierra than anything else I’d read, with Ken providing a version of events that no one else has ever, or could ever, fully present around the CUC takeover and subsequent loss of control. It really is, as the title suggests, a bit of a cautionary tale.

Of course, Not All Fairy Tales Have Happy Endings is all from Ken’s point of view but, despite the obvious inherent bias there, his accounts do come across as sincere to me. Regardless, I’d highly recommend reading the sometimes overlapping accounts in all three of these books for a more well-rounded perspective. I’d also recommend reading them in the order I covered here; Ken even references his chapters of Hackers in Not All Fairy Tales. When taken together, we finally have as close to a complete picture of the company as we’re likely to ever have.

There you have it! Needless to say, these are far from in-depth reviews and I’d recommend Evan Dickens’s reviews and comparison between The Sierra Adventure and Not All Fairy Tales over at Adventure Gamers if you want to dive a little deeper than I did here.

This article was actually taken from my other blog, originally posted in March of 2023. Given the subject matter, I meant for this to be more of a cross-post but, hey, I guess I got a little distracted. *shrug*

Planetside (Part 2)

Continued from part one

Auraxis, as it looked before The Bending.
“Auraxis, as it looked before The Bending.”

When talking about how to get to the action in the last article I made passing mention of connections between warp gates and “spheres of influence” so let’s expand on that and go over the all-important map. In addition to those empire sanctuary islands, Auraxis was made up of ten continents of similar size and various biomes. Those continents were connected to each other via the same type of warp gates that connected some of them to sanctuary islands. Each continent was a massive, expansive land of a size and scale that is pretty much unheard of for an FPS game. While it might blow other sandbox FPS games out of the water in size, the world is pretty empty, with the only real points of interest outside of the occasional bridge or bunker being the facilities and the small guard towers near them, which are ultimately what we’re fighting over.

Ceryshen's continental map. Mostly controlled by the TR at the moment.
“Ceryshen’s continental map. Mostly controlled by the TR at the moment.”

Like the connections between continents, each facility was connected to at least one other facility on the continent, forming a “lattice” structure. The “lattice links” between these facilities were important in defining the battlefronts – your empire could only attack an enemy owned facility it had a link to, either by facilities you’ve captured, or by a warpgate connected back to your empire’s sanctuary or another continent you control. Thanks to these defined battlefronts, battles were mostly concentrated around these areas, helping keep the player population from being spread too thin. The continental lattice also provided benefits from facilities of certain types under your control. For example, if you were at a friendly facility that was connected to a tech plant your empire owned, you could spawn more advanced vehicle types from its vehicle terminals. This added a little bit more strategic consequence into decisions about which facility your empire should attack, and in what order, whether it be to gain those benefits or simply take them away from your enemies.

As for the sphere of influence, this was simply an area around a facility or a tower that was “controlled” by the empire that owned that facility or tower. This area could not be directly dropped on (as mentioned) and enemy Combat Engineers couldn’t fill them with their own deployable equipment. The area also more generally functioned roughly as a mini “zone” in the traditional MMORPG sense, so things like how experience points for battles over the control of these facilities and the scope of the “broadcast” chat channel were based on these areas. In between these areas was, as mentioned, not a whole lot, but all of this other space was ripe to be turned into massive combined-arms battlegrounds as forces moved between facilities and towers, and the terrain was just varied and interesting enough to lead to some cool battle scenarios. I have vivid memories of battles around Searhus’s massive volcano crater’s rim, and the epic fights around the many long chokepoint bridges spanning bodies of water all across Auraxis are legendary, for example.

A nice, quiet VS tower, just waiting to be taken.
“A nice, quiet VS tower, just waiting to be taken.”

Outside of traveling between them, there were other reasons battles might take place in-between facilities that were directly linked to how taking over facilities worked. Let’s start from the beginning though. Each facility had a relatively small structure called a “tower” just outside of its sphere of influence. There were a few varieties of towers, with some having gun turrets, others having landing pads, but they were all close to identical on the inside. Dominated by a wide staircase wrapping from the basement, which contained spawn tubes and equipment terminals and was protected by a “pain field” to keep would-be enemy spawn campers at bay, up to the roof, with a control console near the top. There was not much to these towers, but they were key in how facility captures worked, as they allowed an attacking force to quickly gain a nearby foothold from which they could respawn and attack the main facility. Unlike facilities, control of the towers would instantly change once the control console was hacked, plus, not being tied to the lattice system, they could be hacked by anyone, at any time. Intense battles in and around towers weren’t uncommon, but they were also some of the more common places for great smaller fights to occur.

Tower fights could be bloody affairs. Get that loot!
“Tower fights could be bloody affairs. Get that loot!”

So, you hacked the door to a tower, made it up (or down, if you decided to land or drop on the roof from an aircraft) to the control console. You hacked it, and control of the tower went to your empire. If there were enemies around, they’d notice this pretty quickly and might immediately begin mounting a response to attempt to take it back from you. In the meantime, you and your allies could you set your sights on the facility itself. While there were other options for tactically deploying around a facility you were attacking, most notably a vehicle called the Advanced Mobile Station (AMS) which could be parked and “deployed” to cloak itself and act as a mobile spawn tube and equipment terminal, ownership of a facility’s tower was definitely a much more solid foothold.

Hacking a VS controlled facility's control console.
“Hacking a VS controlled facility’s control console.”

Taking a facility worked similarly. There were several different facility designs and layouts, but they were all surrounded by high, castle-like walls with turrets which would act as sentry turrets if unmanned, with only a few entrances on foot – either the large arched gates on either side of the courtyard that allowed vehicles in and out, or via the locked backdoor of the facility. This is where a Galaxy dropship is especially handy, allowing a full squad of troops to effectively bypass the outer defenses of a facility, dropping right into the courtyard or onto the upper levels of the main structure itself. Regardless, assuming you were able to make it into and through the courtyard, you’d make your way into the main facility and eventually find its control console room, usually fairly deep within the complex. Unlike the rather exposed control console of a tower, the control console of a facility was in a small, dedicated room that was much more defensible. Assuming you were then able to get in there and hack the control console, you’d then have to wait for a 15 minute timer to tick down before control of the facility finally changed. During that time, of course, you could expect a defense to mount if there wasn’t already one – enemies would drop in via HART from their sanctuary, arrive by various methods from nearby facilities, and enemies killed in their attempts would respawn there. 15 minutes can feel like a damn long time.

Arson
“Arson setting a bunch of Boomers (remote mines) to destroy a generator.”

One strategy that was often employed to help ease the burden of attacking a facility was purposely draining the facility of power. Every interactable device in the facility – equipment and vehicle terminals, spawn tubes, turrets, etc. ran on power provided by the facility’s generator, which was in turn fed by a supply of Nanite Technology Units (NTUs.) This power was drained much more quickly by the facility’s auto-repair systems, which would slowly repair any of these devices when damaged or destroyed. Once a facility was completely drained of NTUs, it would lose power and turn neutral, meaning no defenders could respawn there and it could be hacked freely once power was restored. Another version of this tactic involved blowing up the generator itself which would immediately cause the facility to lose power until it could be repaired, but this would also alert everyone that it was under attack as well as requiring it to be repaired before the facility could be back up and online. Still, it could be very effective to strategically take a facility’s generator down to deprive your enemies of the lattice linked benefits they’d get from it. Regardless, these strategies could allow small, coordinated groups to run special ops style “back-hacks” to assault facilities away from the frontline and take them over without much resistance.

An ANT refilling the NTU silo at a neutral facility
“An ANT refilling the NTU silo at a neutral facility”

One really cool element of the whole facility power system was that if a facility did run out of NTUs, it could be refueled. There was a special vehicle called an Advanced Nanite Transport (ANT) which could be driven out to a warp gate and deployed to fuel its tank, then driven back to a facility and deployed near its NTU silo to refuel it. Making NTU runs after a facility had been drained wasn’t usually too exciting, but making an emergency run during a huge battle could be edge of your seat intense. There were various ways to lessen the chances of your ANT run ending in a glorious, extra-large explosion, such as driving with an escort or even a whole convoy for protection, or using a Galaxy or Lodestar to haul one around in the air, but regardless, a well coordinated assault OR defense often involved accounting for the availability of NTU refuels.

Similarly, there was also a system added early into the game in which some facilities had a special device called a Lattice Logic Unit (LLU) which needed to be physically carried to another facility after a successful hack to complete the change of control rather than waiting out the timer. There were all kinds of conditions and limitations to who could carry the LLU and how – what vehicles they could ride in, etc. The LLU was, of course, a bit of a MacGuffin. It’s real purpose was to generate more battles outside of facilities similarly to those that could take place around ANT runs. While I don’t know how successful this ultimately was, I do recall being involved in some particularly intense battles that revolved around trying to protect or assault an LLU carrier.

A squad of NC Lightning tanks engaging.
“A squad of NC Lightning tanks engaging.”

As a quick aside, both of those systems seemed to be there to introduce more opportunity for fights to happen outside of facilities and, of course, using numerous vehicles. While it was common to use vehicles of all sorts to travel between facilities, which is when the most epic vehicle battles took place, and using certain vehicles like Galaxy dropships for infantry drops, AMSes to setup spawn points, and ANTs for refuel runs were very specific but common use-cases, running vehicles that required multiple crew members, like main battle tanks and the fearsome Liberator bomber, along with running multiple vehicles together, tended to be something more of a distraction to my outfit. Something we did for fun, but not something that often felt like it was contributing meaningfully to most battles. Likewise, running the lighter Mosquito and Reaver aircraft seemed like it was used for more quick transport and scouting behind the lines, and solo hunting of enemies. While all of these vehicles could be effective in combat in the right circumstances, due to the way facilities were structured and facility capturing worked, their effectiveness as “force multipliers” was limited.

So, as mentioned above, once you controlled a facility, the lattice link to other connected facilities opened up, expanding the front and allowing you to move on to more facilities. This went on (often involving struggles between all three sides) until eventually one empire controlled the entire continent. This temporarily locked all of the facilities on the continent from being captured, so efforts would usually move to one of the next connected continents. So on, and so forth. Honestly, this larger strategic part of the game was one of the weaker areas of Planetside in my opinion. There wasn’t any real purpose to taking over a continent, or indeed all of Auraxis. Unlike similar MMORPG territory-control based PVP systems, you’re not establishing your own strongholds where you can build housing or shops, or new areas to craft, hunt, or run dungeons, and there’s zero permanence to any of it. Planetside, it seemed, gambled on the fun of the actual fights being enough to inspire players rather than any end goal or rewards. This couldn’t have helped Planetside’s subscription base – it really only took a month or two of playing the game to have seen everything and have it totally figured out, and unlike most MMORPGs, there simply wasn’t enough variety of other diversions to keep players who were bored or just needed a break from cancelling.

A massive TR force gathers at a warp gate.
“A massive TR force gathers at a warp gate.”

I didn’t really mention the concept of “zerging” at all, and I should, because it comes up a lot in discussions around Planetside. The “zerg” was an obviously Starcraft-inspired term used to describe the largest masses of players, and “zerging” was the act of joining one of these groups and following them from enemy facility to enemy facility, overwhelming enemy resistance with sheer numbers. Most of the time these huge forces would inevitably meet, meaning that on every contested continent, there was usually at least one incredibly huge, lag inducing, ridiculously chaotic battle. Following the zerg was a way to guarantee access to Planetside’s largest fights, and more importantly, the experience points that came with them, but to many of us this was less exciting than smaller fights, special ops missions, coordinated vehicle runs, and numerous other experiences the sandbox nature of the game could provide. Getting online and following the zerg every night was the entire game to some people, and unsurprisingly, many of them quickly grew to consider Planetside as rather repetitive and dull.

A group of NC Lodestars hauling Vanguard main battle tanks behind enemy lines.
“A group of NC Lodestars hauling Vanguard main battle tanks behind enemy lines.”

That about wraps up my lengthy overview of Planetside’s gameplay. As mentioned, I played the game pretty steadily for its first year or so. In that year, development felt a little slow, especially given the monthly fee we were paying SOE for the privilege, but in reflection it wasn’t too bad. The Liberator bomber was added, along with a dedicated anti-air vehicle called the Skyguard. The aforementioned LLU system was added. They expanded hacking. They added platoons, which could be used to combine 3 squads into one larger unit. They also added the Lodestar, which I’ve mentioned a couple of times now. I do have to wonder just how many of those additions were holdovers that didn’t quite make release, but regardless, content is content. Actually, looking back, one of the issues I think Planetside’s development team had with adding new content to the game is that it was essentially already fairly well designed and balanced upon release. Anything all that interesting that they added to the game was sure to irreversibly alter that balance. Speaking of…

Core Combat's caverns looked like nothing else in the game.
“Core Combat’s caverns looked like nothing else in the game.”

The game’s first and only paid expansion, Core Combat, also came out at around this time. Core Combat added several huge underground cavern maps to Auraxis. These could be accessed via warp gate-like areas called “Geowarps” that were limited in their availability. The main appeal of these caverns was a shift to more CQB-inspired infantry combat, as the caverns featured a lot of cramped areas, a lot of verticality, and relied on teleporters and ziplines for traversal since vehicle usage was limited. While most of my outfit mates were excited about the concept, I don’t think I was alone in being fairly underwhelmed by the cavern-based combat experience. There was at least a reason to go down to the caverns, and that was the new facility module system. You could obtain and charge-up a “module” in a cavern which could then be brought back to the surface and installed at a facility, giving it a particular new benefit, which also extended to any other connected facilities your empire controlled. These benefits were things like adding an energy shield to the otherwise open gate entrances in the walls of your facilities, granting players faster movement speed and reducing spawn times to a facility, and allowing them to pull some of the new “ancient technology” vehicles added with expansion, such as the extremely useful Router (a deployable teleportation system) and the Flail (long distance artillery) from the facility’s vehicle terminals. I totally appreciate a lot of the ideas they were trying to implement with Core Combat, and cavern runs could be a fun diversion for smaller squads, but it ultimately felt like too much of a distraction from the core systems of the game, and a bit of misstep.

A TR BFR stomping across the battlefield.
“A TR BFR stomping across the battlefield.”

Still, even more was added later into the game’s life. Beyond things like bug fixes and numerous UI enhancements, they added new vehicles, such as the Fury ATV and new empire specific versions of The Deliverer troop transport. They added a merit/accommodation system and other improved ways to view and track your stats. There was “The Bending” patch that replaced one of the continents (Oshur) with several new smaller “Battle Islands” which each had its own special rules and restrictions, which was kind of neat for variety’s sake, but they also made each continent its own planet, changing the global map to a interstellar map in a rather stupid move. Then, in perhaps the most controversial thing to ever happen in the game, they added huge mech-like vehicles called BattleFrame Robotics (BFRs) which absolutely shook the game to its core. I had mixed feelings about BFRs myself. I mean, the panic instilled by being on foot when a towering BFR stomped onto the battlefield, leaving a path of destruction in its wake, was a totally new addition to the dynamic of the game, and was only topped by having a friendly BFR show up shortly thereafter and watching them go toe-to-toe in an epic scrap. Regardless of how much SOE “nerfed” and otherwise altered BFRs after first introducing them, a vocal part of the community completely hated their addition for reasons ranging from reasonable concerns about the balance and indeed the entire overland combat meta being altered, to simply hating the idea of “unrealistic” mechs being added to their sci-fi vidja game. Boy…

There was more after that, of course, as the game stayed online in one form or another until 2016, but the last time I stepped foot onto the virtual battlefields of Auraxis was around the time the BFRs were finally close to resembling being balanced. I’ve said it before, but Planetside was a special game to me – one where I got really into gaming with a community, and where I made friends I still have today. It was a unique game too, that, like so many online-only games, is sadly now gone to us outside of some unofficial preservation efforts. It’s also survived by Planetside 2, of course, and while Planetside 2 was influenced heavily by the first game and does a good job of respecting what it established, they’re also very different games. It may end up being quite an effort, but I’m hoping to compare and contrast those two games, as well as talk more about Planetside 2 in general, in a future article here. Stay tuned!

Pictures taken from my old NC outfit, The Praetorian Guard’s, archived website, JeffBeefjaw’s Imgur album, which looks quite similar, but from the TR perspective, and some newer pictures acquired while playing around on the PSForever server. Unfortunately the two former sources don’t really show any ACTUAL combat, as few people captured full time back in the day so most screenshots were of points of interest, outfit photo ops, and just dicking around rather than normal gameplay. I also had to grab the original world map, the Core Combat cavern, and the BFR pictures from wherever I could find them.