ဧည္႔စရင္း


hit counter

Monday, February 24, 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







Sunday, February 23, 2020

Tekken 6 PC




Minimum System Requirements


Operation System: Windows XP SP 3/Vista/7/8
CPU: Pentium 4
Processor: 2.6GHz or AMD Athlon 2600+
RAM Memory: 1 GB
Graphics Card: 256 MB with Pixel Shader 3.0+ (Required)
Hard Drive Space: 14 GB
Sound Card: Windows Direct X 9.0 Compatible
DirectX: Version 9.0


Recommended System Requirements


Operation System: Windows XP SP 3/Vista/7/8
CPU: Pentium 4
Processor: Core 2 Duo 2.4GHz 
RAM Memory: 2 GB
Graphics Card: 512 MB with Pixel Shader 3.0 (Required)
Hard Drive Space: 14 GB
Sound Card: Windows Direct X 1.0 Compatible
DirectX: Version 10.0


Download PPSSPP Emulator For PC Here



Download The Game ISO File Here

How To Download And Play Tekken 6 On PC (With Proof) [Voice Tutorial]


Thursday, February 20, 2020

Realms Of Arkania: Blade Of Destiny: Summary And Rating

        
Realms of Arkania: Blade of Destiny
Germany
Released in Germany as Das Schwarze Auge: Die Schicksalsklinge
attic Entertainment Software (developer); Fantasy Productions (German publisher); Sir-Tech (U.S. Publisher)
Released 1992 for DOS, 1993 for Amiga
Date Started: 13 November 2019
Date Ended: 7 February 2020
Total Hours: 38
Difficulty: Moderate-Hard (3.5/5)
Final Rating: (To come later)
Ranking at Time of Posting: (To come later)

Summary:

First in a lineage based on the German tabletop RPG Das Schwarze Auge, Blade of Destiny is a gem waiting to be cut and polished. A party of six, comprising familiar races but original classes, stops a horde of orcs from razing the city of Thorwal by finding a legendary sword that defeated the orcs in the past. In an effort to offer a computer game that adhered closely to tabletop rules and gaming style, Blade perhaps errs too much towards obtuse statistics, lengthy character creation and leveling, myriad spells, and exhausting tactical combat. Yet the developers managed to create a large, open game world and populate it with interesting encounters of a variety of length and difficulty, thus feeling a lot like a series of tabletop modules. Nothing in the game--first-person exploration (in Bard's Tale style, but with an interface drawn from Might and Magic III), paper-doll inventories (looking a lot like Eye of the Beholder), axonometric combat (clearly inspired by SSI), dozens of skills and spell skills--works badly, but almost every part of the game needed a little tweaking, editing, or tightening. I enjoyed it more as I became more familiar with its conventions, and it left me looking forward to its next installment.

****
      
I grew to enjoy Blade of Destiny more as the hour grew later (the opposite of what usually happens), although the game never really did manage to solve some of its early weaknesses. In the end, I'm struck at how much it reminds me of Pool of Radiance, the first attempt at a serious adaptation of another tabletop system. Both feature the standard party of six. In neither game do the party members have a direct, personal connection to the main quest. In both, the main quest is somewhat low-key--the fate of a city versus the fate of the world. Both keep character leveling in the single digits, and both err towards keeping faith with their tabletop roots, even when it might have been best for the computer game to improvise a bit.

I don't know whether to blame Das Schwarze Auge or the computer game for my chief complaints, most of which can be rolled up into three words: combat is exhausting. Combat is a major part of any RPG, so you don't want your players doing things like reloading to avoid it, which I did a lot. I abandoned entire dungeons because I was sick of all the fighting, so it's a good thing I didn't need an extra character level to win. The primary issues are:
           
  • The axonometric perspective doesn't work well for combat. It's hard to separate the characters and enemies from each other and particularly hard to move to a specific tile.
  • Everyone misses too often.
  • Attacks don't cause enough damage.
  • Spells, which would make the whole thing go faster, eat up so many magic points that you can rarely cast more than three or four before needing multiple nights' rest to recharge.
         
In light of these things, the "quick combat" system was a good idea. Unfortunately, combat is hard enough (at least until the end) that you can't really use it until there are only a couple enemies left. Even then, quick combat isn't really "quick." (To be fair, I guess they don't call it that; it's something like "Computer Fight.") You still have to watch the computer take all the actions and monitor your characters' status. It just means you can watch a television show at the same time.
           
If you can make out individual characters in those blobs, your eyesight is better than mine.
         
The spell issue had more consequences than just a difficult combat experience. The developers took the time to put several dozen spells into the game, and I never used more than about 5 of them. I kept meaning to find a good place to save near a known combat and then just keep reloading and experimenting, but I never identified an ideal position for this. Most of them would have failed anyway because the nature of the spell skill system means that you can't possibly specialize in more than half a dozen. When I play the sequel, it will absolutely be my priority to more fully investigate the spell catalog.

I had a few lingering questions after the last entry, such as what happens if you try to kill the orc champion with a weapon other than Grimring, and what happens if you don't honor the rule that only your champion fights. Unfortunately, the final save prompted me to overwrite the save game I'd taken just before the battle. My next-most recent save was from before exploring the orc caves and getting the message that led to the endgame. I'm not willing to do all of that again, so we'll have to leave it a mystery unless someone has some experience with it. But I was able to check out the alternate "bad" ending, which I would have experienced had I lingered for extra year in the quest. As I typed the rest of this entry, I had my party sleep at the inn for batches of 99 days until the game woke me up with the fateful message:
             
So the orcs are the "Vikings" of this setting.
            
Overall, I felt that the time constraint was generous enough that it wouldn't have impacted my approach even if I'd been more eager to explore every trail and sea lane. This is a good thing because there was quite a bit more to find. I took a look at a cluebook for the game, and among entire dungeons that I overlooked were a "wolf's lair" between Ottarje and Orvil, a six-level "ship of the dead" that I would have found if I'd taken more boat trips, and a three-level "dragon's hoard" on Runin Island. This latter location sounds like it would have been especially lucrative, with an option to do a side quest for the dragon and receive four magic items as a reward.

But I've always been fine with missing content. It's practically necessary in modern games, lest you exhaust yourself before the end. It also enhances a game's replayability. It's nice to see the number of titles with such optional content growing.

Let's give it the ol' GIMLET:

1. Game World. I didn't find the Nordic setting terribly original, but I enjoyed it just the same. The backstory is set up well, and as previously mentioned, I liked the low-key nature of the main plot. The main quest did a good job encouraging nonlinear exploration of the large world. The problem is that the game itself doesn't quite deliver on the backstory (or the tabletop setting in general). The various cities and towns are too interchangeable, the NPCs too bland. Score: 5.

2. Character Creation and Development. Well, I can't complain that it doesn't give you enough options. The leveling-up process in Blade of Destiny is probably the longest in any game to date. Not just longest, but most frustrating, with the caps on the number of times you can increase a particular skill per level (even if you neglected it in the early levels) and frequent failures as you try to increase. The caps in particular make it feel like the characters are never really getting stronger or better. (I think the final battle could be won by a Level 1 character.) Hit points and spell points, in particular, are almost imperceptibly slow to increase.
         
No, not now! I have an appointment in 90 minutes!
         
Still, I like the nature of character classes in the setting, including the use of "negative attributes" and the plethora of skills. I just wish I had a clearer sense of what skills, attributes, and negative attributes came into play in what circumstances, which bits of equipment compensated for them, and so on. The game text is obtuse enough that sometimes it's not even clear whether you succeeded or failed. When it is, it's almost always because you failed. Honestly, how high do I need to jack up my "Treat Wounds" skill before it has a greater than 50% chance of not making the character worse?

Back on the positive side, I think different party compositions would make a considerable difference in gameplay. I think you could have fun with some interesting combinations, like an all-dwarf party or an all-magician party. It's just too bad the different race/class templates didn't have more role-playing implications. Score: 5.

3. NPC Interaction. This was a really wasted area of the game. The developers give you the ability to talk to every bartender, innkeeper, smith, and cashier, but most of the dialogue is stupid when it isn't confusing. I'd blame the translation, but my German readers report that it was stupid and confusing even in German. The few dialogue options are either false options that lead to the same outcome or confusing ones with counter-intuitive results (e.g., asking to see the map makes the NPC give it to you; asking for the map makes him just show it to you). That said, you occasionally get an important hint from your various NPC interactions. I just wish it had been more consistent and that the developers had used the system to give more blood to the game world. Score: 4.
              
This conversation made no sense as a whole, and these individual responses made no sense in detail.
         
4. Encounters and Foes. The game shines, though sometimes with a marred finish, in this area. I really enjoyed the variety of encounters, some fixed, some random, that the party gets on the road and as it explores dungeons and towns. I like that some of them are a single screen, resolved instantly, and others lead you off on a multi-hour digression. In contrast to the dialogue, the text of these special encounters is usually evocative and interesting, and I can even forgive the occasional shaggy dog joke like the "wyvern" encounter. I just wish for a few more role-playing options in these encounters.
           
These diversions and side areas never stopped being fun.
           
Foes were mostly high-fantasy standards with similar strengths and weaknesses that we've seen in a thousand RPGs but at least they appeared in appropriate contexts. We've come a long way from the days when we were inexplicably attacked by parties of 6 orcs, 3 trolls, 2 magicians, and a griffon right in the middle of town. Score: 6.

5. Magic and Combat. Very mixed. I like the combat options, the variety of spells, and the turn-based mechanics. I just didn't like the execution, which was partly due to interface and partly due to the game rules. Either way, combat was generally a tedious, annoying process rather than the joyful one I typically find in, say, a Gold Box game. As for spells, the game really needs some in-game help to assist with them, perhaps annotating the spells in which each class is supposed to specialize. Every spellcasting session and every level-up was a long process of flipping through the manual. It's too bad because the spells are so varied and interesting on paper. Score: 4.
           
I only ever tried about 6 of these spells, which coincidentally is the number of spells I got above 0 in my ability to cast after 5 levels.
         
6. Equipment. Another disappointment. I like the approach to equipment, with a number of slots, but you get upgrades rarely and it's extremely hard to identify them when you do. This is something that perhaps no game has done very well up to this point. I don't mind if it's hard to identify a piece of equipment--if you need a special skill, or spell, or money, or whatever--but I mind if it's annoying. I mind if I have to swap the item around to multiple characters to try different things, especially when the interface makes swapping annoying and time-consuming. I mind when there's no symbol, color, or other mechanism to distinguish weapons and armor with different values. 

Blade offers perhaps the largest variety of "adventure" equipment that we've seen so far, which makes it all the more frustrating that either so much of it is useless, or the game doesn't bother to tell you when a piece of equipment has saved the day. Finally the encumbrance system is geared towards making most characters chronically over-encumbered. The ability to make potions is nice, but again the system is a little too complicated. Score: 4.

7. Economy. Blade almost perfectly emulates the Gold Box series here: money is plentiful from the first dungeon and you hardly have any reason to spend it. My party ended the game with well over 1,000 ducats. Even potions don't serve as a good "money sink" because they don't stack and you have the constant encumbrance issue. A rack of +1 weapons, the ability to pay to recharge spell points, or temple blessings that actually did something all would have been nice. Score: 3.
         
I just donated 999 crowns!
         
8. Quests. Generally positive. Blade is one of the few games of the era to understand side quests, and they sit alongside an interesting-enough main quest with multiple stages. It just needed a few more choices and alternate endings. Score: 5.

9. Graphics, Sound, and Interface. I know that some readers will defend the game here, but I found all three to be somewhat horrid. Graphics are perhaps the least so. Some of the cut scenes are nice. Regular exploration graphics aren't bad, but the inability to distinguish stores from regular houses is almost unforgivable. Combat graphics are a confusing mess from the axonometric perspective. Any virtues the sound effects may otherwise have are obscured by the jarring three-note cacophony that accompanies opening any menu. And there's no excuse for the interface, which occasionally gives some nods to the keyboard but really wants you to use the mouse throughout.

Aside from my usual complaints about mouse-driven interfaces, the game is full of all kinds of little annoyances. When you find or purchase a piece of equipment, it always goes to the first character. You've got to then go in and redistribute it. It's annoying to transfer equipment between characters, especially if one is over-encumbered. Messages often time out before you're done reading them, or pop up so quickly that you don't have time to read them before you accidentally hit the next movement key, making them disappear. There's a lot of inconsistency, particularly in dungeons, about when you need a contextual menu and when you need to use the buttons on the main interface. There are dozens of other things like this. The developers took the appearance of the Might and Magic III interface but none of its underlying grace.

The auto-map didn't suck. I'll give it that. Score: 2.

10. Gameplay. We can end on a positive note. This is one of the few open-world games of the era, and in between the opening screen and closing combat, it's almost entirely non-linear. The many things that a first-time player doesn't find makes it inherently replayable. And the length and difficulty are just about perfect for the era. I particularly love that you have to lose experience points to save (except at temples), which discourages save-scumming. Score: 8.
               
This NPC seems to think he's living hundreds of years in the past.
         
That gives us a subtotal final score of 46, a respectable total that would put it in the top 15% of games so far. But I'm going to administratively remove 2 more points for an issue that really isn't covered by my GIMLET: a lack of editing that created unnecessary confusion at numerous points in the game. There are numerous places that go unused, such as the tower and "Ottaskins" in Thorwal. NPCs frequently tell you things in dialogue that aren't true. There are numerous false leads on the map quest, and I don't think they're there to challenge you--I think the developers changed things and didn't update the dialogue. All of the NPCs in Phexcaer were clearly written for an earlier game in which the nature of the backstory and quest were quite different. It's common now, but relatively uncommon back then, to find a game released in what was clearly its "beta" stage.

So that gives us a final score of 44, which still puts the game in the top 15%. It had a lot of promise, and I'm sorry that the developers didn't find more time to tweak and tighten it.
            
This is not the sort of game for which you really want to emphasize "conversation."
         
Blade of Destiny wasn't released in the United States until 1993, so Scorpia didn't take it on until the October 1993 issue of Computer Gaming World. It's one of her more ornery reviews. After saying that the English translation of Das Schwarze Auge, "The Black Eye," "might be appropriate," she goes on to spoil the entire plot in the next paragraph, including the one-on-one combat at the end. She found the plot unoriginal and wasted three days trying to figure out how to find the orc cave, noting that there are no clues to be found anywhere. (Remember: I had to use a walkthrough for this.) She hated the failures when trying to level up, complaining that one of her fighters "made no advance in swords on two successive level gains." She noted a lot of discrepancies between the manual and actual gameplay, particularly in the area of spells, and she agrees with me that combat is a "tedious, frustrating, boring, long-drawn-out affair."

She liked the automap, the ability to reload in the middle of combat, and the extra experience you get the first time you face a particular monster. That was about it. I was surprised to see how much she hated the experience cost for saving. She says she wouldn't have minded if the creators had awarded a bonus for not saving, apparently seeing a difference there that I don't. 

But her worst vitriol was for a bug that I didn't experience: apparently, if you quit in the middle of the final battle, you get the victory screen anyway. "This is not just a scam; it is the Grand Canyon of scams," she sputters. "How did the 20+ playtesters manage to miss this one? If they didn't miss it, why wasn't it fixed?" In summary:
            
Those who worship at the mythical altar of Realism often end up sacrificing fun and playability on it. That is what happened with Blade of Destiny. In their attempt to make the game "like real life" (something few players want in the first place) the designers went overboard in the wrong direction more than once. I would not recommend Arkania to any game player, but I do recommend it to game designers as an example of what to avoid in their own products. Let us all hope we don't see another one like this any time soon.
             
Ouch. I don't disagree with the elements she didn't like, but I found more that I did like.

On the continent, the game had polarized reviews. Some thought that the designers went overboard in the right direction, or perhaps didn't go overboard, or perhaps only did it once. Whatever the case, the ASM reviewer (92/100) said that he'd "rarely seen a perfect implementation of an RPG that also remains really playable on the computer." PC Joker (90/100) said that it is "only surpassed by Ultima, leaving the rest of the genre competition far behind in terms of freedom of action and complexity." But not all German reviews were positive. PC Player (48/100) recommended that players "close your eyes, put the lid on, and wait for Star Trail."

(At least there were some positives in the reviews for the original game. A 2013 remake by German-based Crafty Studios came out to almost universally negative reviews despite improved graphics, voiced dialogue, and other trappings of the modern era. It was apparently quite unforgivably bugged. Crafty went on to remake Star Trail in 2017.)
             
Combat in the remake. At least you can identify the squares a bit easier.
         
The original game sold well despite a few bad reviews and certainly justified the two sequels, Realms of Arkania: Star Trail (1994) and Realms of Arkania: Shadows over Riva (1996). Together, the trilogy established the viability of Das Schwarze Auge setting, which continues to produce RPGs into the modern era, including The Dark Eye: Drakensang (2008), Deminicon (2013), and Blackguards (2014). Lead developer Guido Henkel would eventually tire of the setting, quit attic, move to the United States, join Black Isle studios, and produce Planescape: Torment.

I haven't attempted to reach out to Henkel, as his work on the Arkania series has been well-documented elsewhere. In his 2012 RPG Codex interview, he explains that the publisher of attic's Spirit of Adventure, StarByte, originally approached the company about creating a series based on Das Schwarze Auge, claiming they already had the rights. The attic personnel were reluctant to work with StarByte after a dreadful Spirit experience ("a horribly crooked company that cheated us and all of its other developers"), so they were delighted to find that the company had been lying about the license. attic managed to get it for themselves, although at such an expense that the three Arkania games barely made a profit despite selling well.

From a 1992 perspective, I would call Blade of Destiny "a good start." I look forward to seeing how things change in the sequels.

*****

B.A.T. II will be coming up next. For the next title on the "upcoming" list, we reach back to 1981 for Quest for Power, later renamed King Arthur's Heir. Come to think of it, the Crystalware titles are so similar and quick that I might try to cover Quest for Power and Sands of Mars in a single session so I can be done with 1981 entirely. Again.

Tech Book Face Off: Getting Clojure Vs. Learn Functional Programming With Elixir

Ever since I read Seven Languages in Seven Weeks and Seven More Languages in Seven Weeks, I've been wanting to dig into some of the languages covered by those books a bit more, and so I've selected a couple of books on two interesting functional languages: Clojure and Elixir. For Clojure I narrowed the options down to Getting Clojure by Russ Olsen, and for Elixir I went with Learn Functional Programming with Elixir by Ulisses Almeida. You may notice that, like the Seven in Seven books, both of these books are from The Pragmatic Programmers. They seem to pretty consistently publish solid, engaging programming books, and I was hoping to have more good luck with these two books. We'll see how they turned out.

Getting Clojure front coverVS.Learn Functional Programming With Elixir front cover

Getting Clojure

I remember thoroughly enjoying Russ Olsen's Eloquent Ruby years ago, so my expectations were already set for this book. Olsen did not disappoint. While Getting Clojure is an introductory programming language book instead of a guide on the idioms and best practices of the language, like Eloquent Ruby was, he brings the same clear, concise writing, and nails the right balance between covering the minutia and sketching an overall picture of Clojure without boring the reader to tears.

Programming books that aim to teach a language from front to back can easily fall into the trap of spending too much time on all of the gory details about the language's arithmetic and logic systems or every possible control structure. Maybe it's because Clojure is a simple and straightforward language that doesn't have the complications that other languages have in these areas, but this book was a very easy read through these normally tedious parts. Olsen assumes the reader is already a programmer with a couple languages under their belt, so he lays out the mundane facts in a succinct, orderly manner and moves on to the more interesting bits.

Chapters are short and evenly spaced, each focusing on one small part of Clojure, starting off with the basics of arithmetic, variables, data types, logic, functions, and namespaces. Each chapter has sections at the end for discussing how to stay out of trouble when using those language features and what those features look like in actual Clojure programs. After the basics he covers the more intermediate topics of sequences, destructuring, records, tests, and specs before finishing things up with inter-operating with Java, working with threads, promises, futures, and state, and exploring the power of macros. It's a logical order that flows nicely, with later chapters building on earlier material through a gentle learning curve. I never felt stuck or frustrated, and I could read through a few chapters in a sitting at a rapid pace. That's testament to excellent technical writing skills that allow an experienced reader to go through the book at speed.

One fascinating thing about this book, and I imagine every Clojure book, is how little time is spent explaining syntax. Clojure is a Lisp-style language, so syntax is kept to a minimum. What do I mean by that? Well, the basic syntax of Clojure is a function call, followed by its arguments, both wrapped in parentheses like so:

(println "Hello, World!")

Vectors are denoted with [] and maps follow the form of {:key1 value1 :key2 value2}. Nearly all of the code looks like this, just with more complicated nesting of functions. After learning the standard library functions, you know and understand about 90% of the language! The more advanced language features like promises and macros add some more syntactical sugar, but really, compared to C-style languages, Clojure's syntax is incredibly lightweight. Some programmers may hate all of the parentheses, and the prefix arithmetic notation takes some getting used to, but learning a language that's so consistent in its structure is enlightening.

Not only does Clojure have the elegance of a Lisp, but it also runs on the JVM so we have access to all of the Java libraries that have been built up over the last few decades. That may not always seem like a benefit, considering how convoluted some Java libraries are, but Clojure has its own great features that should take precedence over the uglier parts of Java while still being able to leverage all of the time-saving work that's been done already.

Plus, Clojure has made significant advances in modern concurrent programming, both through its inherent nature as a functional language with immutable data structures, and because of safe concurrent programming structures like promises and futures. As Olsen says about threads, "One of the things that makes programming such a challenge is that many of our sharpest tools are also our most dangerous weapons." If concurrency is anything, it's hard, but Clojure makes this increasingly important programming paradigm easier and safer, as long as you know how to use those sharp tools.

Olsen has done a great job of teaching the set of tools available in Clojure with this book, and beyond it being clear and well written, it was a fun read all the way through. I love learning new languages and the new programming tools that they reveal, especially when I can find a great field guide like this one to help me along the way. If you don't know Clojure and would like to learn, Getting Clojure is a highly recommended read.

Learn Functional Programming with Elixir

Like Clojure, I wanted to dig more deeply into Elixir after reading about it in Seven More Languages in Seven Weeks. This book showed some promise as a quick introduction to the language that would focus on the functional programming paradigm. I think the title is a bit of a misnomer, though, because it was more on the side of a quick introduction to Elixir, which just happens to be a functional language. Almeida did not go into too much detail about how to use the functional paradigm to greatest advantage, and instead stuck to the basics.

Spending time on the basics is fine, of course. It just wasn't what I was expecting. The book is split into seven chapters that cover a quick introduction of what Elixir looks like, variables and functions, pattern matching and control flow, recursion, higher-order functions (like each, map, and filter), an extended example text game, and impure functions. Notably missing from this list is anything having to do with concurrency and parallelism—Elixir's primary claim to fame, being that it runs on the Erlang VM. But this is a beginner's book, after all, and it keeps things pretty simple, although the pace is probably too fast and the explanations too short for someone who has never programmed before. This book is definitely meant for experienced programmers looking to get started with Elixir quickly.

In that respect, the book accomplishes its goal quite well. It presents all of the basic features of Elixir in a logical and succinct manner, covering all of the different syntax elements of the language without much ceremony. Elixir has its fair share of syntax, too, much more so than Clojure does. Whereas Clojure consists entirely of function calls, Elixir syntax is much more exotic:

max = fn
x1, x2 when x1 >= x2 -> x1
_, x2 -> x2
end
This is a simple function that returns the maximum of two numbers, but it shows some of the more extensive syntax of Elixir with pattern matching on the second and third lines, the when guard clause, the underscore used as a wildcard matcher, and the anonymous function declaration. When this function is called, if line 2 matches, including the guard clause such that x1 >= x2, then x1 is returned. Otherwise, line 3 will match automatically and x2 is returned. This is just a sampling of syntax, too. Things get even more involved with lists and maps and function arguments, all mixed in with pattern matching and pipes. This is a rich language, indeed.

The brief explanations of all of these language features tended to be a bit wanting. They were so clipped and simple that I was often left wondering if there wasn't much more to some of the features that I was missing. The writing style was abrupt and disjointed to the point of being robotic. Here is one example when discussing recursion:
Code must be expressive to be easier to maintain. Recursion with anonymous functions isn't straightforward, but it is possible. In Elixir, we can use the capturing feature to use named function references like anonymous functions:
Here's another example when describing the Enum module:
The Enum functions work like our homemade functions. The Enum module has many useful functions; it's easy to guess what they do from their names. Let's take a quick look:
This kind of writing just starts to grate on me because it has no natural flow to it. I would end up skimming over much of the explanations to try to pick out the relevant bits without feeling like I might be assimilated by the Borg.

Most of the code examples were forgettable as well. They did an adequate job of showing off the language features that they were meant to showcase, but they certainly didn't serve to inspire in any way. On the other hand, chapter 6 on the extended example of a text game was quite delightful. This chapter made up for most of those other faults, and made the book almost worthwhile.

In the example game, you code up a simple text-based dungeon crawler where you can pick a hero and move through a dungeon fighting monsters. It's an incredibly stripped down game, since it's developed in only about 35 pages, but it shows Elixir in a real application setting, using all of the language features that were introduced in the rest of the book. It was fun and illuminating, and I wish the rest of the book could have been done in the same way, explaining all of the Elixir syntax through one long code example.

Alas, it was not done that way, but even though the rest of the book was terse and didn't cover some of Elixir's more advanced features, it was still a decent read. It was short and to the point, making it useful for a programmer new to Elixir that needs to get going with the language right now. For anyone looking to learn Elixir more thoroughly, and maybe more enjoyably, you'll want to look somewhere else.


Of the two books, clearly Getting Clojure wins out over Learn Functional Programming With Elixir. Olsen showed once again how to write a programming book well, while the Elixir book was mechanical and insufficient. That's great if you're in the mood to learn Clojure, but what about Elixir? It's a fascinating language, but I'll have to look further to find a good book for learning the details.

The Ninja Saviors: Return Of The Warriors Review (PS4)

Written by Alexander O. Cuaycong and Anthony L. Cuaycong


Developer: NatsumeAtari
Publisher: ININ Games
Genre: Action, Arcade, Fighting
Price: $19.99
Also Available On: Switch



Back in the nineties, the two dimensional beat-'em-up genre was in its prime. Games like Golden Axe and Double Dragon found a niche in the fickle market by giving audiences fast, intense, action-packed experiences. Seeing the trend, Taito released Ninja Warriors on the Super Nintendo Entertainment System in 1994. For a port of a seven-year-old arcade offering, it held up well; in fact, it was praised for its tight controls, good pacing, and vibrant art style, all while cashing in on its ninja aesthetic. That said, no sequel was planned or made, effectively relegating it as a footnote in history.




Until now, that is. Ninja Warriors has made its way to modern consoles 25 years after its original release via The Ninja Saviors: Return of the Warriors, a remaster aimed at wowing a whole new generation of gamers. As with its source material, it focuses on control of one of three ninjas out to battle an evil regime existing in a dystopian timeline. And, as with its source material, it's extremely challenging, From the moment it's booted up, it presents crisp, redrawn graphics that belie just how much of the gameplay design remains unchanged. It looks like a 2019 release, but still plays like its 1994 self.




In The Ninja Saviors: Return of the Warriors, the opposition comes in large numbers, and aggressively so; enemies are a constant threat if underestimated, and can bring up a Game Over screen at a moment's notice. Powerups are fairly uncommon, thus making mistakes all but fatal, and the plentiful number of boss characters can prove to be Sisyphean hurdles even to veterans of the genre. On the flipside, the three playable characters have their own unique fighting styles and respond fluidly to commands; they are able to attack, block, and dodge at a moment's notice. Likewise, they can perform a variety of special moves through the consumption of a resource bar.




The Ninja Saviors: Return of the Warriors isn't overly long, but its replay value is enhanced by the uniqueness of the characters. In addition, it boasts of a cooperative feature that raises the fun factor. And while it does little to reinvent the genre, it plays so crisply and fluidly that even newcomers will appreciate its virtues.



THE GOOD:
  • Beautifully redrawn two-dimensional graphics
  • Smooth, crisp, fluid gameplay
  • Good replay value
  • Decent coop functions in place

THE BAD:
  • Fairly standard beat-'em-up
  • Can sometimes feel overly challenging and unfair
  • Relatively short, especially for the skilled


RATING: 7/10

Wednesday, February 19, 2020

DE: A Different Take On Wyches

I mean sure, why not?  Let's give these girls another try.

Maybe I have been going after this all wrong.  I've been thinking to myself for a while now:  How do I get Wyches into my army while still being effective.  Well, maybe with Succubi down to 54 points with an Agonizer, it's time to start bringing more HQs, in general, to make up for this loss?  What about Wyches?  Should I go big or go small with them?  If I go big with them, they certainly take advantage of their Obsession bonuses and Combat Drugs more, but they lose out on their ability to be easily transported by Raiders.  I feel that's a big loss because you need something that can reposition them when they need to around the battlefield without exposing them to enemy fire.

The more I think about it, the more I want to try MSU Wyches instead of running larger units of them.  My reasoning is this:
  • What do they really gain after they pass their min units really?  There's definitely more bodies to soak up during Overwatch, but that's about it.  It's only when they get to 10 do they get to take additional Wych weapons.  However, if you take 10, you can't really fit more in the Raider now, can you?
  • If you keep them in min units, not only do you fill out your Troop choices easier, but you can take more Agonizers and Blast Pistols in a squad.  For example, you can run 2x5 and get double the amount of Agonizers and Blast Pistols.  The only downside is that your drugs are going to be more dispersed.
  • For smaller units, it's really the HQs that do the most heavy lifting.  I guess you should start asking yourself what are you really using Wyches for?  IMO, the more competitive lists can kill MEQ just fine by shooting them to death, so what are you doing with them?  At this stage, I think we're just styling.

I think that kinda settles it:  I don't think Wych units are all that competitive, but they're not terrible either.  Reavers are some of the best units in the codex I think, but the Wyches themselves are decent at best.  Regardless, I think you can take a setup that is cheap enough, especially from an HQ perspective, that you can afford to take a Battalion for them if you're planning to use them in the first place.

Quick note:  I think Strife and Red Grief are the best for this.  They both have really nice Warlord Traits.  Strife gives you Blood Dancer and the 9-attack Succubus build with the Whip, whereas the Blood Glaive is just a fantastic weapon to have.  In general, I see +1A is very useful all around, especially with Agonizers because Strength doesn't matter for it and neither do Blast Pistols.  As always, I think anything that can Advance and Charge and re-roll the results of both after T2+ is just amazing.  I am definitely more inclined to take these two cults over Cursed Blade.

This is what I mean:

1990 // 10 CP
Black Heart Battalion +3 CP

HQ:
Archon, Agonizer, Blaster = 91
Warlord Trait: Cunning

Archon, Agonizer, Blaster = 91

TROOP:
10x Warriors, 2x Blaster, Dark Lance = 114
Raider, Dark Lance = 85
199

10x Warriors, 2x Blaster, Dark Lance = 114
Raider, Dark Lance = 85
199

10x Warriors, 2x Blaster, Dark Lance = 114
Raider, Dark Lance = 85
199

PARTY BUS:
Raider, Dark Lance = 85
Raider, Dark Lance = 85

+++

Black Heart Spearhead +1 CP

HQ:
Archon, Agonizer, Blaster = 91

FLYER:
Razorwing, 2x Dark Lance = 145
Razorwing, 2x Dark Lance = 145

HEAVY:
Ravager, 3x Dinsintegrators = 125
Ravager, 3x Dinsintegrators = 125
Ravager, 3x Dinsintegrators = 125

+++

Strife Battalion +3 CP

HQ:
Succubus, Adrenalight, Whip = 54
Warlord Trait: Blood Dancer

Succubus, Painbringer, Agonizer = 54

TROOP:
5x Wyches, Agonizer, BP, Shardnet = 59
5x Wyches, Agonizer, BP, Shardnet = 59
5x Wyches, Agonizer, BP, Shardnet = 59

>>>

Firepower:
12 Dark Lances at BS3+
9 Disintegrators at BS3+
6 Blasters at BS3+
3 Blasters at BS2+
3 Blast Pistols at BS3+
2 Razorwing Missiles at BS3+
25 Splinter Rifles at BS3+

Face it:  There's nothing that this list can do that the pure Kabal list can't do from a pure damage perspective.  Killing things at range is satisfying for sure, but killing them in close combat with some of the most ridiculous melee heroes in the game so far might be very worthwhile as well.

So what does deployment actually look like?  Well, the 2x5 unit of Wyches goes into a single Raider while all the Archons and Succubus pile into another Raider with the rest of the Wyches.  Yes, 3 Archons and 2 Succubus go into a Raider:  The beginning of every dirty film.

From there, you just treat the 2x5 unit as a single Raider unit while remembering that you will probably get murdered if you try assaulting before you Raider gets a chance to get in there first.  You charge in with the Raider, tie up whatever was trying to shoot your ass, and then run your naked girls in for some good damage with Agonizers.  Don't forget to bring you super killy Succubus along for the ride too.  The Archons can come if they want, but most of the time they will be running around the rest of the Kabal spreading good stuff 6" bubbles while totting Blaster fire down on your opponents.  However, always remember that they're not shy to getting their feet wet, so if you need them to take on a big unit of MEQ for whatever reason, hook them up with some Huskblades and throw them into the fray.

I'm just going to leave this list right here and let it marinate for a while.  This is just a theory list and I think it can do pretty decent.  One thing's for damn sure:  10 CP sure makes me happy.

Inclusivity And The Blue Hair (Tradecraft)

My store has a reputation for being an inclusive environment.

Much to my surprise.

You see, I haven't put up signs saying we're against hate or networked with the community to be more inclusive. I haven't sought out a more diverse staff or advertised in the Pink Pages. I don't have a particular store policy on inclusivity and I don't have any rules in my Game Center, as I think rules postings are only necessary when they're really, really necessary. History has shown only crazy people post rules (or make laws) when it's not necessary.

The reason why we have a reputation for inclusivity is we try really hard, now get your notebook out so you don't miss this, we try really hard not to be a dick.

When other people show intolerance, it's not a "he said, she said" issue. The intolerant person is shown the door. Because they're being a dick, not because of some political stance, rule or policy. Most of the time I'm not even there, as this activity happens in the evening hours during events. It's ingrained in the store culture, and staff are part of that culture. There's usually one trouble maker in every group (two in Magic).

As for hiring, I've realized inclusivity provides me a great opportunity to hire excellent people overlooked in a more conservative environment. I don't care about the color of your hair, your gender, your orientation, your identity, your race or even your politics, provided you can do the job well. I do want you to be clever, knowledgeable and customer service oriented. Because other hiring managers do care about all the superficial things, I often find diamonds in the rough. Note how selfish I am. Note that I am finding a competitive advantage and not making a political statement. I am not hiring lesser people to make a greater point. I am not being a good person, I'm just being self serving. Most importantly, I'm not being a dick. As with everything in the game trade, the bar is low.

I want to mention when I was doing research for my store in 2004, I visited the local comic shop, Flying Colors, with a friend. As we were leaving I mentioned, "Do I really want a life managing young people with blue hair?" That was what I saw at Flying Colors and being in the professional world, you would never see that. I had no experience with blue hair (my son later had blue hair for years) or really anyone who didn't file down their personality to fit into a corporate culture. I assumed blue hair meant trouble and weird problems and unpredictability, when in fact, blue hair meant opportunity. I really do want a life managing young people with blue hair.

This diversity grows the store and brings in a diverse crowd like I could not have imagined five to ten years ago. It's a hiring dividend, not the core value of the hire. The hobby has become mainstream. If you would have looked at my store a decade ago, it would have been the stereotypical "sausage fest" of all males, acting male, smelling male, being their stereotypical male selves and expressing their dumb ass stereotypical male opinions. I get it. You become so blinded by testosterone that you can't even smell the sweat or notice the pee on the seat. Testosterone in the air blurs the senses. That was the community, whether you liked the smell or not. For some stores that haven't adapted, this is still the community.

There was good and bad in that group, like any group, but it was an insular community, that repelled others, especially women. That is gone for the most part, or at least lessened. The hobby has spread rapidly and the customer base has expanded to all types of people and most importantly, we have been there with open arms. We didn't change, we just provided the open environment that allowed diversity to stream in, and the understanding that there will be no hostility or intolerance allowed.

Not everyone agreed. Not everyone went quietly. One edge lord threatened violence against me. As someone who's not a squishy liberal, and more libertarian (a liberal who returns fire), this had me a bit fired up. I will go down with the ship and take you with me. I bought a couple Louisville Sluggers, in case we wanted a little spontaneous staff batting practice. But like most cowards, they made a lot of threats, trolled me on the Internet for a while, and eventually disappeared.

In any case, there was no change needed for this transition, no Sluggers wielded, just an understanding we would make hard decisions to defend people who chose us as their home. If you're not a dick, how could you not? Embrace the blue hair. Blue hair is here to stay. If you really are a dick, embrace it anyway, for your bottom line. Fake it for the money.

Thursday, February 13, 2020

Brave Browser the Best privacy-focused Browser of 2019



Out of all the privacy-focused products and apps available on the market, Brave has been voted the best. Other winners of Product Hunt's Golden Kitty awards showed that there was a huge interest in privacy-enhancing products and apps such as chats, maps, and other collaboration tools.

An extremely productive year for Brave

Last year has been a pivotal one for the crypto industry, but few companies managed to see the kind of success Brave did. Almost every day of the year has been packed witch action, as the company managed to officially launch its browser, get its Basic Attention Token out, and onboard hundreds of thousands of verified publishers on its rewards platform.

Luckily, the effort Brave has been putting into its product hasn't gone unnoticed.

The company's revolutionary browser has been voted the best privacy-focused product of 2019, for which it received a Golden Kitty award. The awards, hosted by Product Hunt, were given to the most popular products across 23 different product categories.

Ryan Hoover, the founder of Product Hunt said:

"Our annual Golden Kitty awards celebrate all the great products that makers have launched throughout the year"

Brave's win is important for the company—with this year seeing the most user votes ever, it's a clear indicator of the browser's rapidly rising popularity.

Privacy and blockchain are the strongest forces in tech right now

If reaching 10 million monthly active users in December was Brave's crown achievement, then the Product Hunt award was the cherry on top.

The recognition Brave got from Product Hunt users shows that a market for privacy-focused apps is thriving. All of the apps and products that got a Golden Kitty award from Product Hunt users focused heavily on data protection. Everything from automatic investment apps and remote collaboration tools to smart home products emphasized their privacy.

AI and machine learning rose as another note-worthy trend, but blockchain seemed to be the most dominating force in app development. Blockchain-based messaging apps and maps were hugely popular with Product Hunt users, who seem to value innovation and security.

For those users, Brave is a perfect platform. The company's research and development team has recently debuted its privacy-preserving distributed VPN, which could potentially bring even more security to the user than its already existing Tor extension.

Brave's effort to revolutionize the advertising industry has also been recognized by some of the biggest names in publishing—major publications such as The Washington Post, The Guardian, NDTV, NPR, and Qz have all joined the platform. Some of the highest-ranking websites in the world, including Wikipedia, WikiHow, Vimeo, Internet Archive, and DuckDuckGo, are also among Brave's 390,000 verified publishers.

Earn Basic Attention Token (BAT) with Brave Web Browser

Try Brave Browser

Get $5 in free BAT to donate to the websites of your choice.

Brave Browser voted the best privacy-focused product of 2019

Out of all the privacy-focused products and apps available on the market, Brave has been voted the best. Other winners of Product Hunt's Golden Kitty awards showed that there was a huge interest in privacy-enhancing products and apps such as chats, maps, and other collaboration tools.

An extremely productive year for Brave

Last year has been a pivotal one for the crypto industry, but few companies managed to see the kind of success Brave did. Almost every day of the year has been packed witch action, as the company managed to officially launch its browser, get its Basic Attention Token out, and onboard hundreds of thousands of verified publishers on its rewards platform.

Luckily, the effort Brave has been putting into its product hasn't gone unnoticed.

The company's revolutionary browser has been voted the best privacy-focused product of 2019, for which it received a Golden Kitty award. The awards, hosted by Product Hunt, were given to the most popular products across 23 different product categories.

Ryan Hoover, the founder of Product Hunt said:

"Our annual Golden Kitty awards celebrate all the great products that makers have launched throughout the year"

Brave's win is important for the company—with this year seeing the most user votes ever, it's a clear indicator of the browser's rapidly rising popularity.

Privacy and blockchain are the strongest forces in tech right now

If reaching 10 million monthly active users in December was Brave's crown achievement, then the Product Hunt award was the cherry on top.

The recognition Brave got from Product Hunt users shows that a market for privacy-focused apps is thriving. All of the apps and products that got a Golden Kitty award from Product Hunt users focused heavily on data protection. Everything from automatic investment apps and remote collaboration tools to smart home products emphasized their privacy.

AI and machine learning rose as another note-worthy trend, but blockchain seemed to be the most dominating force in app development. Blockchain-based messaging apps and maps were hugely popular with Product Hunt users, who seem to value innovation and security.

For those users, Brave is a perfect platform. The company's research and development team has recently debuted its privacy-preserving distributed VPN, which could potentially bring even more security to the user than its already existing Tor extension.

Brave's effort to revolutionize the advertising industry has also been recognized by some of the biggest names in publishing—major publications such as The Washington Post, The Guardian, NDTV, NPR, and Qz have all joined the platform. Some of the highest-ranking websites in the world, including Wikipedia, WikiHow, Vimeo, Internet Archive, and DuckDuckGo, are also among Brave's 390,000 verified publishers.

Earn Basic Attention Token (BAT) with Brave Web Browser

Try Brave Browser

Get $5 in free BAT to donate to the websites of your choice.