Some time ago I was asked what I thought was the best written web-comic. Was it Sluggy Freelance, was it PvP, was it Schlock Mercenary, It's Walky, College Roomies from Hell, Clan of the Cats, Wandering Ones, RPG World, or the like? I surprised the person asking the question by naming a sprite comic as the best written web comic running.
Generally, I hate sprite comics. Free hosting sites like Keenspace were flooded with people putting various sprite rips of Mario, Sonic, and Mega-man together. Some of the sprite comics did rub off on me, such as Bob and George and Alan Solivan's Author Space.
Bob and George was largely a pioneer in the sprite-comic world, and if you can think of a cliche that's used in sprite comics, Bob and George probably did it first. Author Space was largely a spin-off of Alan's The Rogue's Gallery comic, one I enjoyed not only for Alan's great artwork, but also because it was genuinely well written.
As time went on, Bob and George became not just a home page for the webcomic featuring Bob and George, but also a portal to some of the better sprite comics. Sure, a lot of the comics posted through Bob and George were junk, but some gems did shine through.
There was Universal Voyage which was excellent, until I think NW got clonked on the head by Reichsman or something. Oddball Fancomics was worth a read. Evil Inc., which is not related to the spin-off from Greystone Inn was one of the better comics. Taco: the Comic started off slow, but trust me, get to the world ending flood of Taco's, and you'll be glad you did so.
The best comic by far though, and I mean, it really was the best comic, was Ramnesis's Jailhouse Blues. The jokes were original, the plot-line was ludicrous, and the sense of meta-humor through the whole comic just worked. I'd be hard-pressed to name any other web-comic that I looked forward to updating as much as I did Jailhouse Blues.
Then Ramnesis just... disappeared. Nobody on the Bob and George forums knew what happened to him, or if they did, they weren't saying. What was worse for readers like me is that Ramnesis was in the middle of a story-arc that had just exited an extensive psychotic dream scenario and had gotten back to the main story arc against a... well... transforming, regenerating reploid that has gone maverick. Players of any Megaman X game are probably blinking and praying they didn't read that right.
Does Jailhouse Blues stack up as one of the best written webcomics now?
Oh no. Howard Taylor's Schlock Mercenary has come a long way in it's story quality since the days when Jailhouse Blues was updating. There's also comics like Girl Genius and Erfworld being updated these days, and they set a pretty high bar for writing quality.
That being said, the lack of an ending for Jailhouse Blues has always bugged me. I keep wondering what happened to Ramnesis anyways? When other webcomics have ended, many without really resolving plotlines, I basically haven't cared. I doubt there's any that I'd be searching for 3 or 4 years later wondering if the author ever got around to writing a proper ending.
Jailhouse Blues? Well, it was good enough back then to keep me hoping that somewhere Ramnesis will pop back-up and at least finish the story.
This blog normally orients towards technology matters, chewing out various news sites and their readers, but will also include the interests of one Very Grumpy Bunny.
Friday, August 13, 2010
Wednesday, August 04, 2010
Blogger's Font Controls and HTML Generation
Not exactly the post I started with... but while putting together a new guide I got fed up with Google's new in-Blogger picture loading system. Quite simply, the newly exposed in-Blogger composer is not ready for any kind of usage. After filing a bug report in the Blogger help section for stuff that's broken I decided to take on the in-Blogger font controls as well. Since I've been on Blogger I've never really said much about the behind the scenes controls exposed for fonts in the content generator. I've often accepted that Blogger is a relatively free-of-financial cost product that is made available as it leverages Google's core competency: Advertising Distribution through Search.
Google's continued development of Blogger, as well as it's exposure as a tool for Commercially Oriented Blogs, finally warranted something being said on the said state of the internal font controls as they are applied to user generated content. The font controls of the old blogger interface were pathetic at best. Let me demonstrate with a picture of the old in-Blogger composer as accessed through Firefox.

Here I've typed out 3 lines of text. Now I am going to apply a single Font change to these 3 lines:

Now I'm going to access the Edit Html tab at the top of the composer:

Each line of text has been given it's own separate span tag. Now I'm going to go back to the Compose tab and select Font Size.

With my font size set as small, I'm now going to click back on the Edit Html tab:

My entire file size has exploded. I checked in Open Office. There are 339 characters in this HTML generation. The original text only had 92 different characters. Blogger's composing system added 247 new characters, more than tripling the raw text. I now have 5 different sets of commands to set the font size to 85% and 3 different commands to set the font itself to Courier.
The actual amount of HTML code needed to generate the text I want is signifcantly smaller:

As can be seen, with just a total of 149 characters I have the same exact text formatting output.

So that's the old Composer. One would think that Google's new Composer system would fix some of this ludicrous over-use of HTML tags.

The short answer is that no, the new composer actually makes the HTML generation even WORSE than before. The browser that you use will also influence just how many redunant HTML commands are included in the Blogger HTML generation. So here we have the Blogger composer under Google-Chrome using the older editing interface.
Our Text here uses 62 characters. The Blogger HTML generator uses significantly more characters:

No, that is not your eyes decieving you. That is 1,097 characters. More than 1,000 characters have been added to the document source just to describe the formatting on 4 lines comprised of 62 characters.
Is the new Composer system any better? Well, here's the plain text in the new Composer Interface:

Again, this is just 4 lines of text with just 62 characters set to Font Courier with a size of small. This is the HTML generation in the new Composer:

Believe it or not, the amount of HTML has actually gone up, with a total character count of 1168characters. The new Composer system adds 71 new characters. The entire system is OUT OF CONTROL.
Now, I realize that all of the pictures shown thus far deal with converting existing text into the text format I want to use. Is the system really this bad when I am just generating text as a new input? To find out I'm going to use Seamonkey's Composer system to generate the html, and then do the same generation in Google's online system.
With Seamonkey I was able to specify the font type of Courier and font size of small before I actually entered the text:

This is the HTML Source that Seamonkey Compozer generated from 63 characters:

As can be seen, Seamonkey Compozer took 297 characters to fully describe the text, the line breaks, the page, and the pertinent meta data to describe the text as a standalone HTML page. Of this, only 162 characters were used to actuallydescribe the text itself, including the line breaks. Of those 162 characters, 134 characters are used to describe the text without the line breaks.
Of the actual HTML commands, Seamonkey Composer correctly used only two commands to dictate the text formatting. One 'small' command to dictate relative font size, and one font-change command. The result is a relatively efficient use of HTML.
Now, for the comparison, here's how Google Chrome does with Google Blogger. There is another bug with the new content generation system here alone. I can not dictate a font size and type of font before I start entering text. I have to actually enter some text first, then I can specify the size of the font and the type of the font.

As can be seen, I have not typed out the full 4 line character test from before. Rather I can going to make a single carriage return and type a single letter:

With only 13 characters in the edit box, this is what my HTML generation looks like:

Google Blogger has used 497 characters to describe just 13 characters.
Again, I realize that by and large Google's Blogger system is a free-of-financial-cost tool. Google does expose it as a professional option which has been used by CEO's like Rahool Sood of VoodooPC. The old http://voodoopc.blogspot.com/ still directs to http://www.rahulsood.com/, which at first glance still seems to be using the Google Blogger interface. Google also appearently utilizes the content generation Engine in some of it's Premier Business edition tools.
By the same token, Mozilla Seamonkey Compozer is also free-of-financial-cost. Yet the HTML generation of the two software systems is dramatically different. Google's Blogger Compozer is a bloated wreck of an application that adds browser-context-sensative html code.
On a small scale viewpoint the massive train-wreck that is Google's Blogger HTML generation isn't that big of an issue. Internet Speeds are increasing on an across the board basis, and Microsoft has finally figured out that upholding Industry Standards in it's browser might stop the flood of users to competing browsers. What's the big deal if Google Blogger generates a massive amount of redundant and useless HTML code?
The problem is the scale of Google itself. Google hastens of thousands, if not hundreds of thousands, if not potentially millions of active users worldwide. Google goes to great lengths to design datacenters to hold and sort through information. Google goes through a great deal of engineering work to cool these data-centers off and exhaust the massive amount of heat that can be generated.
Okay, fine, one person turning 64 characters of text into over One Thousand Characters of Text is not really a bad thing. 10,000 users turning 64 characters into over One Thousand Characters IS A BAD THING. 100,000users is even worse than that. 1,000,000 uses would generate over 1,000,000,000 characters of text for 64,000,000 characters. This now goes from the realm of small potatoes into that's actually a large amount of bandwidth through the network and storage space on the hard-drives.
Google's formatting system for Blogger NEEDS TO BE FIXED. Getting a handle on HTML formatting and fixing the underlying formatting controls would have a direct and immediate effect on operating network bandwidth, processing time, and file-size storage. I mean, I really would have thought then that an upgrade to Blogger's content generation would have focused on streamlining the HTML generation processor. Instead, the system has gotten even more bloated and more ludicrous in the generation of HTML.
This type of generation is something I would expect from a MICROSOFT PRODUCT.
Google's continued development of Blogger, as well as it's exposure as a tool for Commercially Oriented Blogs, finally warranted something being said on the said state of the internal font controls as they are applied to user generated content. The font controls of the old blogger interface were pathetic at best. Let me demonstrate with a picture of the old in-Blogger composer as accessed through Firefox.

Here I've typed out 3 lines of text. Now I am going to apply a single Font change to these 3 lines:

Now I'm going to access the Edit Html tab at the top of the composer:

Each line of text has been given it's own separate span tag. Now I'm going to go back to the Compose tab and select Font Size.

With my font size set as small, I'm now going to click back on the Edit Html tab:

My entire file size has exploded. I checked in Open Office. There are 339 characters in this HTML generation. The original text only had 92 different characters. Blogger's composing system added 247 new characters, more than tripling the raw text. I now have 5 different sets of commands to set the font size to 85% and 3 different commands to set the font itself to Courier.
The actual amount of HTML code needed to generate the text I want is signifcantly smaller:

As can be seen, with just a total of 149 characters I have the same exact text formatting output.

So that's the old Composer. One would think that Google's new Composer system would fix some of this ludicrous over-use of HTML tags.

The short answer is that no, the new composer actually makes the HTML generation even WORSE than before. The browser that you use will also influence just how many redunant HTML commands are included in the Blogger HTML generation. So here we have the Blogger composer under Google-Chrome using the older editing interface.
Our Text here uses 62 characters. The Blogger HTML generator uses significantly more characters:

No, that is not your eyes decieving you. That is 1,097 characters. More than 1,000 characters have been added to the document source just to describe the formatting on 4 lines comprised of 62 characters.
Is the new Composer system any better? Well, here's the plain text in the new Composer Interface:

Again, this is just 4 lines of text with just 62 characters set to Font Courier with a size of small. This is the HTML generation in the new Composer:

Believe it or not, the amount of HTML has actually gone up, with a total character count of 1168characters. The new Composer system adds 71 new characters. The entire system is OUT OF CONTROL.
Now, I realize that all of the pictures shown thus far deal with converting existing text into the text format I want to use. Is the system really this bad when I am just generating text as a new input? To find out I'm going to use Seamonkey's Composer system to generate the html, and then do the same generation in Google's online system.
With Seamonkey I was able to specify the font type of Courier and font size of small before I actually entered the text:

This is the HTML Source that Seamonkey Compozer generated from 63 characters:

As can be seen, Seamonkey Compozer took 297 characters to fully describe the text, the line breaks, the page, and the pertinent meta data to describe the text as a standalone HTML page. Of this, only 162 characters were used to actuallydescribe the text itself, including the line breaks. Of those 162 characters, 134 characters are used to describe the text without the line breaks.
Of the actual HTML commands, Seamonkey Composer correctly used only two commands to dictate the text formatting. One 'small' command to dictate relative font size, and one font-change command. The result is a relatively efficient use of HTML.
Now, for the comparison, here's how Google Chrome does with Google Blogger. There is another bug with the new content generation system here alone. I can not dictate a font size and type of font before I start entering text. I have to actually enter some text first, then I can specify the size of the font and the type of the font.

As can be seen, I have not typed out the full 4 line character test from before. Rather I can going to make a single carriage return and type a single letter:

With only 13 characters in the edit box, this is what my HTML generation looks like:

Google Blogger has used 497 characters to describe just 13 characters.
Again, I realize that by and large Google's Blogger system is a free-of-financial-cost tool. Google does expose it as a professional option which has been used by CEO's like Rahool Sood of VoodooPC. The old http://voodoopc.blogspot.com/ still directs to http://www.rahulsood.com/, which at first glance still seems to be using the Google Blogger interface. Google also appearently utilizes the content generation Engine in some of it's Premier Business edition tools.
By the same token, Mozilla Seamonkey Compozer is also free-of-financial-cost. Yet the HTML generation of the two software systems is dramatically different. Google's Blogger Compozer is a bloated wreck of an application that adds browser-context-sensative html code.
On a small scale viewpoint the massive train-wreck that is Google's Blogger HTML generation isn't that big of an issue. Internet Speeds are increasing on an across the board basis, and Microsoft has finally figured out that upholding Industry Standards in it's browser might stop the flood of users to competing browsers. What's the big deal if Google Blogger generates a massive amount of redundant and useless HTML code?
The problem is the scale of Google itself. Google hastens of thousands, if not hundreds of thousands, if not potentially millions of active users worldwide. Google goes to great lengths to design datacenters to hold and sort through information. Google goes through a great deal of engineering work to cool these data-centers off and exhaust the massive amount of heat that can be generated.
Okay, fine, one person turning 64 characters of text into over One Thousand Characters of Text is not really a bad thing. 10,000 users turning 64 characters into over One Thousand Characters IS A BAD THING. 100,000users is even worse than that. 1,000,000 uses would generate over 1,000,000,000 characters of text for 64,000,000 characters. This now goes from the realm of small potatoes into that's actually a large amount of bandwidth through the network and storage space on the hard-drives.
Google's formatting system for Blogger NEEDS TO BE FIXED. Getting a handle on HTML formatting and fixing the underlying formatting controls would have a direct and immediate effect on operating network bandwidth, processing time, and file-size storage. I mean, I really would have thought then that an upgrade to Blogger's content generation would have focused on streamlining the HTML generation processor. Instead, the system has gotten even more bloated and more ludicrous in the generation of HTML.
This type of generation is something I would expect from a MICROSOFT PRODUCT.
Saturday, July 31, 2010
Nvidia beta's OpenGL 4.1
http://developer.nvidia.com/object/opengl_driver.html
Nvidia has pushed an OpenGL 4.1 driver out the door for testing. Granted I'm unable to actually test this I don't have any Fermi based cards on hand
Now, I'll admit that I'm not exactly Nvidia's biggest fan. I consider the GTX 470
to be overpriced, too hot, and too power hungry. I'm not even sure the 850 watt power supplies
I picked up some time ago could handle 3 470's in Triple SLI. I have an even lower opinion of the GTX 480
. Yes, the GTX 480 is more powerful than a stock RadeonHD 5870
, but if you check the links that I'm putting in here, it's not near as makes no difference $100 more powerful.
Anyways, since I don't have a Fermi card on hand to test with, I can't really give any feedback on how well this driver works. For this then, I'll just have to rely on readers who bought Fermi cards to download and test the driver.
Nvidia has pushed an OpenGL 4.1 driver out the door for testing. Granted I'm unable to actually test this I don't have any Fermi based cards on hand
Now, I'll admit that I'm not exactly Nvidia's biggest fan. I consider the GTX 470
Anyways, since I don't have a Fermi card on hand to test with, I can't really give any feedback on how well this driver works. For this then, I'll just have to rely on readers who bought Fermi cards to download and test the driver.
Monday, July 05, 2010
Biting the Bullet: Help
Over the past couple of years that I've been writing this blog, I've been reluctant to well, talk about myself. Of course, this meant disappearing for months at a time with only a trickle of posts, then a flood of posts, then another disappearance, and so on. I've also mentioned my dislike of taking donations, instead pointing readers to other sources who needed it more.
Well, now I'm having to bite a bullet here and actually ask for help.
Short version is, I'm not exactly healthy. I wrote about one of my major problems back on live journal several years back, where I was determined by the Augusta Neuroscience Doctors to have a pinched nerve, one they couldn't locate, and one Blue Cross / Blue Shield wasn't willing to continue to fund treatment for. The basic problems of the pinched nerve is that my legs will cramp up, and my muscles can quite literally rip themselves apart. Other symptoms include prolonged work leading to my legs locking up and my knees turning purple. I don't like to talk about this because I'd rather not admit that I'm injured, or go through the hassle of filing for a disability since I'm not really disabled... as I see it.
The second major problem, well, I think I've mentioned here, is my blood pressure, which has normally been high. Earlier this year I came down with an illness, and was thrown into the hospital for intense dehydration and a blood pressure systolic reading of 80. Which caused a couple of double-takes from nurses, at least one "you should be unconscious" statement, and more than a few "you walked to your hospital bed?" questions.
Also, over the past couple of months, my bad legs and back and have, well, come back to haunt me, causing their own pain and driving a bad case of insomnia. So, I've been on and off stuff like Fioricet, Ultram, Mobic, Flexeril, Naprosyn, and Ambien.
Which brings me to the problem of... now. Since I was dismissed from AC, I haven't been able to find another job local to me within the realm of tech support or computer repair, outside of a part-time job as a family systems administrator. Immediately, this means I have a still looming hospital bill that I can't pay.
Which means I am now at the point of, well, needing help.
I really wanted to have something more to show for this post, which is why I kept putting it off. My, direct intent, had been to work on getting a proper book published, and to that end I've been putting some of my old Callaer stories together. I've uploaded the progress that I've made on piecing these stories together to Google Docs:
Forward
Part 1: Origins
Part 2: Exit
Part 3: Roxanne
From this point though, I don't know where to start with to get a publishing deal. The last time I had anything published in a proper book (mostly poetry), my English teachers took care of all the details.
My, immediate plan of action then, is to finish editing the first few parts I have now and create an Ebook on Lulu. I had wanted to have an Ebook ready for purchase, but the more I put off making this post, the more difficult it is going to be for me to make this post.
I am also, at this point, willing to do something I haven't been willing to do in the past, which is move. I haven't been wanting to leave the Augusta area largely because of my health issues. There is a certain amount of comfort being in a hospital town, and with doctors being somewhat familiar with my medical background.
I think that's really all I have to say for now... I'll try to get back to posting opinion pieces on tech and finishing up several game reviews I've had on the table.
Meanwhile, I can hope that a game studio decides they need another writer or somebody to handle tech support... maybe I should go poke Valve.
Well, now I'm having to bite a bullet here and actually ask for help.
Short version is, I'm not exactly healthy. I wrote about one of my major problems back on live journal several years back, where I was determined by the Augusta Neuroscience Doctors to have a pinched nerve, one they couldn't locate, and one Blue Cross / Blue Shield wasn't willing to continue to fund treatment for. The basic problems of the pinched nerve is that my legs will cramp up, and my muscles can quite literally rip themselves apart. Other symptoms include prolonged work leading to my legs locking up and my knees turning purple. I don't like to talk about this because I'd rather not admit that I'm injured, or go through the hassle of filing for a disability since I'm not really disabled... as I see it.
The second major problem, well, I think I've mentioned here, is my blood pressure, which has normally been high. Earlier this year I came down with an illness, and was thrown into the hospital for intense dehydration and a blood pressure systolic reading of 80. Which caused a couple of double-takes from nurses, at least one "you should be unconscious" statement, and more than a few "you walked to your hospital bed?" questions.
Also, over the past couple of months, my bad legs and back and have, well, come back to haunt me, causing their own pain and driving a bad case of insomnia. So, I've been on and off stuff like Fioricet, Ultram, Mobic, Flexeril, Naprosyn, and Ambien.
Which brings me to the problem of... now. Since I was dismissed from AC, I haven't been able to find another job local to me within the realm of tech support or computer repair, outside of a part-time job as a family systems administrator. Immediately, this means I have a still looming hospital bill that I can't pay.
Which means I am now at the point of, well, needing help.
I really wanted to have something more to show for this post, which is why I kept putting it off. My, direct intent, had been to work on getting a proper book published, and to that end I've been putting some of my old Callaer stories together. I've uploaded the progress that I've made on piecing these stories together to Google Docs:
Forward
Part 1: Origins
Part 2: Exit
Part 3: Roxanne
From this point though, I don't know where to start with to get a publishing deal. The last time I had anything published in a proper book (mostly poetry), my English teachers took care of all the details.
My, immediate plan of action then, is to finish editing the first few parts I have now and create an Ebook on Lulu. I had wanted to have an Ebook ready for purchase, but the more I put off making this post, the more difficult it is going to be for me to make this post.
I am also, at this point, willing to do something I haven't been willing to do in the past, which is move. I haven't been wanting to leave the Augusta area largely because of my health issues. There is a certain amount of comfort being in a hospital town, and with doctors being somewhat familiar with my medical background.
I think that's really all I have to say for now... I'll try to get back to posting opinion pieces on tech and finishing up several game reviews I've had on the table.
Meanwhile, I can hope that a game studio decides they need another writer or somebody to handle tech support... maybe I should go poke Valve.
Wednesday, June 30, 2010
More bad news for Nvidia: Sony Viao Recalls
http://www.geek.com/articles/chips/sony-recall-535000-vaio-laptops-as-heat-distorts-shape-burns-skin-20100630/
I really don't have much more to say on this subject.
I really don't have much more to say on this subject.
Saturday, June 19, 2010
Gamenikki.com Domain
Might as well go ahead and address this. The content from Gamenikki.com can currently be found at www.gamenikkiinexile.com
It's a long and ugly story, and I think the shortest way I can explain the situation is that somebody at the hosting provider decided to stop answering the telephone.
Of course, this means that jason at gamenikki dot com is out of commission. I can be reached at jason dot frothingham at gmail dot com, or mepisguides at gmail dot com.
It's a long and ugly story, and I think the shortest way I can explain the situation is that somebody at the hosting provider decided to stop answering the telephone.
Of course, this means that jason at gamenikki dot com is out of commission. I can be reached at jason dot frothingham at gmail dot com, or mepisguides at gmail dot com.
Friday, June 18, 2010
CoH: Tracking Combat numbers
One of the questions I get asked on a regular basis is how I get a separate window to track combat statistics in City of Heroes
, as shown with my ice tank here:
To get this pop-up, simply open up Combat Attributes from the Power Tray
Here we have our list of the avatar's vital stats.
As can be seen, I typically monitor my Ice Tank's Smashing / Lethal Defense, Recovery Rate, and Endurance consumption.
If you Right Click on a combat stat in the main power window, there's a pop-up with an option to Monitor Attribute.
So, if I Right Click on Energy Defense and Left Click on Monitor Energy Defense..
Energy Defense is added to the combat tracking window.
Basically, you can monitor all of the vital stats of an avatar.

Have fun keeping track of your character.
To get this pop-up, simply open up Combat Attributes from the Power Tray
Here we have our list of the avatar's vital stats.
As can be seen, I typically monitor my Ice Tank's Smashing / Lethal Defense, Recovery Rate, and Endurance consumption.
If you Right Click on a combat stat in the main power window, there's a pop-up with an option to Monitor Attribute.
So, if I Right Click on Energy Defense and Left Click on Monitor Energy Defense..
Energy Defense is added to the combat tracking window.
Basically, you can monitor all of the vital stats of an avatar.
Have fun keeping track of your character.
Sunday, May 30, 2010
CoH: Willpower / Stone Melee Tank
Jordan Yen, of Jordon's Town, has been bugging me to join in his ongoing contest with new player guide(s). So, here's a another, not so new character build, and to date, probably one of the cheapest ones to actually make. It's a Willpower / Stone Melee tank, made largely because I saw somebody with a WP/Stone tank a MoSTF.
Saying that Willpower has issues is a bit misleading. The set is honestly one of the better balanced sets for survivability. There's really no "what the blazes were you thinking" power or "that's an auto-skip power" to be had in the set. Willpower is a good solid set for those who have never played C.o.H. before, and an excellent choice for veterans as well.
That being said, there are some things that Willpower players probably should know.
Stone Melee is also a good set, providing players know what they are getting.
Because of these factors, Willpower / Stone both works well together, and doesn't work well together. The lack of a strong AOE component, or a taunt that builds against Gauntlet means that Aggro Tanks will have to work really hard to hold aggro on AOE heavy teams.
However, Willpower's high recovery potential means it can support sustained use of Stone Melee's hardest hitting powers.
Overall Power Selection and Design
The Willpower set itself is an Asynchronous Mixed Resist / Defense / Regeneration set. What this means is that the set has native resists, native defenses, and native regenerations, but the resists and the defenses generally don't stack for the same damage type. This gives Willpower a wider range of power types compared to other tank sets, and is one of the reasons. Technically, each power type is weaker when directly compared to another power sets power with the same effect. In the case of Willpower though, it's the entire package that makes the set, not a single solitary power.
I approached the Willpower slot design with 3 primary goals in mind:

As can be seen, my love of frankenslotting continues. Now I feel sure that somebody is going to come along and say that I missed an opportunity to make this build .001% better by switching out some of the crafted level 50 IO's for an IO set.
I don't particullary care, and I'll explain why at the end of the post.
Now, the most expensive part of this build is the procs. Again, I knew on paper going into this build that there was no protection against slows. The proc's really are not required to make a Willpower Build shine. Now, procs can make a good willpower set great, but if you just want something to cut your teeth on, this build is a bit overkill.
Now into the powers and the slots.
Mind over Body: Mind over Body is the primary resistance for Smashing, Lethal, and Psionic Damage.
Compared to the Dark Armor set that I just looked at, the outright resist values are indeed lower. As we'll so though shortly, this isn't really an apples to apples comparison.

For the slotting, I went mostly with a 3 slot Titanium Coating for the health boost, and an Aegis Resist / Endurance IO to lesson endurance usage and increase resists.

Fast Healing: The primary native regeneration power.
The power is slammed far into ED with 3 level 50 crafted Heal IO's.

The proc in use is the Regenerative Tissue: Regeneration proc.

Indomitable Will: The primary anti-mez power for Willpower, IW also offers a Psionic Defense Bonus.

Leveraging this Defense Status are both a LoTG 7.5 recharge proc

And a GoTA: Run proc.

Rise to the Challenge: The Willpower's taunt aura.
Rise to the Challenge also increases the player's regeneration rate while fighting mobs, while decreasing a mob's to-hit rating. The To-Hit debuff combo's well with Defense sets, as a lower to-hit is the equivelent of a higher defense rating.

Here though, for Willpower, I focused more on the healing aspect, maximixing the healing aspect while in a mob situation, and edging off the endurance usage.
A Doctored Wounds End / Heal provides the extra heals and endurance reduction ontop of the 3 slotted Numina's Convelesence.

Quick Recovery: Willpower offers a native recovery bonus.

Here a level 50 crafted IO backs up a double slot Performance Shifter with chance for endurance.

Heightened Senses: The primary defensive power of the Willpower set.
While Mind over Body provides a strong resistance to Smashing, Lethal, and Psionic damage, Heightened Senses only provides for minor Smashing and Lethal damage defense with no protection against Psionic Damage.
Rather, Heightened Senses provides a strong defense against the other damage types, Cold, Fire, Energy, Negative Energy.
Heightened Senses, as a defense power, shares the same IO's as Indomitable Will.

High Pain Tolerance: This power simply offers resistance to all damage types, and raises the players maximum HP. No fancy IO sets here, just straight level 50 crafted IO's to maximize the dual nature of this power.

Strength of Will: The tier 9, I'm in trouble power for the Willpower set.
Like High Pain Tolerance, it's IO potential is limited, since the only enhancements it can accept are Resist Damage and Reduce Endurance Consumption. However, since it's Endurance usage is only 2.60 End, this really isn't a barrier to usage.

Still, it was a good place to slot a Steadfast Protection: resist / defense proc.

With the primary powers done, now onto the attacks:
Stone Fist: Reasonable Damage, Reasonable endurance usage.


Stone Mallet: Another melee attack, same slotting with Crushing Impact.

Heavy Mallet: Another Melee attack, and more Crushing Impact.

Taunt: I know I keep saying this over and over. Tanks need taunt.

Perfect Zinger is leveraged for it's 5% recharge boost, incidentally capping the 5% recharge buffs.

Fault: Originally I was not going to take this power, and for the longest time ran without it.
However, one of my friends also has a Willpower / Stone tank, and his internet service died one night while he was prime-tanking an ITF. He called me to login in and finish the TF out. I found, strangely, that fault helped shore up the poor aggro control.

I also figured out that I hated the power because every tank whose taken this before probably slotted it for knockback instead of stun.

Tremor: The only PBAOE power Stone Melee gets.

Scirocco's Dervish is pretty much the only good PBAOE damage set for a power that's used on a repetitive basis.

Seismic Smash: Also known as kiss your endurance good bye.

Even with a near 70% decrease in endurnace consumption from Crushing Impact, this attack still wipes out 1/10 of an average endurance bar

Hurl: Stone Melee is one of the few tank attacks with a ranged component.

Devestation: useful for the damage and max HP bonus.

Combat Jumping: I knew early on that I wanted another base for Luck of the Gambler proc, and since only the jump and fly sets offer this slotting, I went with Combat Jumping.

As mentioned, Combat jumping is just a proc mule.

Super Jump: not much to type here really.

Winter's Gift was chosen as it's unique proc helps shore up Willpower's lack of any native resistance to slows.

Health: Proc Mule.

Hosting Numina's unique, and a 3 slot on the numina set for the HP boost.

Stamina: same slotting as Quick Recovery

Boxing. As normal, a single stun.

Tough: not much to write here. Same slotting as Mind over Body.

Weave: Same slotting as the other defensive powers.

Okay, here we go with the analysis of what this slotting does.

44

Now, on these initial numbers, you might notice that they aren't actually that far off of the numbers from the heavily IO'd Dark Tank I just showed. Both have near 70% resistance to Smashing / Lethal damage. The Dark tank as better esoteric resists, the Willpower tank has better esoteric defenses.
There are differences though.
The Dark tank has a maximum HP of 2550, and that's after the inclusion of all of the available Accolades to boost Hit points.
The Willpower tank has a current maximum HP of 2816 and is missing two HP boosting accolades. Those accolades will give 93.70 hp and 187.41 hp respectively, bringing the Willpower's tank maximum health up to around 3097.
The Dark Tank has a regeneration rate of 23.92 HP per second.
The Willpower Tank has an out of combat regeneration rate of 53.36... and in combat sustained regeneration of... 134 hp/sec.

Then there's the small matter of Strength of Will. Activate it...


In Strength of Will, smashing / lethal resistance is hard-capped, resistances to everything else increase, and endurance recovery goes up. Even on SO's, Strength of Will will be touching hard-cap smash / lethal numbers.
There's also the matter of Defense Debuff Resistance, something I found difficult to take pictures of. Basically put, when something attacks a Willpower tank with a power that removes Defense, not as much defense is removed in each attack.
The Dark armor set gets no such benefit, so any attack that takes aware defense... takes away the maximum amount of defense.

I figure my HP cap bonus's as follows:
1.5% : 1, 2
1.88%: 1, 2, 3
1.13%: 1, 2, 3, 4
2.25%: 1
Swapping out the level 50 crafted Endurance IO's for a performance shifter endurance / something would put me at the 1.88% cap, and in theory, a Miracle proc placed on Fast Healing would make up the endurance usage.
I'm not entirely sure that's the best way to go though, and I'm not likely to change it for now.
The Major Issues
Saying that Willpower has issues is a bit misleading. The set is honestly one of the better balanced sets for survivability. There's really no "what the blazes were you thinking" power or "that's an auto-skip power" to be had in the set. Willpower is a good solid set for those who have never played C.o.H. before, and an excellent choice for veterans as well.
That being said, there are some things that Willpower players probably should know.
- Willpower is pretty much about the regeneration rate, so anything that boosts regeneration and the HP cap is a good thing.
- There's no native resistance to slows. Which means that every single enemy critter with a slow attack is going to slow down a WP with no problem.
- The native taunt aura is weak. All other Tank Taunt aura's taunt for 400%, Willpower's aura only taunts for 300%.
- The native taunt also can't build against Gauntlet as it has no damage component.
Stone Melee is also a good set, providing players know what they are getting.
- Like Energy Melee, Stone Melee is weak on the AOE damage.
- Stone Melee is also an incredible endurance hog.
Because of these factors, Willpower / Stone both works well together, and doesn't work well together. The lack of a strong AOE component, or a taunt that builds against Gauntlet means that Aggro Tanks will have to work really hard to hold aggro on AOE heavy teams.
However, Willpower's high recovery potential means it can support sustained use of Stone Melee's hardest hitting powers.
Overall Power Selection and Design
The Willpower set itself is an Asynchronous Mixed Resist / Defense / Regeneration set. What this means is that the set has native resists, native defenses, and native regenerations, but the resists and the defenses generally don't stack for the same damage type. This gives Willpower a wider range of power types compared to other tank sets, and is one of the reasons. Technically, each power type is weaker when directly compared to another power sets power with the same effect. In the case of Willpower though, it's the entire package that makes the set, not a single solitary power.
I approached the Willpower slot design with 3 primary goals in mind:
- Boost HP Cap
- Boost Regeneration
- Boost Recharge Rate

As can be seen, my love of frankenslotting continues. Now I feel sure that somebody is going to come along and say that I missed an opportunity to make this build .001% better by switching out some of the crafted level 50 IO's for an IO set.
I don't particullary care, and I'll explain why at the end of the post.
Now, the most expensive part of this build is the procs. Again, I knew on paper going into this build that there was no protection against slows. The proc's really are not required to make a Willpower Build shine. Now, procs can make a good willpower set great, but if you just want something to cut your teeth on, this build is a bit overkill.
The Build: Primary Powers
Now into the powers and the slots.
Mind over Body: Mind over Body is the primary resistance for Smashing, Lethal, and Psionic Damage.
Compared to the Dark Armor set that I just looked at, the outright resist values are indeed lower. As we'll so though shortly, this isn't really an apples to apples comparison.

For the slotting, I went mostly with a 3 slot Titanium Coating for the health boost, and an Aegis Resist / Endurance IO to lesson endurance usage and increase resists.

Fast Healing: The primary native regeneration power.
The power is slammed far into ED with 3 level 50 crafted Heal IO's.

The proc in use is the Regenerative Tissue: Regeneration proc.

Indomitable Will: The primary anti-mez power for Willpower, IW also offers a Psionic Defense Bonus.

Leveraging this Defense Status are both a LoTG 7.5 recharge proc

And a GoTA: Run proc.

Rise to the Challenge: The Willpower's taunt aura.
Rise to the Challenge also increases the player's regeneration rate while fighting mobs, while decreasing a mob's to-hit rating. The To-Hit debuff combo's well with Defense sets, as a lower to-hit is the equivelent of a higher defense rating.

Here though, for Willpower, I focused more on the healing aspect, maximixing the healing aspect while in a mob situation, and edging off the endurance usage.
A Doctored Wounds End / Heal provides the extra heals and endurance reduction ontop of the 3 slotted Numina's Convelesence.

Quick Recovery: Willpower offers a native recovery bonus.

Here a level 50 crafted IO backs up a double slot Performance Shifter with chance for endurance.

Heightened Senses: The primary defensive power of the Willpower set.
While Mind over Body provides a strong resistance to Smashing, Lethal, and Psionic damage, Heightened Senses only provides for minor Smashing and Lethal damage defense with no protection against Psionic Damage.
Rather, Heightened Senses provides a strong defense against the other damage types, Cold, Fire, Energy, Negative Energy.
Heightened Senses, as a defense power, shares the same IO's as Indomitable Will.

High Pain Tolerance: This power simply offers resistance to all damage types, and raises the players maximum HP. No fancy IO sets here, just straight level 50 crafted IO's to maximize the dual nature of this power.

Strength of Will: The tier 9, I'm in trouble power for the Willpower set.
Like High Pain Tolerance, it's IO potential is limited, since the only enhancements it can accept are Resist Damage and Reduce Endurance Consumption. However, since it's Endurance usage is only 2.60 End, this really isn't a barrier to usage.

Still, it was a good place to slot a Steadfast Protection: resist / defense proc.

The Build: Secondary Powers
With the primary powers done, now onto the attacks:
Stone Fist: Reasonable Damage, Reasonable endurance usage.


Stone Mallet: Another melee attack, same slotting with Crushing Impact.

Heavy Mallet: Another Melee attack, and more Crushing Impact.

Taunt: I know I keep saying this over and over. Tanks need taunt.

Perfect Zinger is leveraged for it's 5% recharge boost, incidentally capping the 5% recharge buffs.

Fault: Originally I was not going to take this power, and for the longest time ran without it.
However, one of my friends also has a Willpower / Stone tank, and his internet service died one night while he was prime-tanking an ITF. He called me to login in and finish the TF out. I found, strangely, that fault helped shore up the poor aggro control.

I also figured out that I hated the power because every tank whose taken this before probably slotted it for knockback instead of stun.

Tremor: The only PBAOE power Stone Melee gets.

Scirocco's Dervish is pretty much the only good PBAOE damage set for a power that's used on a repetitive basis.

Seismic Smash: Also known as kiss your endurance good bye.

Even with a near 70% decrease in endurnace consumption from Crushing Impact, this attack still wipes out 1/10 of an average endurance bar

Hurl: Stone Melee is one of the few tank attacks with a ranged component.

Devestation: useful for the damage and max HP bonus.

Pool Powers
Combat Jumping: I knew early on that I wanted another base for Luck of the Gambler proc, and since only the jump and fly sets offer this slotting, I went with Combat Jumping.

As mentioned, Combat jumping is just a proc mule.

Super Jump: not much to type here really.

Winter's Gift was chosen as it's unique proc helps shore up Willpower's lack of any native resistance to slows.

Health: Proc Mule.

Hosting Numina's unique, and a 3 slot on the numina set for the HP boost.

Stamina: same slotting as Quick Recovery

Boxing. As normal, a single stun.

Tough: not much to write here. Same slotting as Mind over Body.

Weave: Same slotting as the other defensive powers.

Power Performance
Okay, here we go with the analysis of what this slotting does.

44

Now, on these initial numbers, you might notice that they aren't actually that far off of the numbers from the heavily IO'd Dark Tank I just showed. Both have near 70% resistance to Smashing / Lethal damage. The Dark tank as better esoteric resists, the Willpower tank has better esoteric defenses.
There are differences though.
The Dark tank has a maximum HP of 2550, and that's after the inclusion of all of the available Accolades to boost Hit points.
The Willpower tank has a current maximum HP of 2816 and is missing two HP boosting accolades. Those accolades will give 93.70 hp and 187.41 hp respectively, bringing the Willpower's tank maximum health up to around 3097.
The Dark Tank has a regeneration rate of 23.92 HP per second.
The Willpower Tank has an out of combat regeneration rate of 53.36... and in combat sustained regeneration of... 134 hp/sec.

Then there's the small matter of Strength of Will. Activate it...


In Strength of Will, smashing / lethal resistance is hard-capped, resistances to everything else increase, and endurance recovery goes up. Even on SO's, Strength of Will will be touching hard-cap smash / lethal numbers.
There's also the matter of Defense Debuff Resistance, something I found difficult to take pictures of. Basically put, when something attacks a Willpower tank with a power that removes Defense, not as much defense is removed in each attack.
The Dark armor set gets no such benefit, so any attack that takes aware defense... takes away the maximum amount of defense.
***
Now, as I said earlier, I know this build is not as tightly optimized as the Dark Tank / Energy Melee build. It doesn't need to be. This tank is Master of capable and has prime-tanked all of the Master of capable task forces.
Now, once I get the last couple of HP buff accolades, I'll be within a hundred points or so of the HP cap.
When writing this guide (and why it's going up now and I'm still finishing it out), is I've been playing around with a build that works on increasing the HP cap by sacrificing some of the end-recovery capability.
Now, once I get the last couple of HP buff accolades, I'll be within a hundred points or so of the HP cap.
When writing this guide (and why it's going up now and I'm still finishing it out), is I've been playing around with a build that works on increasing the HP cap by sacrificing some of the end-recovery capability.

I figure my HP cap bonus's as follows:
1.5% : 1, 2
1.88%: 1, 2, 3
1.13%: 1, 2, 3, 4
2.25%: 1
Swapping out the level 50 crafted Endurance IO's for a performance shifter endurance / something would put me at the 1.88% cap, and in theory, a Miracle proc placed on Fast Healing would make up the endurance usage.
I'm not entirely sure that's the best way to go though, and I'm not likely to change it for now.
Subscribe to:
Posts (Atom)








