Hyperstrike

All right! We had a really decent turnout tonight!

I'd like to thank all the people who teamed with me, plus all the people on the other banner teams for helping lay the smack down on these unholy hellions!

We were able to successfully complete the following.

1: Rikti Invasion (Sharkhead)
2: 2 Eochai (Sharkhead)
3: Deadly Apocalypse (Sharkhead)
4: Scrapyarder (Sharkhead)
5: Deadly Apocalypse (Cap Au Diable)
6: Zombie Invasion (Cap Au Diable)
7: Deadly Apocalypse (Grandville)
8: Eochai (Grandville)

We had one final, unsuccessful run at the banners in St. Martial. We only had about 10 people in-zone. We were STILL able to get the banners vulnerable, and beat the Purple banner down about 1/4 of the way.

Not bad for three hours, at all.
Because of this, we were able to get at least 24 toons their Deadly Invasion badges. Plus several toons got their Zombie Invasion badges in one go (NEVER seen such a small group pulling EB's out at the speed we were).

Maybe in the next week I'll be looking to do something similar Blue-Side.

Vaya Con Ding Dongs!
(Go with the Hostess Cakes my child!)

For those checking this thread.

I'm running just a bit late here. Just got home and found the client needs to update itself.

I AM coming though. So gimme a minute.

By your concept you could be either enlisted or commissioned (maybe even a Warrant Officer, but just being good at killing stuff is kinda hard to find an MOS for in the military).

Take my PB. He was an absolute hellraiser. He maimed several people in a bar fight and was given a "Go to war or go to jail" ultimatum from the judge and joined the Marines. Right in time for WWII.

Surprisingly enough, he fit into the Marines line a fist in a glove. And the war gave him a GREAT outlet for his more antisocial tendancies.

About the time he was wounded on Iwo Jima, a Peacebringer came crashing to earth, his old host dying. Then, the usual thing happens between a kheldian and their new host and VOILA! Peacebringer with 'tude.

He spent the next 60-odd years as part of a special ops program before being forcibly retired with little more than cosmetic aging (looks like he's in his 50's-60's, but has the fitness of a 20 year old). Moving back to Paragon City, he was aghast (and not a little pissed off) with some of the changes that had come to "his" city (if he could, he'd give the collective superhero population a smack upside the head for letting it get so bad, and as for the villains themselves...you don't wanna know).

So, he's basically having a "Get off my lawn" moment with the entirety of the criminal population of Paragon City.

None here.

Had one on Freedumb. "Americum Dream"

Americum is a somewhat prevalent misspelling of Americium.

Apparently it offended someone and got generic'ed.

Had CS convert it to the corrected "Americium Dream".

And NO, it wasn't a scrapper or a tank. It was a Kin/Rad.

The whole thing is, while there are lots and lots of gradations and delineations in military groupings and ranks, the reality is, it's seldom this simple.

There are tons of considerations and special cases involved (back in the early 90's, the Physicians Assistants in the Army Medical Corps had a transition from Warrant Officer Status to Commissioned Status. So you had a lot of Warrant Officers becoming Liutenants with LOTS of time-in-grade).

Depending on unit type, size, etc, you can see all sorts of leadership structures.

The medical clinic I worked at while enlisted had a Full Bird in charge of the clinic of about 12 doctors and PAs, plus about a dozen enlisted medics, plus some NCO management. Yet all the enlisted belonged to the medical company on the post, which was initially run by a captain, who was then replaced by a Liutenant. The urgent care center on post was overseen by a captain, with the medical clinic there run by yet another Colonel, with the entirety of the USA MEDDAC run by a General.

And the Detachment I worked at in Korea was run by a captain, had 4 doctors, 3 PAs, and about a dozen US military personnel and half a dozen KATUSA. Run by a captain.

Depending on what the unit was doing it could be lead by just about any NCO rank from Sergeant on up, or could have a commissioned officer directly in charge.

1: You'd never HAVE to use them.
2: If they're documented programmer codes like a console game, ones that aren't found and killed, then they technically aren't "Cheat" codes.

Would I use them? Maybe. If I had evidence that everyone was.
More likely than not, I'd just solo a lot more than I already do.
More than likely, I'd just quit playing the game after a while.

Sure, there'd be a wicked little novelty, like when the new mission TP could get you into level-locked zones. But after a bit, it gets old.

Friday night, starting around 9PM Eastern (8PM Central, 7 Mtn, 6 Pacific) I'm going to be pulling out my 50's red-side to do banner runs for people who haven't gotten them yet.

If you need your red-side banner badges, or know someone on Protector who does, point them at this thread and/or reply yourself.

I'll begin assembly in Sharkhead at quarter to nine. I'd like to get at least two good teams together (preferrably three). And, as long as we have enough people, I'll keep running banners so you can get them on as many alts as you can manage.

1: How much RAM do you currently have?
2: What other major memory hogs do you have on your system?

Currently I play on a system with 8GB of RAM. The game sucks up about 1.6GB most of the time.

While I do crash out on occasion, most of the time I'm fine. Usually crashes come shortly after extremely heavy usage (zone raids, etc).

Short answer for Multi-core and hyperthreading with an analogy.

Multiple cores allows you to work on multiple tasks simultaneously.

Hyperthreading is a technology that allows you to keep individual cores busy by interleaving multiple processes in the execution pipeline, instead of merely completing one task at a time in a serial fashion.

These technologies don't make your processes run FASTER than a single core processor of the same clock speed.

What they do is prevent the programs from slowing down due to a very resource-intensive process hogging the processor.



Think about a fast food restaurant with only one checkout lane. It goes along as fast as the cashier can take care of his customers. Now what happens when one of the customers has a difficult order or decides to be a bipedal donkey? The line slows down.

This is a single core, non-hyperthreading machine.

Now imagine if that register had TWO cashiers there. So one cashier takes an order and goes to run and fulfill it while the second casheir deals with the next guy in line. And if you get a difficult customer, the person taking care of him steps to the side and lets the next person get waiting on by the co-worker.

This is a single core, hyperthreading machine.

Now think about a restaurant with 4 checkout lanes. Each processes customers as fast as their respective cashiers can run them down.

This is a multi-core non-hyperthreading machine.

Now think about a restaurant with 4 checkout lanes and two cashiers at each register.

This is a multi-core, hyperthreading machine.