GuyPerfect

The .dat files come from the Titan Network site. If you can't access it, it may be a firewall issue.

Before anyone decides to follow in my footsteps, realize that it was old before I posted this.

We're all super villains, right (Golden Girl, go away)? We know what it means to be super. Everything we do is super: be it kicking puppies (SUPER kicking), eating breakfast cereal, and filing our taxes. If you're not going to be super about it, then why bother? Where's the flair? The finesse?

Today, I'm going to talk to you about not only how to submit a software bug report, but to submit a super bug report! Let's go over the basics.

* Identifying a Bug - A bug may be somewhat loosely defined, but everyone seems to agree on it meaning one thing: the software doesn't work as advertised. Don't worry about definitions, though, because they're not important. When submitting a bug report, you can submit it about anything you want, including any of the following... A feature exists but you don't know where it is. A data error is present that may as well be a program error. A feature exists but you don't know how to use it. You are using an entirely different application. And this one's my favorite: You are unable to do something that the software doesn't even claim to do.

* Ticket Title - When looking over the list of fatal errors and life-changing problems caused by their software, the developers don't really like to waste their time trying to pick through long, complicated ticket captions. When submitting a report, make sure you call it something short and easy to read, such as "bug problem" or "doesnt work." Be sure to use all-lowercase and exclude punctuation, since consistency is much easier on the eyes.

* Bug Description - In order for the developers to be able to fix the problem you are reporting, you should give some minimalist information about it. Don't be verbose or otherwise understandible--again, it's about looking through reports quickly and developers are all psychics anyway (C++ is short for "psychic"). Identify the most general aspect of the program in which you've encountered a problem, and say that the feature in its entirety is completely non-functional.

* User Information - Sometimes it's a matter of the user's computer that can cause problems. However, self-contained applications are becoming less and less about how you have your system configured and more about what operating system you are running, so be sure to mention that. For added convenience, if you're using the same operating system as the software authors, be sure to use the phrase "if that makes a difference." For example: "I'm running Windows 7 64-bit, if that makes a difference."

* Your Problem is Important - Last but not least, forget about everyone else. The bug you've encountered applies to you, first and foremost. Don't bother looking two or three threads down for a solution, workaround or simple acknowledgment of the same problem; just start a new report thread. After all, the simpler a problem is, and the more people who have it, the more the developers like to hear about it (they get to make the most people happy fastest with the least amount of effort).

And there you have it. Follow these simple guidelines and you too can be a super bug reporter!

He carefully analyzes all the other joke threads people are posting so he can strategically outdo them.

That said, I'm pretty sure there's a mechanic in the game that allows for an Enhancement to boost spread likelihood, and not just Disintegration. Think Chain Induction and the like.

Have you considered preparation?

I've been wanting to organize a MARTy hunt on the test server with some assorted bringers of destruction from the community. If we can get a group of 8 people with builds that like to solo x8 missions with ease, we may be able to trigger the throttle without doing anything wrong. It'd be a fun experiment.

If that's an ending, I'd mark down the writer for failure to complete the essay. I know conclusions are hard, but I'd rather have work turned in late than to omit it entirely.

We should complain that it didn't take the full scheduled downtime!

I mean, if we want to remain consistent.

Ranged knockback should be knockback. You launch a missile at a guy, it's going to push him back. Certain melee knockback (Power Thrust, Telekinetic Thrust) should as well. But certain other melee knockback (Foot Stomp, Head Splitter) should really be changed into knock up.

Remember that there are also powers whose sole purpose is to knock back, like Force Bolt, Power Push, Gale and Repulsion Field.

Personally, on my Dark/Ice Tanker, I hate when my targets get confused by some inconsiderate Plant or Mind contoller. But you won't see me complaining about it because it's just a type of mez that quite frankly isn't disruptive. Knockback falls under the same category.