Kitsune Knight

Upgrading to Service Pack 3 could have fixed the issue. Also, you REALLY SHOULD UPGRADE TO SERVICE PACK 3. In one week, Microsoft is END OF LIFING SP2 (which means ZERO updates, including security updates!). Service pack 2 was released six years ago, and 3 was released two years ago.

Staying on SP2 is just putting yourself at risk.


A lot of people generally have a lot of state on their computer If I reformatted my computer, it'd be weeks before I was really completely up and running again.

I bet 100 million inf that it is Intel!



Maybe one day, Intel can make some graphics stuff that only sucks... they have a long road ahead of them, though...

By the time the code even TOUCHES the Public Test Server, its already gone through multiple revisions of Q&A.

Also, if they added a powerset to the test server just to try it, if they decide they're not going to push it to live, they'd have to deal with a huge number of now corrupted characters.

Plus, its been said that proliferating powersets isn't just a simple copy & paste, and actually takes a fair bit of work (especially if it's an off combo port).

And if it goes to test, there's going to be many furious players that demand that it must go live.


Nope, just using a little bit of common sense, mixed with prior dev comments on proliferation and the Training Room.

No, low supply causes high prices. If prices were too low, they would go up to compensate, resulting in higher prices (which is how supply and demand works).

If more than a few hit the cap, the Dev's hands will basically be forced. Either they'll have to raise the inf cap, increase the supply somehow (i.e. bump the drop rate, artificially add more to the market, etc), or remove inf from the market.

IMO, the last option is the best, since there's going to be virtually zero inf leaving the market come the next update (removing the transaction fees), which means inflation will spike. They need to create a legitimate (legitimate = something people are willing to use, if not want to use) inf sink, to begin draining at least some inf from the economy (ideally, to cause the total inf in the economy to begin slowly decreasing, increasing the purchasing power of inf). I don't think there's any one way they could do this, but a few different ones (fix prestige conversion, create artificial sellers on the market, etc) might be enough.

Random drops don't reset in such a way.

Actually, they did announce it here.

The amount of notices a user should see should be EXTREMELY limited (with the exception of (un)installing an application, I probably see zero a month). Microsoft tried to make them annoying to tell application developers to stop being lazy idiots that still think they're using Windows 95. Every other operating system vendor has already implemented UAC-like technology years ago, which has been a major improvement for their system's security (next, microsoft needs to force the default account to be Limited so UAC is full effective).

No, it creates a directory that's user/users writable (there's already MANY, including Public and the user's home folder), and set a bit on a single file that tells it to not prompt for UAC and to just run as a regular user (UAC's heuristics notice the 'update' in cohupdate.exe and think it should require elevation). It does not give extra permissions... in fact, it takes them away by not requiring CoX to be run with maximum system access.

And you lose your system state There's a reason Microsoft has worked to limit the number of activities that force a restart.

You also have to trust all your programs completely, then, as they'd be run as full Administrator with 100% access all the time (or you're running as a Limited User and you break a lot of functionality & ease of use)

Your solution: shotgun. My solution: high precision laser that doesn't kill an orphan

At least you aren't a dev, they don't have an excuse

My solution doesn't require a reboot, or lower your system's security

IMO, if you have Quick Recovery, Stamina is quite optional, depending on the rest of your build. If you have a fair amount of -end in your attacks and toggles (which you will if you've heavily IOed out with sets), Stamina would likely be overkill. If you don't want to invest heavily in sets, frankenslotting your powers (mix'n'matching cheap multiaspect set IOs) is a good way to reduce your end usage, without breaking the bank.

That should be 'buff their own Tohit', as accuracy takes places later on in the formula. Defense can only impact Accuracy via impacting Tohit. Once 'tohit' is floored, Defense can have no further impact on accuracy.

It looks like you're using the unsuppressed values of hide (5.625, 5.625, 39.4, unenhanced) instead of the suppressed values of hide (1.875% to all), which would drastically lower your current defense.



Shadow Meld is a good panic button or alpha-soaker power to use.

On Stalkers, it's 75%.

The Defense Soft Cap is the amount of defense that'd floor an even con minion's, that has no extra to hit, chance to hit you (5%). This is considered the 'magic' amount, as beyond that point there's not much benefit to additional defense (beyond enemies with +tohit or -def).

The defense HARD cap is 175.00%. Beyond that value, you can't get anymore defense (quite frankly, if you're still having defense problems at that high, you're royally screwed anyways).

It's the LGTF

That just tells Windows to ask you.


There's two things you need to do to get CoX to work without Administrator access.

1. You need to give your user (or the 'Users' group, if multiple user accounts on the system use CoX) ownership of the City of Heroes installation directory. It's usually installed in C:\Program Files\City of Heroes (32bit windows) or C:\Program Files (x86)\City of Heroes (64bit windows). See this website for a detailed walkthrough (applicable to both Vista and 7).
2. You need to selectively override UAC, so the built-in heuristics won't trigger an automatic elevation due to the 'update' substring in cohupdater.exe. Follow this article using the Microsoft Application Compatibility Toolkit to selectively override cohupdater.exe (in the installation directory you just changed ownership of).

To-da! You now have a completely UAC-free user experience, without horribly crippling your system's security! I'd, personally, like to see this process streamlined (CoX far predates UAC), but I don't think that'll happen anytime soon due to the complexity of the huge preexisting user base.