In my recent time playing Dark Souls for On the Branch Gaming, we discussed several ideas for ways that the game could have been improved. I'm not sure if From Soft will be making any more Dark Souls or Bloodborne games (at least not anytime soon), but if they do, here's a list of some things that I'd like to see them improve. At the very least, we can consider this to be a retrospective, "How could they have done it better?" brainstorm, and any other developers who want to try their hand at a Souls-Borne-style game could maybe try these alternative designs out for their games.

This isn't a wishlist of changes that I'd like to see in specific games. I've already done those for each of the Souls games:

• Pre-Dark Souls wishlist
• Pre-Dark Souls II wishlist
• Dark Souls II wishlist
• Dark Souls III wishlist
• Bloodborne wishlist

Some of these posts (and the ideas presented in them) haven't aged very well, but I do stand by most of the suggestions offered in the above posts. At the very least, they offer perspective on how my own perceptions of the games have evolved over time.

Table of Contents

• More informative UI
  • Collection log
  • More HUD indicators
  • Preview equipment upgrade paths
• Demonstrative tutorial
• Left-handed controls
• Multiplayer and matchmaking
  • Concede to a PvP match-making Ladder
  • A widening field of cooperators

More informative UI

The UI is something that could definitely use some work. Each game in the series made minor tweaks to the UI - sometimes improving the overall experience, other times seeming to regress to a clunkier interface. But there are some things that probably should have been present, if not in Demon's Souls, then at least by Dark Souls or Dark Souls II. Some of these things seem so obvious that it boggles my brain that nobody at FROMSoft thought of them. Or maybe they were always items near the bottom of the priority list, that the team simply ran out of time to ever implement.

Collection log

Something that persitently bothered me across all the Souls-Borne games was the intrusive item-pickup notification. That giant, black box sitting almost dead in the center of the screen, partially blocking your view of your character and his or her immediate surroundings, did not need to be there. If you pick up an item in the heat of battle, then having to press X to dismiss it could be just enough of a distraction to get you killed.

While playing Dark Souls with On the Branch Gaming,
I was reminded how distracting the item-pickup notifications are.

Instead of this big notification box, I propose an alternative: put a smaller notification in the corner of the screen somewhere that vanished after a few seconds. Since we don't want to miss knowing what we just picked up, the game should also include an item-collection log in the menu. Heck, it wouldn't even need to be a separate screen, it could just be a sorting option in the existing menu: sort by recently-acquired...

I've written quite a few wishlist and feature proposals for video games on this blog. But today I'm going to do something that I don't think I've done before: suggest ideas for a board game expansion. In this case, I'm going to outline some ideas for my own user-made expansion ("mod"?) for Bloodborne: the Card Game. An official expansion may be due out later this year, so perhaps designer Eric Lang might come across this post and incorporate some of these ideas.

In my review of the card game, I mentioned that the card game adaptation is very simple, that a lot of stuff from the source material seemed strangely absent, and that it almost seemed as though the designers were leaving the door open for some easy expansion material. So I'm going to go ahead and try my hand at creating some of that material.

This isn't the first time I've ever tried my hand at modding a board game, but it is the first time that I've publicly posted my ideas. One of my better ideas (I think) was to try to write a series of national agendas for each of the factions in Axis & Allies, which would be drawn in secret at the start of the game. Only the faction(s) that fulfilled their agendas (and won the war) would be considered victorious. The idea was to make the game more interesting for more than just two players. Probably my most successful mod idea was for the Battlestar Galactica board game (specifically the Exodus expansion). Nobody in our BSG group ever liked playing as Laura Roslin, as we didn't feel that her benefits offset the handicap of having to sacrifice cards from her hand. In order to make her feel more viable, we all agreed that instead of having to discard two cards, Roslin could chose to take a trauma token. This introduced the risk that she might suddenly die (if a blood stain was drawn), but also allowed the player to keep her cards in her hand if they were going to be needed.

So let's see if I can come up with some workable expansion suggestions for Bloodborne...

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:
https://forums.civfanatics.com/threads/using-more-of-the-dead-space-in-the-map.610171/.
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)...

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:

• film study
• weather forecast
• preseason substitution logic
• hot blocks
• delayed kneel down and rugby punt
• onside kicks and loose ball recovery
• coach's challenge option
• scheme experience
• training camp
• multi-week scouting
• Mulligan the previous draft
• time to read the opponent's offense

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. This should be tied to a QB's Awareness and/or Play Recognition rating, and there could maybe also be a small chance that if the QB doesn't make the right read, then the coach can call a timeout instead. 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...

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:

• film study
• weather forecast
• preseason substitution logic
• hot blocks
• delayed kneel down and rugby punt
• onside kicks and loose ball recovery
• coach's challenge option
• scheme experience
• training camp
• multi-week scouting
• Mulligan the previous draft
• time to read the opponent's offense

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 an hour into 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 60 or so...