Every year, I hope that UNLV's football team will show some improvements. That it won't repeat the same mistakes that it's made year after year.

But every year, UNLV finds a way to let an easily winnable game slip away early in the season, setting a tone of disappointment for the entire season. Usually, UNLV at least gets its first game or two against a power conference team and gets to raise an illusion of optimism by playing surprisingly well until they inevitably get overpowered in the fourth quarter.

Cam Newton's little brother, Caylin, thrashed UNLV with his legs in a 43-40 upset.

But this year, the tone-setting upset couldn't even wait past week one. In fact, it couldn't even make it past the first play of the season. UNLV opened its 2017 season by going offsides on the opening kickoff. They went on to play a mistake-filled game that Howard University exploited to a 43-40 victory -- the biggest upset against a point spread in college football history. A $100 bet on Howard to win outright would have won you $55,000.

UNLV lacked discipline, committing multiple procedural penalties that killed drives and put UNLV in a hole early. They lacked energy and couldn't contain freshman quarterback Caylin Newton (Cam Newton's younger brother) who dominated UNLV with his running ability. And UNLV gave up back-breaking fumbles that prevented momentum from swinging back in their favor.

UNLV seemed to have a lot going for them going into this season. UNLV had one of the top running games last season. The defensive line is supposed to be improved. Star receiver Devonte Boyd is back from a severe injury that prematurely ended his 2016 campaign, and he has a hyped up freshman quarterback throwing him the ball.

The offense did show some promise. Rogers and Boyd connected on some big passes, and the running game looked pretty good. They even met their goal of 40 points per game!

Armani Rogers and Devonte Boyd hooked up for a couple big plays.

The defense, however, looked abysmal. From the start, they showed a frustrating lack of energy. They lost contain, missed open-field tackles, and couldn't get to Caylin Newton in the pocket. From the start of the game, the defense looked like it was tired, as if it had already gone through three quarters of ground-and-pound football. Howard had even recognized that UNLV's greatest weakness is likely to be its secondary and coverage against the deep pass. Howard took a number of shots down the field, but was never able to connect. Kudos to Howard's coaches for identifying that vulnerability and designing a gameplan to exploit it, but they didn't have to exploit UNLV's obvious weakness, because even the supposed strengths of the defense looked rusty and full of holes...

Rumors of a Demon's Souls remaster or remake have been floating around for a while now (as have rumors of a sequel). I have mixed feeling on the idea of a remake/remaster. On the one hand, Demon's Souls is one of my favorite games ever and may represent the peak of the series. Naturally, I want more people to play it and recognize its brilliance.

On the other hand, my fondness for the game means that I am hesitant to allow anyone to modify the game at all. After suffering through the abysmal Silent Hill HD Collection, I have strong reservations about any game remastering. Even the announced remake of Shadow of the Colossus has me on edge.

Sadly, a remaster would probably mean that the servers for the original game would finally get shut down. But I guess having a replacement would be better than having no Demon's Souls at all...?

So with Dark Souls having come to its end with its Ringed City DLC, I've been thinking a lot lately about what I might want to see in any potential Demon's Souls remake or remaster -- if it were to happen.

Table of Contents

• Things to keep
  • Maintain uniqueness of each boss
  • Keep the Item Burden
  • Maintain the Online Elegance
  • Finite Crystal Lizard respawns
• Things to Fix
  • Grass farming
  • Heavy Armor and Poise
  • Defenseless Snipers
  • Colliders and Hitboxes
  • Obstacles and General Camera Instability
  • Character and World Tendency
  • Combat Updates and Other Soulsborne Suggestions
• Things to Add?
  • Cross-Platform Multiplayer and Activity Levels
  • Finish the Incomplete Sixth Archstone
  • Left-handed Characters
  • Import PS3 Save File!

I was a little late at seeing the Bears' first 2017 preseason game. I had meant to record it Thursday evening and watch it later that night. Instead, my DVR recorded two hours of A Football Life instead of the game. I don't know if this was NFL Network's fault for airing the wrong show, or if it was Century Link's fault for mislabeling the schedule. In any case, I had to wait to record the re-broadcast later Saturday morning and watch it Saturday night.

I've been pretty vocal about my confusion with the Bear's offseason quarterback decisions. While I wasn't sorry to see Jay Cutler kicked to the curb, I was very unsure about signing Mike Glennon. I was even more dumbfounded by the Bears' decision to trade up to draft Trubisky after having already spent all that money on Glennon.

Glennon didn't give fans reason to be optimistic, as his preseason debut went about as bad as it could possibly go. His second pass of the game was intercepted by Chris Harris Jr. and returned for a touchdown.

Mike Glennon's second pass was intercepted by Chris Harris Jr. and returned for a TD.

In Glennon's defense, the offensive line wasn't doing him many favors. He seemed to be getting hit every time he dropped back. While Chris Harris Jr. was high-stepping the pick into the end zone, Glennon was peeling himself off the turf. If the Bears want Glennon (or any quarterback they decide to field) to be successful, then they're going to need to beef up their protection.

Cody Whitehair, in particular made a key mistake by snapping the ball over Glennon's head during the Bears' second possession. The ball was recovered by the Broncos, but the Bears' defense managed to hold them from scoring.

Cody Whitehair snapped the ball
over Glennon's head.

The Bears' third drive was where they were finally able to move the ball for the first time in the evening thanks mostly to their running game. Jordan Howard only got a few runs, but rookie Tarik Cohen made some pretty good runs that may earn him some extra play-time and maybe a spot on the final roster. Down 10-0, Glennon ended his night in the early second quarter with only two completions on eight attempts, with the pick-six and a quarterback rating of 0.0 -- yes, that's zero point zero!

Mark Sanchez didn't see much playing time, but I think the coaches probably have a pretty good idea of what Sanchez brings to the team...

The Kingdom of Kongo was a small, but prosperous kingdom located on the west coast of sub-Saharan Africa. It can trace its origins back to the late 14th century, when Lukeni lua Nimi conquered the city of Mwene Kabunga and renamed it M'banza-Kongo. The city grew rapidly in an otherwise sparsely-populated region, and by the 17th century, it contained about one-fifth of the entire Kongo population (around 100,000 people). It's large population made it a prosperous and wealthy trading hub that eventually attracted the attention of European powers. The Portuguese set up colonies in Kongo territory, where they would set up a Roman Catholic church that would become one of the strongest churches in all of Africa. In 2017, the entire city of M'banza-Kongo was declared a UNESCO World Heritage Site.

In the first half of the 16th century, Kongo was ruled by Mvemba a Nzinga. His father converted to Christianity following the arrival of the Portuguese, and Mvemba a Nzinga added "Afonso" to his name, later becoming known as King Afonso I of Kongo. Afonso played a leading role in Kongo's conversion to Christianity and helped to establish and promote the Roman Catholic Church in the region. The reasoning for his conversion is unclear. Some scholars believe that he was motivated by genuine faith; while others believe that he was only complicit in the conversion in order to facilitate trade with European powers, and possibly to try to spare his population from becoming subject to the Atlantic slave trade. While Kongo had a slave economy of its own, and the kingdom willingly sold slaves to the Europeans, Afonso still denounced the Portuguese as exploiting Kongo's cooperation by kidnapping free Kongo citizens in violation of Kongolese law. The King of Portugal responded by dispatching officers to oversee the slave trade and ensure that only lawful slaves were sold to Europeans, and he demanded additional tribute from Kongo, such as wines and grains.

DISCLAIMER:
Civilization VI is still very early in its life-cycle. Strategies for the game (and for specific leaders and civs) may change as Firaxis applies balance patches, introduces new features, or expands the game through DLC or expansion packs, or as the Civ community discovers new strategies. As such, the following strategy guide may change from time to time. I will try to keep it up-to-date, and will make notations whenever changes are made. I'll also post links in the official 2K forums and CivFanatics, where I'll also report any changes made. If possible and practical, I will try to retain the original content of the strategy for posterity.

I welcome any feedback or suggestions that readers wish to offer. Feel free to post on the linked forums, or by posting a comment at the bottom of the page.

This guide is up to date as of the Summer 2017 patch (ver. 1.0.0.167) (Nubia DLC)

Kongo is a civilization that thrives in jungles and forest, growing massive (and productive) cities. Mvemba a Nzinga adds a unique religious flavor to the civilization by preventing it from being able to found its own religion, while simultaneously wanting other players to send their religion to you.

The 2016 reboot of Master of Orion kind of shoots itself in the foot a bit with its own subtitle: "Conquer the Stars". When I play 4x games, I like to feel like I'm really building an empire, managing an economy, and conducting diplomacy. All of those things are present in Master of Orion, but I've gotten a pretty distinct feeling that this is yet another strategy game that falls victim to military rushing being the optimal strategy by far. Master of Orion doesn't really want you to build a civilization and colonize the galaxy; it firmly wants you to do what its subtitle tells you: conquer the stars.

Master of Orion III was kind of shit (it was boring, ugly, and completely lacked personality and substance), but at least it made some effort to be new and interesting. Most noticeably, the galactic map was actually three-dimensional. Sure, this was a navigational and UI nightmare for the human player, but it required players to think differently about how they approached expansion and warfare. At a more fundamental level, MoO3 sought to be a game about macro-management, asking the player to manage a vast galactic empire rather than just a collection of a dozen or so planets. The meat of the game, thus, was intended to be in the mid-to-late stages, as developed empires engaged in epic battles for survival, rather than all the fun and challenge being front-loaded in the early rush to colonize all the nearby planets. It didn't work, but at least it was trying to genuinely innovate the 4x genre.

The new Master of Orion isn't anywhere near that ambitious, and seeks instead to simply bring the original Master of Orion concept (in its simplest form) into the age of high-resolution 3-d graphics. It's a scaled-down, bog-standard space-4x game that borrows heavily from Endless Space and Civilization V. But it is at least a competent one!

Conquer the Stars isn't as big, complex, or ambitious as Master of Orion 3, but at least it's competent.

The galaxy itself isn't very big this time around. Depending on the map's size, there's only a few dozen stars, and most of them only have two or three planets. Unstable star lanes and space monsters can lock you out of exploring certain systems until you research certain technologies or grow your military sufficiently large (respectively). Other than that, exploration is over fairly quickly (especially once you start performing map trades in diplomacy).

Planet-management is also fairly easy. You can assign population meeples between one of three different types of output: food, production, and research. Meeples of different jobs and races have different icons, and unhappy meeples on strike have icons that sit down holding a picket sign. It makes it very easy to see what your population's current status is at a glance. There's just not really much to do with them. You don't have to assign them to work specific buildings, and with only 3 outputs to manage, balancing or specializing isn't that difficult.

All the buildings in the game are also one-time builds that don't serve much function other than to provide flat points of one of the three outputs, or to modify the efficiency of meeples in a particular output category. Buildings that have unique functionality (such as the Spy Center, Gravity Generators, or Interplanetary Administration) are few and far between. The only other thing that you do with your planets is to occasionally terraform them in order to boost your max population and unlock additional slots along each of the output tracks.

Each point of population is of a specific race, which affects the morale of conquered planets.

The tech tree also feels kind of bland and linear. I would much prefer a tech web along the lines of Civilization: Beyond Earth. Master of Orion kind of goes in this direction a bit by including some techs in which you have to chose which of two different items you want to take when you research certain techs. You can then trade for the other via diplomacy if you want to. It's kind of like the leaf nodes in Beyond Earth, but only some techs have them, and I rarely had to think too hard about which one I wanted...