The initial announcement of Star Trek: Discovery looked very promising. Unfortunately, the news has not been as good since then.
First of all, the first teaser showed some lackluster CGI effects, but I was willing to dismiss that as being evident of the show's early prouction. But then news kept getting worse. Bryan Fuller stepped down as the showrunner, CBS repeatedly stated that the show won't be an anthology (even though an anthology would be a great idea), and the show was delayed from January to March. Now it's been delayed again - this time indefinitely. The delays appear to be related with CBS's in ability to get its streaming service off the ground, delays in casting, and scheduling conflicts with those who have been cast.
But production has started, and the first teaser trailer has come out.
A behind the scenes teaser gives a look at uniforms, sets, possible ship redesigns, and the captain's chair.
The first thing that stood out to me is the tease of the new uniforms, which resemble a combination of the Star Trek: Enterprise uniforms, and the cadet uniforms from the rebooted Star Trek movies. But there's a huge flaw in this uniform: the breast badge is the delta shield. Since this is a prequel to the original series, this uniform is unlikely to belong to an Enterprise crew member, even though that delta shield was unique to the Enterprise in the original series.
The Discovery teaser shows a delta shield badge on a pre-TOS uniform - which is a Star Trek faux pax.
In the Original Series, each ship, starbase, or installation had its own unique mission badges, similar to contemporary NASA missions. This was a detail that even Star Trek: Enterprise got right! But the Abrams reboot, and now the new Discovery series have broken with this detail, making the uniforms anachronistic within established series' canon.
Each ship, starbase, or installation in The Original Series had its own unique mission patch, inspired by NASA missions.
By the time of The Next Generation, Starfleet had adopted a single insignia for the use of its communicator badges, which was based on the Enterprise 1701's mission insignia. Of course, this badge was a piece of technology, rather than a simple patch on a shirt, so there could have been technical limitations that required the adoption of a single insignia.
UPDATE: FEBRUARY 10, 2017:
Since seeing the trailer and writing this post, it has come to my attention that I may have over-reacted to the insignia. The presence of this insignia may be a reference to the possibility that the lead character of the show is going to be the first officer from the original Star Trek pilot. This character was played by Majel Barrett (who later went on to protray Nurse Chapel), and this character was un-named, and was only called "Number One"). So this character would have previously served onboard the U.S.S. Enterprise with Captain Pike. Perhaps this insignia is on Captain Pike's uniform?
Either way, the fact that this insignia is still being used as the show's insignia bothers me, as the show is called "Star Trek: Discovery". The insignia for the show should be the Discovery's insignia, and the Discovery should have an insignia all its own. But this insignia is dangerously close to the original Enterprise's
I really like Civilization VI! Of course, it has its share of nagging problems (some of which have been resolved already) - any game of this size and scope is likely to have issues at release. I've already been thinking of some ideas for how the game could be improved in expansions and DLC, and I'd like to spend a few posts to share some of those ideas with you now.
In my review of the game, I mentioned that oceans feel like they've regressed a bit since Beyond Earth: Rising Tide, in that they've returned to feeling like lifeless dead space on the map. Even though they're more important for Holy Sites and Campuses, mountains are also still mostly dead space on the map. They act as obstacles, and that's basically it. In expansions and DLC, I would like to see some of this space become more alive and useful. I'd like to spend this first suggestion post going over some ideas that I have for expanding the ocean mechanics, and for taking advantage of more of the map's dead space.
I have posted a link to this blog on Civfanatics at:
Feel free to discuss through the comments on this post, or via the linked forum topic!
Improve coastal cities
I'm very underwhelmed with coastal cities right now. Water tiles have very little utility. They provide small yield, can't have districts (other than a single harbor per city), and generally lack production. Coastal cities with lots of water are, thus, very unproductive and not really worth building. I think there's a couple ways to resolve this.
Harbors could provide a small amount of production. Or perhaps Harbors could act similarly to lighthouses from Civ V and provide production on sea resources. Or they could provide production on all adjacent sea tiles (so that placement is still important, and more of those empty sea tiles become useful and worth working, and you actually have to work them in order to get the benefit (as opposed to the Harbor just having an adjacency bonus). If we want to only use adjacency bonuses, then another alternative might be for Harbors to provide +1 production per adjacent coastal resource and +0.5 gold per adjacent water tile. That way, even cities that don't have clustered water resources can still have valuable locations for harbors.
Coastal and island cities lack production and have limited space to build districts.
Another way to improve coastal cities would be to have some more early policies that benefit coastal cities. Perhaps the Maritime Industries policy could be changed to "+1 production in coastal cities, and +1 production from Harbors". Alternatively, Maritime Industries could be similar to the Veterancy policy, and it could provide "+33% production towards Harbor districts and buildings for that district". Or we could have policies that do both! A new policy could be added that provides the bonus production for early naval units. Maybe there can even be a whole extra early-game civic (maybe called "Seafaring" or "Way-finding") that has some policies and buffs towards coastal and island civilizations.
The lack of production for coastal cities could also be offset by giving them more gold and/or food for growth (in order to support a specialist economy)... [More]
Being the follow-up to a masterpiece is no small order. Being the follow-up to two masterpieces is a Sisyphean task. Ico is a masterpiece of its time. Fumito Ueda and SIE Japan managed to follow that game with Shadow of the Colossus - a masterpiece of even higher order. The bar was set tremendously high for the team's third project: The Last Guardian. Multiple delays, a change in platform from PS3 to PS4, and Fumito Ueda's departure from Sony squashed a lot of the hype for the game. Might the game turn into vaporware? Or might it release in a condition analogous to Metal Gear Solid V?
On the surface, The Last Guardian comes off as being a mash-up of Ico and Shadow of the Colossus. Superficially, it's much more in-line with Ico: you play as a small boy who must guide a companion through a maze of environmental platformer obstacles and adventure puzzles. The catch this time around is that the companion happens to be a giant animal that you can climb and ride on.
The Last Guardian share more with Ico, but your companion is a giant creature that you climb and ride on.
The big difference though, is that The Last Guardian is sort of an inversion of the gameplay of Ico. In Ico, the player character had to guide a helpless (some even speculated she is blind) princess through a castle and defend her from shadow monsters that try to drag her away. In The Last Guardian, however, it is the player character - the boy - who is mostly helpless. True, you have most of the agency and are guiding Trico through the maze. But Trico is the one with all the power, and your progress is often dependent on Trico getting you past obstacles.
This point is most hammered home by the game's combat mechanics - or rather, its almost complete lack thereof. The boy can't fight off the stone knights that hunt him down. You can only run away, or let Trico smash them into dust for you. If they catch you, they drag you off to a nearby mysterious blue doorway (a parallel to the smokey portals that the smoke monsters dragged Yorda through in Ico), and all you can do is mash buttons to kick and squirm. Ico and Shadow of the Colossus experimented with player agency by making the player question the motivations of the character and wonder if maybe you're doing more harm than good. The Last Guardian toys with agency in other ways. In this game, you, the player, are the helpless tag-along character in an escort quest. You get a glimpse through the eyes of Yorda from Ico or Ashley from Resident Evil 4.
The boy can't fight back, he can only kick and squirm - much like Yorda from Ico.
Not entirely though. The player and Trico make mutual contributions to progress, and their contributions are shared much more than Ico and Yorda. Much like how Yorda could occasionally open the magically-locked doors, the boy in Guardian also has to pull levers and open doors for Trico to pass from room to room. The boy also has to destroy glass eye murals that mesmerize and terrify Trico to the point of paralysis. The boy also hunts down barrels of [supposedly] food for Trico to eat whenever Trico is tired or wounded. But then there's also parts of the game in which the boy simply hops on Trico's back, and Trico leaps away to the next puzzle area without the player having to do anything... [More]
Earlier this month, I posted a suggestion for hiding player ratings until the player has played enough games to reveal them. Afterwards, I posted a list of my suggestions for offense, defense, and special teams for Madden 18. That still leaves some other outstanding areas of improvement such as Franchise mode, and I'd like to spend this post focusing there.
Let's start out by going over some of the things that are left over from last year's wishlist:
A lot of these items are related to Franchise, and so keep them in mind as you read through this post. But before I jump into franchise suggestions, let's first look at the issue of the Accelerated clock as it has been implemented in Madden for years:
Accelerated clock, two-minute drill, and CPU timeouts
I've brought this up before, but clock management really needs to be addressed. The accelerated clock should never be disabled! Not in the two-minute drill; not ever. The two minute drill is when it is most important to enforce the accelerated clock because otherwise it completely breaks the two-minute drill. The CPU is particularly bad at exploiting this. I regularly see the CPU go into a huddle and break it within 5 seconds of game clock, which is faster than if they had tried a hurry-up, and which spares them from using a timeout. Human users can exploit this same tactic as well in order to avoid the time it takes to run up to the line. All you have to do is quickly select any pass play then audible or hot route your receivers.
Breaking a 2-minute drill huddle with 35 seconds on the play clock while
the game clock is running completely breaks the 2-minute drill.
And speaking of CPU timeouts: the CPU should actually use them. There should be some logic in place where if a CPU QB either can't figure out the pre-snap coverage, or he doesn't like the pre-snap coverage, then he should call a timeout to mulligan the play. This should happen if the defense puts eight men in the box when an inside run was called, or if the CPU QB reads press coverage on a wide receiver screen, or other such situations in which the the CPU determines that the player's play is likely to trump their play call. CPU defenses should similarly be able to burn a timeout if they read a particularly unfavorable personnel match-up.
Another improvement that could be made to the accelerated clock is to add some variability to it... [More]
I recently wrote regarding a proposal for improving practice squad and training features by hiding player ratings until the player has played enough games to reveal them. Of course, there's still a lot of other aspects of the game that I'd like to see improved. I was pleased that this year's Madden 17 implemented some items from my wishlist from last year. There's still a lot from last year's wishlist that I'd like to see implemented in some fashion. Playing Madden 17 has also raised new ideas for improvement.
Let's start out by going over some of the things that are left over from last year's wishlist:
Loose ball A.I. was a point on my wishlist last year, but it wasn't addressed, as evidenced by this clip.
Now, admittedly, a lot of the following suggestions are going to be based on my own subjective experiences with the game. And these opinions come from someone who is almost exclusively a single-user Franchise player. My priorities are going to be far different from the desires of MUT players or even online franchise players.
I'm also not going to bother (right now) with the obvious problems: rubberband AI that creates obnoxiously artificial "momentum swings", the broken man coverage, robo QBs, the complete unwillingness of my linemen to block at the point of attack on run plays, or the down-tuning of new features (such as throw out of sack, aggressive catch, and defensive line moves) to the point of irrelevance, and so on. Instead, I'm going to try to focus on less-obvious mechanics that interact with these problems and which have forced EA to make the [bad] decisions that they've made.
Better run-pass balance and longer games
The general design of Madden isn't very run-friendly. The fact that the game is balanced and tuned for quick, 6-minute quarter, pick-up-and-play online matches (instead of full 15-minute quarter games) means that grinding it out on the ground to establish the run is futile. Trying to run the ball in a 6-minute quarter game (with accelerated clock turned ON, which is the default) can rapidly burn through time. I regularly eat up an entire quarter and a half in a single drive when I commit to the running game in such matches, and that is just unrealistic. This forces both players and the CPU to depend on the passing game to score before a half expires. In my opinion, this is a fundamental design flaw of Madden, and the game will never be truly great as long as 6-minute quarters is the focus of design.
Madden's fundamental design is not very run-friendly.
But fundamental design flaws aside, my experience with Madden 16 and 17 has been that the CPU is completely inept at running the ball. Even when the blocking is solid, the CPU-controlled back can rarely identify and hit the hole, and usually runs right into a waiting defender or one of his own blockers. CPU backs are even worse at running to the outside, as they'll often run backwards in a futile attempt to get to the edge, instead of just cutting upfield for whatever yardage they can get. This often leads to large losses of yardage, backs up the CPU, and contributes towards the CPU's over-reliance on passing the ball. I usually play with the CPU Run Blocking A.I. slider up between 80 or 100, and yet CPU running backs still routinely finish games with stats along the lines of 15 rushes for 20 total yards. Pathetic. If a CPU runner does have a successful game, it's usually because they broke one or two long runs due to a missed tackle, and 90% of their yardage total comes from one or two plays. Also pathetic. Seriously, I have rage-quit games because of the CPU's ineptitude.
CPU Doug Martin runs right into his pulling guard [LEFT] instead of going inside like the trap play is designed.
CPU Doug Martin has a huge hole with only a single cornerback to beat [RIGHT], but cuts into traffic instead.
I also have a lot of trouble running the ball myself with my own Run Blocking A.I. slider set to anything below 50... [More]
|12|| || || || || || ||60|
|11|| || || || || || ||55|
|10|| || || || || || ||50|
|09|| || || || || || ||45|
|08|| || || || || || ||40|
|07|| || || || || || ||35|
|06|| || || || || || ||30|
|05|| || || || || || ||25|
|04|| || || || || || ||20|
|03|| || || || || || ||15|
|02|| || || || || || ||10|
|01|| || || || || || ||05|