I have a bit of a confession to make: despite my years of playing Madden, and my frequent blog rants about the quality of the game and my desired feature sets, I'm actually not particularly good at the game. I never really have been. I don't really have the "stick skills". I've been playing the game exclusively on All-Pro difficulty setting since the PS2 days, and never really graduated to being an All-Madden level player. All-Pro has always been a bit on the easy side, but I just never have a good time on All-Madden due to the A.I.'s excessive cheating.

Pro and All-Pro difficulties actually providing a challenge?

I'm having a really hard time with Madden 19, and I'm wondering if I'm the only one. The game feels like it's a lot harder to move the ball, and I'm still not quite sure if that's a result of the game cheating more, or if the A.I. has legitimately improved considerably, or if there's something wrong with me (are my 33-year-old reflexes simply not fast enough to play this game anymore?).

My early games were low-scoring defensive struggles in which I and the CPU struggled moving the ball.

I'm not the only one who's struggling; the CPU is only faring a little bit better. My first few exhibition games (on All-Pro difficulty, 9-minute quarters with 19-second accel clock) were field goal battles with final scores in the 16-6 or 20-10 range. I struggled to put up 150 or 200 yards passing or to surpass 30 or 40 yards rushing. The CPU didn't fare much better, usually getting around 150 yards passing, but beating me with 80 or 90 yards rushing.

In general, defensive reactions times and coverages (for both my team and the CPU team) seemed much tighter (without even having to tweak the game's A.I. sliders). Passing the ball downfield seems considerably harder and riskier, as receivers for both teams were often blanketed by man coverage, and the underneath defenders are uncannily good at reacting to the ball and swatting passes. They might even be a bit too good at swatting passes now, as even touch passes over the middle were routinely swatted down. Tiburon might need to tune down linebacker jumping abilities a smudge and add some animations of the ball being tipped instead of outright swatted.

Underneath defenders are swatting a lot of passes.

Passing concepts that had been reliable "money plays" for me over the past few years were completely shut down. Corners did a better job of staying with the receivers for Dagger, Corner, and comeback routes, and the defenders in the flats did a much better job of providing underneath support with those crazy leaping swats. Even when there were gaps in zones, I had trouble getting the ball off before defensive pressure got to me. Blocking is still a very binary "pass or fail" affair, so sensing pressure and getting the ball off on time is still largely a crap shoot. Drag routes seem to still be completely indefensible, but defenses are much quicker at converging and limiting the yards after catch.

This generally excellent coverage was counterpointed by occasional complete breakdowns. I had several instances in which my defender in a deep zone coverage (and it was always my defender!) would suddenly undercut the route while the ball is in the air -- as if to go for an aggressive interception or swat -- only to run himself out of the play and leave the receiver wide open with no help over the top. Almost every touchdown that I saw in those first few games was a direct result of one of these coverage breakdowns.

While I struggled with these early exhibition games, I did appreciate that Madden 19 was actually providing me with a substantial challenge unlike any that I had seen in the entire history of the franchise. And best of all, the game seemed to be relatively fair about imposing that challenge. As hard as it was for me to move the ball, it seemed almost equally hard for the CPU as well!

Could it be? After all these years, has EA finally produced a Madden game this is challenging, fair, and -- dare I say -- good?

...

I've been having a lot of trouble with Madden 19 so far. The game has so far seemed unusually difficult. Not just for myself, but also for my CPU opponents. Both myself and the CPU have had a lot of trouble moving the ball. Part of this seems to be the result of some tighter coverage in the defensive secondary. But a big part of it is the complete ineffectiveness of the running game. At first, I thought the problem was associated with the defenders not being bound by the same Real Player Motion locomotion limitations as the ball-carrier. This may still be the case, but I discovered that a big part of the problem is a recurring glitch in which the center gets stuck in a looping animation of him snapping the ball instead of blocking his assignment.

This problem happened several times during the course of my Franchise preseason game. I captured some footage of it, and edited it into a quick Youtube video highlighting the problem.

When this happens, the defender who the center is supposed to block (usually the defender closest to the quarterback or running back) goes completely unblocked and has an unobstructed path into the offensive backfield. This results in runs repeatedly getting blown up for losses of 3 or more yards. So far, I haven't seen it happen on a passing play, but it's possible that the bug affects passing plays as well.

The problem isn't isolated to the human user. While going back through some footage from that same game, I also saw at least one incident in which it happened to the CPU's center as well.

This isn't the first glitch that I've found in the game. I also posted a short clip of a defensive coverage glitch in which defenders in deep zones would undercut a receiver's route, as if to go for an aggressive interception or swat. The problem is that the defenders runs himself out of the play, out of position to even attempt such an interception or swat, and leaves the receiver open for a huge gain or a touchdown. I've seen this happen on several occasions, and the defender does it even though he doesn't have any help over the top.

Bugs like this have been pervasive enough in my early time with Madden 19 that I'm not sure if I can consider the game to even be viably playable at this point. It just isn't worth my time. I might have to put Madden aside for now and check out the recent patch for Maximum Football 2018 instead. Or hold my breath until Axis Football releases...

Here's something that I've never done before: a review of a game mod! I don't play mods very often. When I play games, I usually want to play the game that the creators created in order to get a feel for what their intent might have been. For some of the more sandboxy PC games that I play (like Cities: Skylines or the like), I might try some small mods.

There has yet to be an official game quite like Microprose's 1999 release, Birth of the Federation.

For this one instance, however, I'm making an exception because this particular mod fills a very specific niche desire for me that has gone unfulfilled for around 15 or 20 years. The "New Horizons" mod for Stellaris is finally allowing me to play a full 4-x strategy game set in the Star Trek universe. I haven't been able to do that since Star Trek: Birth of the Federation, developed by Microprose for Windows 98!

The creators seem to have been inspired by BotF.

Yes, there have been other Star Trek mods for other games in the past, and there's even some community projects to create spiritual successors to Birth of the Federation (such as Star Trek: Supremacy). The problem is that I've yet to ever see one of these get finished. "New Horizons" for Stellaris is still a work-in-progress, but it is mostly functionally complete and fairly robust. Since Birth of the Federation holds such a special place in my heart, I'm going to take a stab at reviewing "New Horizons" and see how it compares to my personal favorite [official] Star Trek game of all time.

Built on the back of Stellaris

"New Horizons" is, of course, a mod for the PC game Stellaris (developed and published by Paradox). Because of this, it takes advantage of most of Stellaris' strengths, but it is also hamstrung by many of Stellaris' faults.

"New Horizons" makes excellent use of the massive size and scale of Stellaris' maps by featuring a detailed recreation of the canon Star Trek galaxy, and including a surprisingly exhaustive roster of Star Trek races and factions -- all of whom are playable. Yes, of course, the big players like the Federation, the Romulans, Klingons, Cardassians, Ferengi, Dominion, and Borg are all here. As are all the expected ancillary empires like the Gorn, Tholians, Orions, and so forth.

The playable roster is surprisingly vast and exhaustive.

It doesn't end there, though. This mod also features a crap-ton of "aliens of the week" as fully-featured, playable empires. They aren't "minor races" like what we had in Birth of the Federation or the city states of Civilization V or VI. They don't just have one planet and a handful of ships just waiting for a "major faction" to conquer or absorb them. The obvious choices like the Vulcans, Andorians, Bajorans, are all there. The game also features empires like the Sheliak, Anticans, Selay, Caitian, Cheron, Dosi, Hirogen, Kazon, Krenim, Kelpian, and more! If you have a favorite space-facing civilization from any episode of Star Trek (including Gamma Quadrant aliens from DS9 and Delta Quadrant aliens from Voyager), there is a very good chance that it's a playable faction in "New Horizons"...

If you get this error message, then training will stop working completely, and will just hang on an infinite load screen.

Is your Madden 17 franchise getting hung up on an annoying bug that prevents you from doing weekly training? Are you getting a dialogue saying "Training is not ready. Ensure that you have focus players selected."? I had this happen to me, and the resolution is not immediately obvious. I searched the EA troubleshooting forums and Reddit and only found partial solutions that didn't work for me. Apparently, this "glitch" has a couple different causes.

Most of the solutions that I had read online involved adjusting the user team's depth chart. In some cases, users said that the problem was caused by not having enough active players in a specific roster position. By signing a player at the necessary position, the problem was resolved, But this fix wasn't applicable to all users. I specifically encountered this bug in week four of my franchise's preseason. It happened right after installing the 1.04 update, and I feared that the update had hosed my save file. Fortunately, I found a resolution.

First, I tested the fix suggested above by ensuring that I had players at all roster positions and that all depth chart positions were filled, but didn't have immediate success. After a little bit of extra troubleshooting, I found that it was because I had too many players on my active roster. I had signed an extra player to replace an injured player. The injury was only for 3 weeks, so wasn't worth putting the guy on IR, but the new player put me over the roster cap. Since it was preseason, the game apparently doesn't enforce a roster limit, but I noticed that the Week 4 activities included "Cut 11 players". Usually in week 4, you're only supposed to cut 10 players. So I cut some dead weight (so that the activity now says "cut 10 players") and the training loaded...

The attached video will show an easy, zero-risk method for utilizing poor pathfinding AI to easily dispatch all three giant club-weilding Barbarians near the Valley of Drakes / Londo Ruins entrance to Blighttown.

All you need to do is get their attention, then run back to the ladder that goes down into Blighttown and climb down a rung or two. The Barbarians will chase you, then fall to their deaths when they get to the wooden walkway. I was never able to get more than one of them to follow me at a time, so if you want to kill all three of them using this method...