The Woodshed

Behind here, no one can hear you scream

Clash Of Clans Attack: GoHoWiWi

Golems, Hogs, Wizards, Witches

The Name:

The official name that the community has given this attack (if you want to look up more about it, such as examples on YouTube) is “GoHoWiWi” (obtained by taking the first two letters of the major troops involved). In fact, the attack where you use 2 golems is called “Shattered GoHoWiWi” (silly name, yes).

The Troops:

  • 2 Golems
  • 1-2 Witches
  • 8-14 Wizards
  • 15-20 Hog Riders
  • Bring a few barbs/archers to help with luring/killing their troops
  • If your hogs are below level 4, try to request level 4+ hogs for your clan castle

The Spells:

  • 1-2 Heal
  • 1-2 Rage
  • 1 Jump

The Objective:

After taking out their clan castle troops, you want your golems and wizards to clear out the defenses on one side of the base, so that when you deploy your hogs and heroes, they will head for the important buildings in the center of the base. The golems, wizards, and witches should also help deal with some big problems faced by traditional hog attacks: triggering giant bombs and distracting the enemy Archer Queen.

The Breakdown:

  • Lure out the enemy castle troops. Remember that hog riders and golems will ignore enemy troops in favor of defensive buildings, so this is a crucial step. Before you attack, identify a place where you can drop a couple units that will walk in range of their clan castle and draw out the troops. Once the enemy troops are out, draw them to a corner with your barbs/archers, drop a witch to distract them with skeletons, and perhaps a single wizard to help kill them.

  • Place your golems. Do not place both golems in the same spot. They should both be deployed on the same general “side” of the base, but a good distance apart so that they will take different paths through the base.

  • Immediately place your wizards next. They should be placed one at a time (don’t hold your finger down on the screen), in an arc that spans between your golems. Place the “inner” 6-8 wizards first, and then drop a couple right behind each golem.

  • If you have a witch remaining, place her behind the golem that’s most likely to head towards the enemy Queen.

  • Give the golems/wizards/witches a few moments to take out the outer defenses. The goal is to get rid of defenses that might distract your hogs from going towards the core of the base. You also want their Archer Queen to focus on one of your golems and/or your witch’s skeletons, and not on your hogs. Do not, however, wait for your frontline units to get themselves killed before you release your hogs—you don’t want to run out of time!

  • Deploy your hogs. Hold your finger down in one spot while you’re dropping them, so that they all head in the same direction. To reiterate, you want to pick a spot such that they target a defense that will draw them toward the center. Get ready to cast spells on them: a heal spell if they trigger a Giant Bomb or are near Wizard Towers, and a rage spell once they get to the important defenses in the core of the base.

  • There should now be a relatively clear route for your King and Queen to take that will lead them to the enemy town hall. Use your jump spell to help get them there, and of course don’t forget about their abilities!

Rough Raidin'

Since 2005. Sometimes.

Ever since a game called EverQuest came out in 1999, the raid has been a popular—but notoriously demanding—activity for adults who play video games. The essential principle is a large group of players join forces to defeat a dragon (or some such). As the genre has evolved, doing this requires an increasing amount of organization, commitment, and coordination between these players. It is a team “sport” where your teammates may live on the other side of the country (or the world), and you can “compete” regardless of physical prowess, age, or gender.

I was a successful “raider” when I played EverQuest in high school, but since then, depression (and whatever other defects) have impaired my ability to do so (as they have impaired most all aspects of my life in general). Thus, although I’ve tried raiding in World of Warcraft several times in recent years, I’ve generally with varying levels of failure. This is certainly just a drop in the bucket when compared to other areas of life wherein I’ve dropped the ball, but it has helped provide an important insight: my case is perhaps somewhat different from the individual who neglects responsibilities he doesn’t enjoy but devotes himself to hobbies he enjoys. I’ve tended to neglect everything, without “enjoyment discrimination.”

Nevertheless, during those times in which I’m feeling a bit better, attempting to raid has become an interesting barometer of sorts. It requires commitments in a number of legitimate areas that are difficult for me, but the consequences of failure aren’t on the same magnitude as the big “real life” responsibilities.

Non-exhaustively, raiding requires:

  • Schedule commitment (so, reliability, one of my biggest concerns)
  • Time commitment (ability to work on something for 2-3 consecutive hours)
  • Focus commitment (ability to sustain a challenging activity without frustration or fatigue)
  • Self-evaluation commitment (another of my biggest concerns—dealing with personal imperfections without beating myself up)
  • Social commitment (raids are done with anywhere from 10 to 30 people; there is constant communication/interaction [often via voice, like a big conference call]. Even if they are nice people, putting myself out there has always been a big source of anxiety)
  • Attitude commitment (staying positive and open-minded, if not necessarily cheerful, despite the toll that all those other commitments may take)

My last attempt was early in the spring, so it’s been almost a year now. I picked the game up again around Thanksgiving, and met some nice folks who convinced me to give raiding another go. Theirs is a friendly team with a non-judgmental atmosphere, which is good. It’s only been a week, but I can already see marked improvements in most of the aforementioned areas compared to previous forays. Perhaps I’m making some progress after all…

Bashing The Basher

A rebuttal

I disagree with this article. (Specifically, the Bash suggestion—SQLite is cool.)

Let’s start off with some bullet points.

  • Bash might come “preinstalled on your Mac,” but it doesn’t with Windows (not fair to simply ignore the huge amount of people who use Windows), and it’s actually not even the default shell on many Linux distros (last I checked, Ubuntu uses Dash, for example, though it does come with a Bash binary).
  • There is a surprising amount of differences in supported features between Bash versions. It definitely shouldn’t be viewed as some kind of panacea of portability (and in fact neckbeards recommend trying to stick with #!/bin/sh if you can, if you have an interest in writing portable shell scripts).
  • His points about “learning a little at a time” can largely apply to, say, JavaScript (and in fact that’s how a lot of people learn JS)…
  • …But I don’t necessarily agree with that approach anyway. He talks about not realizing Bash supported arrays for 2 years as if that were a good thing; to me that is saying, “I wasted time doing things in a suboptimal way for 2 years.”
  • Bash is full of unintuitive, surprising semantics, not to mention syntax so ugly that it makes Perl blush. For example, if you want to do simple arithmetic, you better enclose it within the right construct (namely the $(( )) stuff), or it’s not going to work right. Same goes for things like comparing variables, text substitution, the list goes on and on. Seriously, just try reading Bash’s manual someday; you’ll quickly realize it’s not there to hold your hand.

I think what he’s trying to say is, it’s nice to be able to see results fast. And that’s fine, but I think you can see just as many results just as quickly from learning a little JS+jQuery (and hell, someone might actually pay you for it… good luck selling your crazyass “Bash+SQLite Application”). Granted, JS has its share of pitfalls too, and I wouldn’t necessarily pick it for a beginner’s first language, but it’s a lot more sensible than Bash.

I think the choice of first language depends on the person. Are we talking about someone who has aspirations to work as a professional developer? A casual hobbyist? Someone in a computery field (sysadmin, web designer, et al.) who wants to automate something or supplement their work? Someone who is interested in scripting a particular application, but doesn’t care about programming outside that?

In any case, I wouldn’t name “Bash” as my choice for any of those people. If “it depends” isn’t a good enough answer, my generic response is probably Python. My pick for the “smallest/cleanest” category actually goes to Lua, but its (albeit intentionally) limited number of out-of-the-box libraries really only make it suitable for beginners who can use it in a preexisting scripting environment (World of Warcraft is one such). Thus Python, even though I don’t care to use it for my own projects, is probably the closest thing to “sane” among the superpopular languages (which thus have a large ecosystem of learning resources, libraries, etc.) I know that’s not as exciting as boldly recommending a crufty shell scripting language, but people don’t come to this blog to be excited. (They come because I send them a link.)

Humphrey Boggart

A cardial journey

The story of the boggarts, Lorwyn’s charming race of mischevious goblins.

Boggarts are tribal, with the tribe living in a warren led by a matriarch known as “Auntie.”
Boggarts live to feel, and share these feelings with other boggarts.
And not sharing is not caring!
The best way to experience new sensations is to get out there and do stuff!
(Yes, those are hedgehog projectiles :)
This might not always go well, but that’s okay.