Category: Miscellaneous

For the stuff that doesn’t belong anywhere else.

The Mercy Rule: A proposal to fix unbalanced FPS matches.

It’s no secret that I play a lot of competitive first-person shooter games. While I vary in skill from an absolute noob to top of the leaderboards depending on the game and match I play, I do play a fair share of competitive games. Often times these become my podcast games, where I just mindlessly shoot things while hearing about video games, history, or forgotten TV shows. And yet, I seem to do okay most of the time with not that much focus.

However, there’s one particular quirk about these kind of games that bothers me. One that’s been set in stone since the early days of online deathmatching with Doom and Quake almost 30 years ago. Something that has become more of a problem in recent years: Unbalanced teams.

We’ve all likely had those kind of experiences, the ones where you realize the other team is just too good, and there’s no way in hell a victory is on the horizon. You get fragged frequently, oftentimes by people with reflexes so sharp that you’d swear they’re hopped up on amphetamines. You may get a lucky frag or two, get a “comeback” medal, but it’s not enough. The game ends with an outright blowout: 100-48.

Nothing more demoralizing than something like this, from a match of Call of Duty: Black Ops Cold War.

Sometimes when players see the writing on the wall, they’ll bounce out of the game mid-match, forfeiting an XP bonus for staying with the match, ending up with a game that ends up being 6 vs 3, making it more lopsided and unbalanced, even as new players join in to make it balanced again. Back in the day you’d see players swapped over to the other team to try to balance things, but not anymore. Once a team’s in a game, that team’s set in stone until the game ends.

For some, it’s discouraging. It feels like one’s skills are inadequate enough to play these games. It demoralizes the player, so they may not give their best. Thus when the odds are stacked against your team, and they know the other team’s filled with the kind of player that’s likely doing sick YouTube frag videos, it just stops being a fun experience.

Granted, some games like Call of Duty have made it so if you joined a losing game in progress that it doesn’t count as a loss against you, but it’s a patchwork solution to a bigger problem. Even recent elements like Skill-Based Matchmaking, which has become sort of a bane to some high-level players, can only do so much to help out games that are clearly favoring one team.

Even being on the winning side of a crushing battle, from Call of Duty: Modern Warfare (2019), doesn’t feel fun to me.

I’ve thought about this problem for a while. While I am not a game designer – I tried that in community college and it went over my head so much that one of our team members, a person with Actual Gamedev Skills and is likely in the industry nowadays, had to bail us out of our final class project – I am familiar with some of the tenets of game design that I think I can make an idea to resolve this. I’ve called it the “Mercy Rule.” It’s not a catchy title, but I think it works in theory.

How does the “Mercy Rule” work? Well, if there’s a large score discrepancy between two teams, the game ends early, regardless of time or frag limit. The winner is immediately decided, XP is rewarded, and everyone’s moved back to the lobby. A fairly simple rule that I think could make a slight difference in terms of multiplayer gaming. Letting games end early with this new Mercy Rule could make a difference when it comes to gameplay. It means matches don’t drag along to the finish line, games finish quicker, and there’s more incentive to stick around rather than ragequit, especially if there’s some extra incentive like bonus XP or something.

Rage and the Art of Reloading.

Alright folks, time for me to get a bit “technical,” as it were. This is one of these posts where I’m gonna talk briefly about a game mechanic and how it actually benefits the player subtly. I know most of my content is a bit more fluff, but hear me out on this one.

I recently beat id Software’s Rage, a solid first-person shooter/driving game hybrid. I was looking to play something after trying to beat Modern Combat 5, and this seemed like a prime candidate.

I seemed to go through a phase where I was playing a bunch of older id Software games to see their career trajectory, as earlier in the year I had ran through Doom 3 — the original, not through the somewhat inferior BFG Edition — just to see if it was bad as I remembered it. It actually wasn’t awful, and is a pretty good game. Hasn’t aged gracefully in the graphics department, but what has?

One of the more entertaining parts of the whole game. A shame it’s too short.

Which brought me onto playing Rage. As time has gone on, this game has been mostly forgotten by hardcore shooter fans, shoved off into the “oh right, that was a game” category that other id games like Quake 4, Enemy Territory: Quake Wars and that 2009 Wolfenstein game have been victim to.

It was also a changing of the guard, being one of the last major games John Carmack worked on at the company before he left for Oculus, and with most of the original people who made some of id’s classics gone, it just seemed like id was in a weird career limbo where they had no idea where to go next. Basically, they went from being the pioneers of video gaming to attempting to be in with the modern shooter crowd, and failing in the process.

But enough about id software’s midlife crisis. I wanna talk about something this game does that people take for granted. Rage has two minor mechanics that while aren’t explicitly mentioned, but really help out the player. It involves the simple concept of reloading your weapons.

In most first-person shooters, when you reload, you can’t cancel out of the reload until it finishes, leaving you vulnerable to attack. Secondly, the reload animation has to play out fully before you can fire again. In a fast-paced shooter, it can be frustrating to have to wait for your dude to slowly tap a magazine into their assault rifle and pull the charging handle before being able to shoot again.

Rage doesn’t do that. If you start reloading mid-magazine and hold down the fire button, the reload is immediately canceled, letting you expend the rest of the magazine. Secondly, if you’re reloading from an empty magazine, you can hold down the fire button before the player pulls the charging handle, letting you skip the rest of the reload and get back to shooting quickly.

You can see this in the video I shot from one of the bonus Sewer levels, but there’s a better demonstration if you skip ahead to 1:53.

It doesn’t sound like much, but it’s a huge help. Rage has you fighting between the quick and melee-heavy mutants, common grunts, and big boss monsters. The last thing you want is to have to watch a painstaking long reload sequence while having enemies take pot shots at you.

Doom modding in the ’90s: My recent fascination.

One day, I was checking out some YouTube videos, until I had stumbled upon this one by Pordontae:

I was gonna write something about that Doom level set featured in the video, but I realized there wasn’t anything particularly unique about it. Some of the levels feel bland and featureless, often with no sense of balance. E2M9 has a fight between one spider mastermind and three cyberdemons, for crying out loud! But it did give me an idea. that’s not the main reason why I liked this level set. It was the random sounds that the creator replaced.

Playing this level made me realize how amazing the Doom mod scene was during the mid-to-late ’90s. END1.WAD is the epitome of a 1994 level, according to the Doom Wiki. During the heyday of Doom modding, everybody was making their own levels to play around in Doom, in varying levels of quality. Some have held up and get universal praise from Doom veterans. Others are forgotten, an experiment often made by a teenager who didn’t pursue game development further.

Modifying an existing game wasn’t a new concept, but Doom was one of the few to openly embrace it in its early days. This lead to many creative levels, some made by people who’d later become famous in their own right.

Though this wasn’t always the case. Since the tools were fairly new, most people were making fairly dreadful levels, usually plagiarizing parts of the original Doom levels, or in some cases created tutorial levels. Such as FEAR21.WAD, which looks so obtusely designed that it’s like if Salvador Dali made Doom levels. Here’s a UV-Max (All kills, all secrets) run from Doom speedrunner ryback:

 

This above is an example of what most people had to offer. For 1994 standards, it was great to have another level to play, but it’s very tough to play today unless you’re like me and have a liking for crap, for sure.

Experiencing PC gaming with Intel Integrated Graphics.

Back in December 2013, I decided to trade in my hunk of junk six year old HP Pavilion PC for a new custom built PC. Running on an Intel i5-4570, 8GB of RAM and a 1TB HDD with Windows 7, I was in PC gaming heaven at the time. I couldn’t quite afford a new video card, so my 3 year old Radeon HD5770 was put into the PC as a stopgap until I could afford a new video card. It worked out great, pushing most of the PC games I had to high settings.

But then, tragedy struck. I saw graphical artifacts while playing Crysis, but thought nothing of it at the time. Several days later, my video card started spinning its fans loudly while I was idling on my PC, temperatures rising by the second. Even with a quick dusting, the card still got loud and didn’t show a picture. It happened to me again: a video card died on me. I got the HD5770 as an emergency replacement for my dead GeForce 8800GT back in 2010, and now I had another dead video card. I was amazed the Radeon lasted that long, maybe pushing all those polygons in those two months was a bit hard on the old gal.

Intel inside. I remember when that was considered amazing. Man, I’m old.

For the past month I’ve been playing other games, mostly on console. Stuff like binging the 2010 Need for Speed: Hot Pursuit reboot and Call of Duty: Black Ops II. Annoyed that I couldn’t play much on the PC, I decided to test something.

All CPUs these days come with a integrated graphics chip inside them. The most hardcore of PC gamers won’t go this route, opting to buy a video card to do all the heavy lifting for their gaming needs. I thought I’d give my i5 processor’s integrated graphics chip a shot in the meantime. After installing the newest drivers for it, I tried a bunch of games on the HD4600, Intel’s integrated graphics chip and screenshotted the results.

Boy, I was surprised at what worked and how it ran. Pretty much every game I threw at it worked mostly fine with little problems, albeit with considerably lower graphical fidelity. For several of the games, I had to kick the resolution down to 1280×720 and lowering the graphics settings as far as they could, but most of them ran perfectly fine. Here are a few examples I decided to try:

Grand Theft Auto IV

Niko looks surprised at how ugly Liberty City looks.

One of the few times “This looks like a PS2 game” is right in this case.

I never thought this could run GTA IV. The game was notorious at the time for its ridiculous hardware requirements, though we’ve made significant advances in technology since its PC release five years ago. It ran pretty well even with the HD5770, so I was totally not expecting this to work with the Intel graphics. Yet, I could run this, with everything on low, at about 15-20 frames per second. There’s a lot of model and texture pop-in, so it’s not the most ideal way to experience Liberty City, but it’s playable.

Surprisingly from what little I played, I enjoyed it. Then again, I was never into the goofy antics that plagued the earlier GTA games like San Andreas, so maybe this game is perfect for me.

Saints Row IV

Look at that view of fake Steelport. Zinyak has quite the eye for detail.

Jumping off a building, to the tune of Stan Bush’s The Touch. Only in Saints Row.

I remember slogging through Saints Row: The Third on that junky old PC. Everything on low quality at 640×480, with framerates well into the teens. Some very dark times.

When I upgraded to the new PC, being able to run that as well as Saints Row IV here on high settings with a solid framerate was a godsend. Even with the integrated graphics shown here, I can still run and jump through cyber Steelport with little problems. Drastically better than what I suffered on the old PC.

I need to get back to this game sometime, this game is pure dumb fun.

NOT FOR RESALE: The mystery of this weird message.

A few days ago, I had snagged this wonderful gem:

I sometimes wonder how used games get all dinged up like this.

Streets of Rage 2, a Sega Genesis classic, for $5. Initially I passed on this, but then I realized it’s Streets of Rage 2, a freakin’ Genesis classic. That Yuzo Koshiro soundtrack! Who could pass that up? The dummy writing this. Thankfully, I was able to correct my mistake and grab it as a wonderful addition to my Genesis collection, along with a Sonic cartridge compilation called Sonic Classics.

Granted, it’s just a cartridge copy and it isn’t in the best of shape, but it’s nice to have. There’s something special about this cartridge: The giant “NOT FOR RESALE” label on it. Anyone who’s into collecting Sega Genesis stuff may have also seen the big “NOT FOR RESALE” stickers on copies of Sonic the Hedgehog. My Sonic the Hedgehog 2 came with my Sega Genesis long ago also with a “Not for Resale” sticker on it. Many pack-in games on the Genesis also came with the “not for resale” sticker on them. It made me wonder: Why is this ugly text on there, and what was its purpose?

At first, I thought this meant so that these couldn’t be resold at second-hand shops, but that wouldn’t make any sense, even when this was new. After doing a bit of research and asking a friend, it turns out it’s a much more sinister story.