28 March, 2020

The Dread Rocket Raticate


Mount Moon is an interesting place. Located in northern Kanto, it's notable not only for its wealth of Pokémon Fossils, but also its extraordinary rate of meteorites per year. I spoke with Gym Leader Brock about it before leaving Pewter City and learned that it was somewhat a rite of passage for Pokémon trainers heading out from western Kanto to the eastern plains. There were certainly easier ways to get to Cerulean City and Saffron City, but Brock assured me that if I was serious about Pokémon training, Mount Moon was the best way to go.
Mount Moon is an arduous climb and littered with numerous interlocking caves that weave beneath the peak. It was not for the faint of heart, but it would be a chance to bond with my Pokémon in the wilderness. I used some of the winnings I earned at Brock's gym to stock up on food, potions, and a handful of Pokéballs before setting out down Route 3 toward the famous landmark mountain.
Along Route 3, I battled a very enthusiastic Shorts Appreciation Fan Club. Delightful young trainers eager to challenge Brock and head off on their own through Mount Moon, but mainly obsessed with shorts. It was along this route and among these youngsters that I first heard the name Team Rocket whispered. According to these young campers and hikers, Team Rocket had set up an operation of sorts at Mount Moon and their presence there was deterring a lot of trainers from passing through.
Back then, Team Rocket was an organization to be feared. They had a lot of influence over everyday life in Kanto, and very few people had the courage to stand up to them. However, as a newcomer to the Kanto region, I was truly clueless at the time. I could see that the kids were unsettled by the thought of Rocket grunts lurking in the caves of Mount Moon, but I was incapable of understanding what this threat meant to them, or what it would come to mean to me. I pressed onward down Route 3 hoping to reach the base camp and Pokémon Center at the foot of Mount Moon before nightfall.
Along the way, I managed to catch a Spearow who I gladly added to the team. I named him Shakespear. Shakespear would come to serve me well inside the dark tunnels of Mount Moon. He needed some training before we entered, so I set to work using the base camp as our new base of operations. Shakespear proved to be a formidable bird and was not unlike Kiwi in his ability to grow quickly adept at fighting and training.
While we were training in the shadow of Mount Moon, Lucky developed a powerful psychic attack that had the potential to inflict confusion upon his opponents, and I noticed Nibbles able to inject a bit of poison from the tip of his horn with some regularity. I was certainly impressed in the team's progress. It was time to start our trek through the underbelly of Mount Moon.


The Zubat was one of the easier Pokémon to sketch,
due largely in part to their huge colony within Mt. Moon.
They don't write this on any of the brochures that I saw, but Mount Moon is absolutely infested with Zubat. You can't go three feet without being assailed by another Zubat, and so naturally the next great addition to Team Fox was a Zubat named Vesper. As I'm sure you can imagine, if you are at all familiar with Zubat, Vesper was a bit of a nightmare to train. That might actually be an understatement.
As we methodically made our way through Mount Moon, I was determined to get Vesper up to par with my other traveling companions. He would often open up a battle with other Zubat, or with the occasional trainer we found along those winding paths, only to be replaced with Shakespear who was an absolute terror in those tunnels.
Shakespear earned his place on my team as the number one Zubat deterrent on Mount Moon. He could out-perform them at every turn, pecking them out of the sky and sending a message that we were not to be trifled with by other Zubat. Those other Zubat did not get that message, however, and continued to plague us the entire time.
Among the outer caves of Mount Moon, I ran into a wide variety of trainers. As Brock had mentioned, it truly did seem as a thoroughfare for aspiring trainers to test their resolve against both the forces of nature and each other. In this particular case, Mount Moon served to test young trainers against a never ending onslaught of territorial Zubat. There were young boys and girls, among them a bug catching kid who wandered too far from Viridian Forest, I presume. I passed and challenged the occasional hiker and a science enthusiast. None posed much of a problem for my team and the pain of losing Rascal felt like it was passing somewhat.

In the heart of Mount Moon, I finally encountered members of Team Rocket. As I approached in the darkness, I heard them talking. Another young trainer had passed through quite recently and dealt them a severe Pokémon beating that still had them upset. Instead of keeping him out of their operation, he had apparently just blown straight through them and their Pokémon without hesitation. When they saw me lurking in the darkness, eavesdropping on their conversation, well they decided to take out their frustrations on me.
Although most of them were weakened by this previous trainer to a point where they couldn't even muster a Pokémon to participate, there was one trainer in that dark tunnel I will never forget. He was the champion of their little operation under Mount Moon, and he would make me pay for wandering where I wasn't wanted. He only had one Pokémon to face my five, but it was enough. I was lucky he didn't have any more.

This Rocket Grunt had an absurdly powerful Raticate, an evolution of my previous Pokémon, Rascal. I knew I had to be careful and so I threw out Lucky to face him. Lucky had recently learned to harness particles on its wings into powerful toxins, and so I had Lucky blow a debilitating sleep powder onto the Dread Rocket Raticate as I would come to call it. As expected, the Raticate dozed off gently and opened itself up to tormenting psychic attacks from Lucky.
What I did not expect was its incredible resilience to Lucky's powerful psychic ability. This ability had taken down numerous thick skinned Geodude along the tunnels of Mount Moon, but the Raticate was formidable. I could tell it was almost defeated, but just as Lucky was going to incapacitate it, Dread Rocket Raticate woke up. It quickly evaded the next attempt to spread a sleep powder. Then it bit down and it bit down hard on Lucky. It was a blow so devastating that Lucky was indeed lucky to not pass out from the strain. I had to switch.
I took a moment to collect myself with all the other Rocket grunts gathered around to cheer on their formidable leader and his terrible Raticate. I knew his Raticate was on the verge of defeat. It would only take one more solid hit to knock it out of the fight and claim a victory. Vesper was still useless. Kiwi and Shakespear were valid candidates, because of their speed and agility. But of all my Pokémon, Nibbles had the most solid defense with his very thick hide, so I felt if any of them were going to survive that devastating hyper fang it would be Nibbles.
Sadly, I was wrong. Nibbles came out of his Pokéball twitching his long ears and ready to face any challenge. Nibbles didn't even have the chance to see what hit him. That damned Raticate bit down on Nibbles head so hard that he was done in seconds. There was no time for Nibbles to react. His fight was over before it had even begun. I let out a loud wail that echoed through the caverns beneath Mount Moon, but that exclamation of shock and disbelief was drowned out by the numerous members of Team Rocket whooping and hollering at their leader's small victory.
It would be short lived. Kiwi came out and could sense my distress. He launched a brutal quick attack on the Dread Rocket Raticate and ended the fight in a single decisive blow. Team Rocket was not amused, but they were out of Pokémon and wouldn't dare lay a hand on me with my trained Pokémon at my side ready to defend me.
I carefully excused myself from whatever nefarious plot they were hatching in that large cavern. They allowed me to pass on my way without any more provocation. They probably said a bunch of intimidating junk that those gangster types like to say, but honestly my heart was sunken deep into the ground. I wouldn't have heard anything they said. Although probably meaningless to them, I had failed Nibbles and now we would part ways forever.
Speaking honestly, I had high hopes for Nibbles. He was so small and weak when we met, but he had the heart of a champion. I thought Nibbles would be with me on Victory Road, facing down the Elite Four and the Indigo Champion. I thought we would take on the world together, but these foul Team Rocket hooligans put an abrupt end to that fantasy.
I nursed Nibbles back to good health in some quiet corner of Mount Moon and spent our last remaining moments together just appreciating the company. Much like with Rascal, I tried to explain to Nibbles why it was important to me that he lived out the rest of his life here on Mount Moon (and I could truly think of no better place for him) and why I would have to press on without him. I shed a few tears and gave Nibbles a careful hug, avoiding his poisonous horn. He seemed to understand and with a final look at me, he scampered off into the darkness.
I soldiered on for Rascal and Nibbles. I pressed on to Cerulean.

Current Team:
Attacks in Blue are recently learned.

Download Arizona Sunshine For PS4

Download Arizona Sunshine For PS4


DarKmooN | CUSA07980 | Update v1.03 | VR | HACKED

  • Release Date: Out Now
  • Genre: Action / Horror / First Person Shooter
  • Publisher: Vertigo Games
  • Developer: Vertigo Games / Jaywalkers Interactive







Arizona Sunshine puts you in the midst of a zombie apocalypse, exclusively in VR. Handle weapons with real-life movements, freely explore a post-apocalyptic world, and put your survival skills to the test with PlayStation®VR - putting the undead back to rest is more thrilling than ever before.


 DOWNLOAD LINKS

  DOWNLOAD DARKMOON VERSION

 DOWNLOAD PART 1
 DOWNLOAD PART 2
 DOWNLOAD UPDATE 1.03:

 CLICK TO DOWNLOAD 


GAME SIZE : 3.8 GB
Password: After 10$ payment is done


Press Release - Greater Than Games Temporarily Closing Parcel Shipments


FOR IMMEDIATE RELEASE
St. Louis - March 23, 2020 - Greater Than Games announced today that we are closing parcel shipments until the estimated date of April 22nd due to the St. Louis County stay-at-home orders and for the safety and health of our employees. This date is subject to change based on federal, state, and local regulations. We are fulfilling all webstore orders placed before March 23rd. We have placed all of our non-digital content to "out-of-stock" on our webstore to ensure no orders can be placed at this time.

As announced in our March 17th press release, we are offering all of our digital material downloads for free, including PDFs of all of the currently released material for Sentinel Comics: the Roleplaying Game and the Cheapass Games in Black and White book. Click here to learn more.

About Greater Than Games, LLC
Greater Than Games, LLC is a leading tabletop game developer and publisher based out of St. Louis, Missouri. Established in 2011, Greater Than Games is well-known for delivering engaging, richly-themed, highly-replayable tabletop games.

Look for Greater Than Games titles in major markets worldwide.

Did you like this press release?  Show your support: Support me on Patreon!Also, click the heart at Board Game Links , like GJJ Games on Facebook , or follow on Twitter .  And be sure to check out my games on  Tabletop Generation.


23 March, 2020

Tech Book Face Off: Breaking Windows Vs. Showstopper!

For this Tech Book Face Off, I felt like expanding my horizons a bit. Instead of reading about programming languages or software development or computer science and engineering, I thought I would take a look at some computer history from the business perspective. There are plenty of reading options out there in this space, but I settled on a couple of books about Microsoft. The first, Breaking Windows: How Bill Gates Fumbled the Future of Microsoft by David Bank, is about Bill Gate's hardball business tactics that won him a monopoly in the PC desktop market, but then nearly destroyed the company in that fateful confrontation with the US Justice Department and caused him to miss the Internet and, later, the mobile revolution. The second, Showstopper! The Breakneck Race to Create Windows NT and the Next Generation at Microsoft by G. Pascal Zachary, has an even longer subtitle that neatly describes the book on its own. Both of these books were written quite a while ago, so let's see how their stories hold up today.

Breaking Windows front coverVS.Showstopper! front cover

Breaking Windows


The narrative starts out with the backstory of how Gates came into his PC desktop monopoly by realizing that software—specifically the computer's operating system—would be an important and valuable part of the PC ecosystem. As PC hardware got cheaper and more prevalent, the software volumes would grow with the spread of the hardware, and at essentially zero marginal cost to Microsoft. All they needed to do was become the defacto standard OS. That's what Gates set out to do, and he succeeded with Windows 3.1 and then Windows 95. The bulk of the story takes place after Microsoft had achieved its monopoly and was deciding on strategies to defend it.

One of the main strategies was to identify competitors that were creating software that was somewhat tangential to Windows or could be added as a compelling feature, and whose software was becoming popular enough to potentially pose a threat to Windows by becoming a new platform. Microsoft would then create their own version of that software and integrate it into Windows or otherwise absorb the other company's software, nullifying the threat to their monopoly.

The most prominent example of this absorption strategy came with Internet Explorer and the browser wars between Microsoft and Netscape. Netscape Navigator started out with nearly the entire market of the World Wide Web before Microsoft got into the browser business. By the time Microsoft had revved up to IE 3.0, they had claimed a significant amount of market share from Netscape, and because of bundling IE with Windows and offering it for free to older versions of Windows, Netscape was doomed to lose in the long (or not-so-long) run.

Everything was not all peaches and cream within Microsoft, though. There were two warring camps fighting for the soul of Microsoft. On one side was the Windows team led by Jim Allchin that was developing the next big thing: Windows NT. On the other side was the Internet Platform and Tools Division led by Brad Silverberg that wanted to leave Windows behind and try to capture as much of this new Internet frontier as possible, using IE as the platform. Gates would end up siding with Allchin and IE became a part of the Windows platform instead of growing into one of its own.

It's almost comical seeing some of these disagreements today. One of the most important features of the IE platform that was integrated into Windows as an option was Active Desktop, but this feature seems so inconsequential today. Making the desktop background a web page was fraught with problems, and all that has survived is a way to enable single-click icons instead of the usual double-click to run a program. I don't think hardly anyone used it, especially after dealing with multiple desktop crashes. I remember it being a novelty for a while, but I soon stopped enabling it because it was so annoying and a double-click is so ingrained in my desktop usage.

Of course, the disagreement with the Justice Department over Microsoft's monopoly was not so insignificant. Part of the reason their tactics got them into trouble was because IE was offered as a free upgrade for older versions of Windows that didn't have it or had older versions of IE. If Microsoft had truly made IE an integrated part of Windows and only released new versions of it with new versions of Windows, Microsoft's competitors wouldn't have had as strong of a case. Microsoft wouldn't have had as strong of a monopoly, either, because IE was getting new versions much faster than Windows was and people that didn't upgrade Windows were still getting free upgrades of IE.

Even so, the government's eventual breakup proposal was preposterous. They wanted to force Microsoft to set prices for Windows versions with and without IE based on how many bytes each version was, like it was produce or meat or something. The government obviously had no understanding of what software really was, no idea how ridiculous that sounded, or what a good solution to the real problems of Microsoft's monopoly would actually look like. In the end that proposal was dropped, and the entire court case seemed to have done nothing more than give Microsoft a ton of bad press.

In the mean time Gates had done plenty of other damage to Microsoft and Windows because of deciding to pursue these retrenchment strategies with the browser and other things related to the Internet. Bank makes the case that Gates should have pursued the Internet platform strategy in order to disrupt his own business and grab the larger market that was just coming to light, but I'm not so sure that would have worked, either. If he had done that, would he have been able to beat Google before they rose to the top, or would he have been able to foresee the coming of mobile and the smartphone before Apple took over with the iPhone? It's hard to imagine Microsoft getting all of that right and still being top dog today. (Although they're now doing quite well now under Satya Nadella.)

There was so much more in this book, like the section on how XML came to be. (Of course bloated, complicated XML was created at Microsoft. In the book it was portrayed as a genius innovation by Adam Bosworth that would help Microsoft take over Internet data flows in spite of Gate's decisions. I'm so glad JSON has stopped that nonsense.) I could keep going, but it's all in the book. It was a wonderful trip down memory lane, covering plenty of things I had forgotten about that were a big deal at the time (remember the AOL shortcut bundled on the Windows Desktop). The book is decently written, if a bit confusing at times. Bank jumps around a lot, and there's no overarching timeline to the narrative. Regardless, it gives great insights into what was happening at Microsoft through all of the turmoil in its history and is well worth the quick read.

Showstopper!


As the subtitle describes, Showstopper! is the story of how the first version of Windows NT was conceived and built. It makes for quite an engaging story, as the NT team was arranged within Microsoft in a unique way for the company. Instead of being a department that reported to and was directly overseen by Bill Gates, the team was more of a startup company within Microsoft that operated fairly independently and was left more or less to its own devices. Gates did check in and imposed some of his own requirements from time to time, but not anything like other departments within Microsoft.

One of the main reasons for this independence was the force of nature that was Dave Cutler, the chief architect and director of Windows NT. Cutler was aggressive and expected incredible things from his team, and he did not get along well with Gates, either. Gates had hired him when Cutler had left Digital Equipment Corp. and respected and trusted him enough to let Cutler run things as he saw fit, so Gates pretty much left him alone.

Cutler had brought along a number of programmers from his team at Digital to be the core of the NT team, and as he took on more Microsoft employees to build out the team, a rivalry emerged between the two groups:
The Digital defectors also were more methodical about their jobs, hewing to textbook engineering practices in contrast to the Microsofties, who often approached a problem helter-skelter. Cutler's people took work seriously, while Microsofties sometimes tossed nerf balls in the hallways or strummed guitars in their offices. The differences in style were apparent to Cutler's people, who derisively referred to Microsoft as "Microslop." By the same token, Microsofties were put off by the clannishness of Cutler's gang.
Regardless of these divisions, work got done and NT progressed through big scope changes and constant feature creep. Throughout the project Cutler never really trusted or approved of the graphics team. He had always been a terminal kind of guy and didn't see the need for a GUI, and he did not agree with the graphics team's much more laid back approach to software development. The graphics team was dealing with their own internal issues as well, having chosen a new, immature programming language to write the GUI: C++. While it was a new language at the time and the supporting tools were rough and unstable, G. Pascal Zachary's assessment of the language seems a little off:
While it was portable, however, C was difficult to master and gave a programmer a great deal of latitude, which increased the likelihood of coding errors. A more inspired choice—a gambler's choice—was C++, a newer language that was all the rage among software theorists. By preventing code writers from making mistakes, C++ promised faster results and greater consistency, which would benefit programs that were the work of many people.
C++ is hardly easier to master than C! With C++ being a superset of C, C is most certainly the simpler language. While it may be true that C++ can support larger projects, it is also quite easy to make C++ programs much more complicated than C. These kinds of off-the-cuff assessments were fairly common in the book, and they made it seem like Zachary was either over-simplifying things or he didn't fully appreciate the technical aspects of these topics. This tendency to over-simplify was especially apparent whenever he was discussing features of NT. The discussions nearly always dealt in generalities, and it was difficult to figure out which features, exactly, he was talking about. He would mention that features were missing from NT or that programmers were adding features on their own whims without specifying what those features actually were. Not knowing what he was referring to became quite frustrating at times.

Even with the occasional vagueness, other discussions were satisfyingly to the point, like whenever the client-server architecture of NT came up:
Time and again, Cutler had hoped to dispel doubts about client-server. In his design, the kernel code treated the entire graphical portion of the operating system, including the Windows personality, as an application. It was a classic design choice. Client-server ensured reliability but degraded performance. It was probably Cutler's most momentous decision.
The performance hit incurred with the client-server model was a constant issue during the development of NT, and it wasn't until near the end of the project, and after a year delay, that the performance was brought under control and near parity with Windows 3.1. The story of how Cutler's team achieved the necessary performance while fixing the innumerable bugs as NT came closer and closer to release was one of the best threads of the book.

The book is also riddled with pieces of advice on software development, most often in the form of little narratives about different aspects of the project and a vast array of the programmers and testers that worked on it. Things like adding programmers to a late project makes it later, working longer hours is counterproductive, first make it right then make it fast, the number of bugs in a system is unknowable, and automated testing and stress tests improve code quality all appeared at various points in the story. It was enjoyable to see all of these hard-won nuggets of wisdom come up and be acknowledged during the course of such a high-profile project.

Sometimes the words of wisdom were quite humorous, too. At one point Cutler had written an email that included this gem: "If you don't put [bugs] in, you don't have to find them and take them out!" Well, yes, that's great. If only it were that easy! Of course he was trying to encourage his programmers to be more diligent and rigorous, but what a way to say it.

Throughout the book, new people were continuously introduced, each with their own mini-narratives told within the larger context of the NT project. It was nice to learn about so many different people that had a hand in the project, and there were dozens of stories related of the approximately 250 people that helped NT over the finish line, but it became exhausting to keep track of everyone as the names kept piling on. The number of people became pretty overwhelming even though only a small fraction of them made it into the book.

The scope and accomplishment that is Windows NT is quite astounding. Nothing like it had ever been done before, and the scale of the project was beyond anything achieved in software development up to that point. The scale of development wouldn't be surpassed until Windows 2000, seven years later. Even with the rough edges and occasional frustrations, the story of how NT was built was a fascinating and entertaining read. I would definitely recommend giving it a read if you're at all interested in how Microsoft managed to revolutionize its Windows operating system.

20 March, 2020

Movie Reviews: Star Wars 8: The Last Jedi (Spoilers), Battle Of The Sexes, Wonder, Coco

See all of my movie reviews.

Battle of the Sexes: It feels like forever since I've seen a movie with real, engaging three-dimensional characters, instead of the one or zero dimensional characters you get in Disney and Marvel movies.

The story starts with some background on Bobby Riggs and Billie Jean King. Riggs is an older former champion tennis player, a sexist but talented socialite, who is having difficulty with his family and looking for a new challenge. King is young and at or near the top in women's tennis, but disgusted that, while women's tennis draws the same ticket sales, the athletes get paid 1/8 what the men do, "because". So she starts her own league. Riggs challenges King to a battle of the sexes.

The trailers for this movie made it seem like Steve Carrell's Bobby Riggs was going to be a caricature of the real Riggs (who was certainly flamboyant). Thank goodness, Carrell, and his screenwriter and director, do a fantastic job in giving us a fully-fledged person that we can care about, even as he is, essentially, the bad guy. So, sucky trailer. Emma Stone does an equally fantastic job as Billie Jean King, as do several of the accessory and side characters, who are fleshed out in full glory (or at least as much as their screen-time allows).

The story lingered perhaps a little too long here and there on some scenes, like the initial haircut scene where she falls for her hairdresser (Carol did a better job with its similar love at first meeting scene). And maybe a little more time could have been added to the story to make it feel like a real epic. But never mind. This was a fun, fine, and satisfying movie to watch.

Wonder: From the trailer I wasn't expecting much for this movie, and in fact wasn't planning to see it at all. It seemed like a straightforward movie about a disfigured boy (Jacob Tremblay) being bullied in school, making and losing friends, and ultimately triumphing. Ho hum. So, once again, sucky, sucky trailer.

That story is, indeed, the backbone of the movie, taking up around 50% of the screen-time; if it was all there was to the movie, the movie would be as expected: not bad, but ultimately nothing special and predictable. But the movie spends the other 50% of its screen-time telling other people's stories, sometimes rolling back the same scene multiple times to view it from different points of view. We spend a lot of time with the sister, but also the mother, the sister's friend, the sister's boyfriend, and two other kids in the boy's class. And all of those stories are better and more original than the main storyline, making the movie so much more than just a story about a bulled boy.

The story is screenwritten by Steve Chbotsky (based on a book by RJ Palacio), the same screenwriter and author of The Perks of Being a Wallflower. I saw and loved that movie and wanted to read the book afterwards. The same thing happened with this movie: the movie is good, but you can see the left-out parts of the book peeking about here and there, and you really want to get more into depth with the characters.

Yes, the story is still a bit of a tearjerker, sentimental and emotional, but it is also narratively creative with some interesting, less predictable characters and story arcs. The main, predictable arc (basically told in the trailer) is raised up by being interwoven with the other stories, although it, too should have been better. Well worth a see, especially for kids and teens. Note: Chewbacca is in the movie, which makes it a candidate as an entry in the Star Wars canon, in my opinion.

Coco: Coco follows in the tradition of Moana, Brave, and Mulan in presenting not only a story of a hero's journey but a journey that is kickstarted, guided, and resolved in consonance with the literalization of a non-American cultural mythology. And I don't know how I feel about that.

A Mexican boy's (Manuel) family refuses to have anything to do with music because the great-grandfather ran off to become a musician, leaving his wife and child to fend for themselves. Naturally, Manuel wants to be a musician. It is the Day of the Dead, where everyone puts up pictures to the dead in order for the dead spirits to be able to (spiritually) visit, but of course a) there is no picture of the great-grandfather and b) Manuel doesn't want to have anything to do with his family. Manuel's idol is a famous musician, and Manuel learns, by accident, that this famous musician was, in fact, his great-grandfather. To compete in a music contest, Manuel steals a guitar from this musician's shrine and finds himself cursed into the land of the dead. Who are happily visiting the relatives who have posted pictures for them. The ones whose families have not posted pictures of them are unhappy. Manuel needs his dead family's blessing to get back to the real world, but they won't give it to him unless he promises not to pursue music. So he runs off to find the spirit of his great-grandfather.

Many of the themes, including the central theme, are reminiscent of the ones in the other movies I mentioned, and the movie also borrows some narrative elements from Up. It has a lot of "learning moments", which are familiar, and a few nice musical scenes. It leans heavy on appreciating your cultural heritage, by turning mythological aspects into real ones.

Which I find kind of bothersome. When mythology becomes fact, it is no longer a question of faith or practice or choice. While in real life there is no easy answer as to whether choosing to honor or not your dead ancestors makes you a good or bad person, movies like this imply that you have no choice not to believe in your family's traditional stories: If you don't, you are murdering or causing tremendous pain to actual beings who walk, talk, and feel exactly like any other living beings do. I'm not comfortable with that message. A mature individual recognizes that what we do to honor the dead and our traditions has nothing to do with the dead, but is about ourselves, our families, and our communities. Coco is aimed at children, sure, and this is just a children's story. But I thought that this movie was supposed to be sensitive to the cultures it was representing, not trivializing to them. You can't really have it both ways.

There are no glaring flaws with the movie, although a Mexican family rejecting all music for several generations seems a bit of a stretch. The movie is filled with pretty art, colors, and architecture which I presume represent both historical and modern Mexican culture. I'm not sure that modern children will appreciate the music, except the few numbers that are obviously meant to appeal to them. I'm not sure in what time period the movie is supposed to be; it must be modern, but no one has cellphones or computers. Is that normal for a modern, large Mexican town? Anyway, I liked it more than I did Moana, which I found derivative and boring. I'm sure that kids will enjoy it.

Star Wars 8: The Last Jedi: Star Wars once had something that was different from other sci-fi movies and worlds, something precious and important. Unfortunately, the makers of the current movies don't see that. Instead of making Star Wars movies, they are making modern sci-fi movies indistinguishable from other modern sci fi movies, with the iconography of Star Wars. Which is very painful to me. Chris Bateman bemoaned something similar after watching the Star Trek reboot, and I didn't get it, then. I think I get it now.

Update: see the end for thoughts after a second viewing.

The new Star Trek movies, the X-Men movies, the Marvel movies, the Ghost in the Shell remake, the Blade Runner movie, Looper, Valerian, Avatar, DC's movies, and many other sci-fi movies in the last 10 or 15 years  have a vast similarity to each other, in much the same way that all modern Disney, Pixar, and other American animated children's movie have vast similarities to each other. They may have different writers, directors, and casts, but they are all, essentially, dumbed down. The creators of these movies avoid complex messages, plots, and themes, throw in snarky slapstick between action sequences, fill the screen with copious action sequences at nearly the same points in the movie, present emotions and dialog that is one-dimensional and transparently representative of the characters, and hammer you with neat and simplistic moral messages in their denouements that are understandable and suitable for a 4 year old. Family is good. Be brave. Be true to yourself. Be loving to creatures, the natives, and the environment.

Star Wars 4-6 and 1-3 were not like that, at all. Well, okay, they often had one-dimensional emotions and dialog, but otherwise. Star Wars did not have tons of snarky dialog, except for Leia, and hers was not slapstick snark but a very specific kind of frustration snark. A Star Wars movie took itself seriously, because the movie was about space opera and adventure, not about instant entertainment. The message about choosing the good side of the force was given, not saved as a discovery for the end of the movie. The dark side of the force and the light side of the force were about our moral choices: people could contain both of these powers, but choosing light meant - by definition - choosing good, while choosing dark meant choosing to be selfish, and therefore evil. People could be ambiguous, but there were clear moral choices. Heroism was heroism: choose good and act on it. Every movie felt like it was part of a world that extended well before and after the movie: what you were seeing was a small part of a great epic, because the movie took time to show and make you feel time passing: Luke's daily routine on the farm represented years, his efforts on Dagobah months. The force presented an exploration of mysticism, not just firepower or "lifting rocks". The movies were NOT just sci fi movies with cool weapons and critters; they were NOT Guardians of the Galaxy, which is a close movie in structure, but just as far in feel as all the others.

The came The Force Awakens. The Force Awakens struck an iffy balance between Star Wars ala Lucas and modern sci fi movies. It felt, at times, too much like a Marvel movie. It was missing a lot of the feel of the Star Wars epic and the mysticism, it felt less like an epic and more like a sequence of events. But the characters, especially Rey, were compelling and the structure was well done, so I had hope it might move in the right direction after the makers received feedback from the fans.

Here be some spoilers, but nothing major.

This movie felt like a Star Trek movie with bits of Star Wars thrown onto it. For the first 25 minutes of the movie, I was in pain, holding my head in my hands aghast at the vast empty, non-Star Wars feel to the movie. Then we got to Rey and Luke, and it was filled with snarky scenes that were supposed to be funny, and I felt my stomach drop. It was supposed to be funny that Luke casually tossed the light saber over his shoulder? Really? It wasn't funny AT ALL, not only because it wasn't funny, but because it wasn't what Luke would do, even if he were disgusted by the force and everything it stood for. He would throw it away in disgust, perhaps, or at least show some emotional acknowledgement that this was his saber he had lost. Or ask some questions of Rey. Anything! The scene was a disaster, and I began to get a headache.

The main part of the movie is dull, with an hour long chase scene where nothing of consequence happens. Poe and Finn basically accomplish nothing in the entire movie. Instead, the entire enterprise of heroism is called into question, because, as one character puts it, we don't kill what we hate, we save what we love? What??? So heroes aren't heroes? It is implied not only that people can have both dark and light in them, but that dark isn't maybe so evil and light ins't maybe so good! What??? That destroys the entire freakin' metaphor! I don't want another vague morality movie that tells me that morality is relative. I don't want a treatise on how heroes aren't heroes, because they should follow orders. And I don't need a new lecture on how both sides are just as bad, and another on how we shouldn't treat animals badly (seriously, the movie took about twenty minutes of run time to tell us this).

The scene on the casino was a phenomenal waste of time; maybe it was supposed to be funny, but it wasn't, and it wasn't Star Wars funny. Even the pod race in TPM made more sense and had more meaning than this. And then we have a scene with Ren gratuitously without his shirt, a callback to the underwear scene in Star Trek Into Darkness. The whole movie takes place over what? Three days? So no story development. Please repeat after me: a character learning something isn't character development. It's just learning. Marvel characters learn things, too, but that doesn't make them less cartoonish. Development takes introspection, depth, complexity, time, and sensitivity.

So yeah, I had problems. Not only in the first 25 minutes, but many times after.

However .... admittedly after the first 25 minutes, some of the scenes were really great, and even really Star Wars great. The Rey-before-Snope and the lightsaber battle afterwards were beautiful, because of the shifting nature of the alliance and the confusion that the characters felt in the process. And the battle over the salt fields with the red plumes were a beautiful thing to see. I liked the dynamic between Ren and Rey, and the Luke and Ren scene, too. I liked Rose, but I didn't like most of the scenes she was in. I hated the multiple BB-ex-machina scenes, even more than I disliked the C3PO nuisance scenes in ESB.

Seen from the non-Star War perspective, the movie dragged in several scenes in the middle, but it was at least as entertaining as any other modern sci fi movie, and better because of the interesting characters of Rey and Ren. But I despair about the future of the franchise. With the exception of certain threads and scenes, these are not Star Wars movies, and for that I mourn. I like these threads and scenes; I want them to be in better, far different movies.

Also ... more spoilers ...

Callbacks: So many scenes were callbacks to TESB and TRotJ: training the Jedi, including entering the "dark side" cave, Rey giving herself up to Ren to be taken before the emperor and snatching up the lightsaber, and others. The resistance flying head on into the marching first order elephant things. And, admittedly, ESB spent mosy of its time simply chasing after the Millennium Falcon.

Things I didn't have a problem with that others might: The above callbacks. The changes in the force, such as the mindlink and the projection. Yes, it's odd that previous generations of Jedi never did these things, but they seem like the kinds of things that they would do, and I'm cool with that. This includes the water actually traveling through the mindlink and that Luke projected an image was of his younger self.

Other minor problems: If this takes place only days after the last movie, how could the republic and/or first order be in any kind of different state than it was in the last one? What happened to the galaxy? Why do they keep calling them rebels, instead of the resistance? Pick one. Since when do bombs fall in space when you release them? Fall which direction? What happened to Snoke insisting on training Ren? Or Rey? What the hell was Snoke? He shows up larger than life, he seems to be stronger than the emperor, and then he just dies? Why didn't the new admiral Holdo just tell Poe what the plan was, instead of waiting until the evacuation? Why did she wait until nearly everyone was dead before light-speeding her ship into the enemy? If that's a thing, can't you rig a bunch of ships to do that and decimate your enemies more frequently

Update: Having now seen the movie a second time, my thoughts are adjusting a bit. The parts that I disliked the first time I dislike now even more: in particular the comedy and the BB8 scenes, which are as annoying as Jar Jar but take up even more screen time. There is a difference between conversational humor, which I can enjoy, and slapstick humor directed at the audience, which I don't. I'm further down on the arrangement of scenes and the pacing. I don't like any scenes with Hux. I don't like the plot about, or even the idea that, spaceships run out of fuel in this universe. I still don't like how the director taunts the audience by not paying off stories about Rey's parents, Snoke, the R2D2 map, Chewbacca's grief, and other things.

The parts that I liked before I like even more, which is also what happened to me with TFA. However, after the second viewing,  I'm feeling a bit better about the neutral parts of the story. I don't LIKE the story - both the good and the bad guys throw away the past, Finn and Poe are reigned in as heroes instead of being heroic - but I'm okay with that being the story.

19 March, 2020

(270 MB) Download Hitman 4 Blood Money Highly Compressed For Pc

(270 MB) Download Hitman 4 Blood Money Highly Compressed For Pc


Screenshot



Hitman 4 Blood Money System Requirements

Following are the minimum system requirements of Hitman 4 Blood Money.
  1. Operating  system: Windows XP, Vista, Windows 7, Windows 8 and 8.1
  2. Processor: Core 2 Duo
  3. Setup Size: 270 MB
  4. Ram: 1GB
  5. Hard disk space: 5 GB







VPN Deal: 73% Off And A Cloud Storage Freebie With This Limited Time Offer - TechRadar

VPN deal: 73% off and a cloud storage freebie with this limited time offer

For The Glory Of... Austro-Hungary?

I picked up some Austro-Hungarian Aeronef cheap at the start of the year on eBay. My buddy Matt and I intend on playing some games with them. He has, in fact, procured the age old enemies of the Austro-Hungarians, the Japanese. We're likely going to bash a few rule sets together into something that's quick and fun.

Austro-Hungarian Aeronef Lussin class Rocket Patrol Nef

I've got a few more things left to build (battleships, fixed wings and a carrier) but this is the lion's share of them. Just a simple base, wash and drybrush. I've got a few details left to do but I don't think I'm going to go full orange Eldar on these.

16 March, 2020

We Are Moving!

The end of an era is here. For 10 long years Frictional Games has used this blog for news about the games, hiring posts, and most importantly tips on tech and design.


After much consideration we have voted in favour of creating a more streamlined Frictional Games experience. In non-corporate talk that means that we have one website, and everything can easily be found on that one website.


Fear not, no information has been lost in the process! On the contrary, as the old posts have been transferred over, all the broken links and images have been fixed or removed.


Thank you Blogger – and thanks to every fan who has read, shared and commented. See you on our new website!



15 March, 2020

Super Mario 64 (N64)

Hey, welcome back, it's Super Adventures 9th birthday etc. But never mind that, I've got TERRIBLE NEWS for you. Some quirk of Blogger has retroactively screwed up all my damn 256 colour images, removing shades and leaving them more dithered than they should be.


It only ruined little bits of them, only a few of the colours, but ideally you want your screenshots to be 0% ruined.

So I've got GOOD NEWS for you: mecha-neko wrote a thing and I did a thing and over Christmas we replaced something like 14,000 images over 1000 posts. So now the site is entirely fixed... or mostly broken, or somewhere in between. Why not click a few old posts and find out! I mean after reading this one.

Super Mario 64 Title screen logo pal europe
Developer:Nintendo|Release Date:1997 (1996 in Japan + US)|Systems:N64, DS, iQue Player

This week on Super Adventures, it's Super Mario 64!

It's a game that needs no introduction, so instead I'll start off by talking about how much I hate 3D platformers. Actually I don't hate them, as long as they keep their distance and don't bother me, but they've never been my genre. I like 2D platformers, I like games where you wander around in 3D, but somehow when you combine the two I lose interest. Maybe it's because I don't like slipping off narrow platforms and misjudging depth.

Actually I will give the game a bit of an introduction, because I like trivia. Super Mario 64 was designed by pioneering Nintendo game genius Shigeru Miyamoto, who's been making Marios since the first Donkey Kong arcade cabinet. He'd already set the template for the 2D platformer genre with Super Mario Bros. so they were hoping he could pull off the same trick in 3D. And he did... though he took a few months longer than planned. Unfortunately Mario 64 was meant to be the big launch title that got people buying the Nintendo 64, so they had to delay the console for months as well. They probably made the right choice though, as the PlayStation and Saturn were well established even before the delay and the N64 needed to show off some actual magic to lure people over to a cartridge-based machine without videos, voices or CD music.

Personally I love the N64 and I've got a lot of nostalgia for it, but Mario 64 not so much. I've maybe played the game twice and the furthest I've gotten is the stone slab boss that falls on you. But some people seem to like it, and it's "acclaimed as one of the greatest video games of all time", so I'm going to give it another few hours to win me over.

Read on »

05 March, 2020

About Hyper Casual Games

In 2014, I wrote a post titled "Casual games for casual players", analyzing important features a good casual game must have. This category of games had a boom with the rise of mobile media (smartphones and tablets). Probably the most iconic case that we can discuss here is the Angry Birds phenomenon: a beautiful game with rules you can understand in a second, a high level of replay, and available for a cheap price. Angry Birds became a model in the app stores and after that we could observe a great number of casual games that explored different business models using these simple mechanics.



We have many casual games in different platforms today, but there's a new idea rising strongly: the hyper casual games concept. These categories of games, according to Johannes Heinze are "games that are lightweight and instantly playable". Note the difference: the hyper casual are instantly playable; this makes a big difference in today's gaming context.

Companies like Voodoo and Ketchapp Games (both French) are two good examples of how to explore business models using hyper casual games. They are creating very simple and addicting games. You play them and, if you like them, there's a possibility to buy a premium version of the game without ads, or you can play it and watch the ads.

One good example of this kind of game is the awesome Helix Jump (one of my favorites). Check the gameplay trailer below:



Here in Brazil, companies like Sioux are investing in this gaming category. They launched a very interesting title named Overjump. Do the exercise: watch the video and notice that in the first 8 seconds you already understand the mechanics.



The most important point of this discussion is the rising of hyper casual games parallel to a big triple A titles showing us that we are living a great moment in the gaming industry: a moment full of opportunities.

#GoGamers

Episode 35: My Kingdom For An App Is Live!

Ep 35: My Kingdom for an App is live!

https://soundcloud.com/user-989538417/episode-35-my-kingdom-for-an-app

Adam Loper and I talk about Tabletop Minions and finding opponents for your games.

Join the conversation at https://theveteranwargamer.blogspot.com, email theveteranwargamer@gmail.com, Twitter @veteranwargamer

Follow Adam and the Game For app on Twitter! @tabletopminions @iamgamefor

Game For app for iOS and Android https://iamgamefor.com/

Tabletop Minions Expo https://tabletopminions.org/tmx/ June 9th-10th, 2018

Try Audible for your free audiobook credit by going to http://audibletrial.com/tvwg

Tabletop Minions Youtube Channel https://www.youtube.com/user/tabletopminions

Tabletop Minions Facebook Page https://www.facebook.com/tabletopminions/

Tabletop Minions Paint Showcase Club Facebook Group https://www.facebook.com/groups/236901433338119/

Sam Lenz blog http://samsonminis.blogspot.com/

GenCon http://www.gencon.com/

Adepticon http://www.adepticon.org/

MOHISTORY show at Ft. Leonard Wood, MO. https://www.eventbrite.com/e/mohistory-tickets-41577851473

Music courtesy bensound.com. Recorded with zencastr.com. Edited with Audacity. Make your town beautiful; get a haircut.

And The Streak Continues!

What's going on everyone!?


Today for the #2019gameaday challenge I played a solo game of Colt Express and didn't do so well. 

As each round went on I would feel like I got this. 

Then I would worry that I hadnt.

And by the time the game was over I placed 3rd unfortunately.  But the game was still fun!

As always, thank you for reading and don't forget to stop and smell the meeples! :)

-Tim

04 March, 2020

Atomic Ed, Short Film, Review And Interview


As the synopsis points out, Atomic Ed is about the underdog becoming the person they need to be for the situation. It is a fun-filled short ride that makes you smile, even if you might get a little squeamish because it is in a horror setting.

I saw Atomic Ed at the 2019 FilmQuest film festival (website). It was nominated for Best Foreign Short, Best Ensemble Cast, Best Score, and Best Makeup.

This is a light horror setting that doesn't reach the gore level of recent television shows. It's a family friendly story everyone can enjoy.

Synopsis: When the body of one of the members of Mark's band is found horribly mutilated, the gang lash out on Ed, who has no choice but to become the person he has always dreamed of being.

The director, Nicolas Hugon, shared some information how his youth in Paris inspired him for Atomic Ed and being a filmmaker.

What was the inspiration for Atomic Ed?

I grew up with my friend writer Cyril Delouche in a suburban suburb near Paris (we also shot the film in the neighborhood of my childhood). At that time, we were watching a lot of horror movies, mostly American. And often, they took place in neighborhoods quite similar to ours.

I think that with the passing of time, my memories of youth have ended up mixing with the images of horror movies that we consume in high doses!

Atomic Ed is a tribute to all these films and my youth.

There is indeed a lot of my experience in Atomic Ed. Already, the alleyways you can see in Atomic Ed are the same ones I have walked with my mates for much of my youth.

After, of course, there is this fantasy a little cliché of the teenager in love with the girl inaccessible and finally arrives at his ends.

Me, I did not arrive, but I was not beautiful as Oscar (who plays Ed in the film)!

What project(s) do you have coming up you're excited about?

Like all the filmmakers, I would like to shoot a feature movie one day of course!

I'm already trying to shoot a new short film by doing better than the previous one.

And maybe, other projects but it's a secret for the moment!

What was your early inspiration for pursuing a career in film?

I grew up in the 80s and like all children of my age I was amazed by all the movies of this era Spielberg/Lucas/Zemekis. Films where the marvelous arose in the everyday life of teenagers. I think about The Goonies, Gremlins, Back to the Future. But also, the first Star Wars.

At the time, I did not even ask myself the question of how we made movies, I let myself be transported and then that's all. Then, I think I needed more and stronger emotions and I really became passionate about genre cinema.

I was traumatized by films like Robocop, The Exorcist, or Brain Dead that I discovered very young and that's when I really wondered how these people make movies. So, I watched the movie with another, more technical look, and then one day my dad bought a camcorder to shoot family movies. I started like that when I was 12, shooting horror movies in my parents' house and garden, splashing my friends with a liter of ketchup!

What would be your dream project?

This one, I have not dreamed of it yet!

I already dream of continuing to do what I do, I still have a lot to improve.

And maybe start shooting movies a little bit longer!

What are some of your favorite pastimes when not working on a movie?
Cinema is a very time-consuming activity that tends to intrude much on privacy. When I do not make a film, I look a lot, I also discuss a lot with my friends about cinema. But I also find time to read, to see my friends, to play video games and to take care of my wife and my son.

What is one of your favorite movies and why?

Robocop of Paul Verhoven. This film, as I said earlier, traumatized me when I saw it when I was barely 10 years old. All this graphic violence, I did not feel well. Then, with time, he fascinated me, I discovered the second degree and the double reading that was hidden behind this film, which seems really nagging.

Since then, I watch it very often, for me it's a perfect film in many ways: the clarity of the screenplay, the rhythm, the structure of the film, the special effects, the emotions it summons to me.

This is the movie I would have dreamed of doing!

You can watch the trailer for Atomic Ed on Vimeo (link).

Find out more about Atomic Ed on

IMDb (link)

Facebook (link)

Instagram (link)

I'm working at keeping my material free of subscription charges by supplementing costs by being an Amazon Associate and having advertising appear. I earn a fee when people make purchases of qualified products from Amazon when they enter the site from a link on Guild Master Gaming and when people click on an ad. If you do either, thank you.

If you have a comment, suggestion, or critique please leave a comment here or send an email to guildmastergaming@gmail.com.

I have articles being published by others and you can find most of them on Guild Master Gaming on Facebookand Twitter(@GuildMstrGmng).