You sure about that?

Considering tab-targetting is broken in it's current form...that type of macro would be a good thing. A lot of macros would just fill the void of unintuitive commands already... such as unstealth/mount.

Ashara's head tentacles are prehensile. Inquisitor's > all.

You're not controlling the character in the book though. There's a difference between being involved regardless of what emotional level or investment that hits with an online character and experiencing a story vicariously as you're reading a book.

Yeah it's much easier to just throw on the tinfoil hat. "placebo effect"...really lol.

As pointed out above, be proactive. If my team doesn't have the ball, I'm looking for the beacon, judging and making my best guess where they are going to go (lets face it, not many options). Of course overload can be done while visible...thanks tips. The only difference is, doing it from stealth is a surprise. Not every opponent is good...and even then, good players aren't immortal. You seem to have assumed I am always trying to kill people in fire, when I said it was an option available and still easy to do. Alternatively you're putting their support into fire, or off a catwalk, separating their healer from the ball carrier. If you're spending more time out of stealth than in stealth as a deception assassin you're already gimping your ability to burst people down because you have lost the energy regen from Dark Embrace. It is to your advantage to begin every fight from stealth.

But why does it matter? Why does it cause such a great offense that someone is relying on automation to do a worse job than you are able to do without it? Maybe they -need it- to enjoy the game. Who are you to decide who can and can't enjoy a game? Ever consider that some addons such as the old healbot were popular because of their accessibility to someone who is disabled? Some features now included in WoW (colorblind mode) were first only possible using mods.

And just as before with other addons that went against the generally welcomed and acceptable standards...they'll cut it out if they deem it to be against those principles. Just like that 3d boss mods thing that used to paint circles on the ground to move to. You still see things from a prohibitive standpoint rather than looking at it objectively. Who cares if some baddie needs a mark over someone's head to identify a healer in BGs? Is it worth not developing an API (even on a limited basis) to get more people what they want? Next argument is going to be banning for voice chat programs because it's "not needed when you can just type in /p or /ops."

I spend a lot of time in stealth, if I'm hunting a ball carrier or their support. I'm not chasing them down from behind, I'm moving ahead of them to spring an attack. Spike their healer, burst them down...overload something into fire or into the pit, electrocute in fire or just being irritating until team respawns catch up. Depends what's going on.

What a useless addon lol. It doesn't auto-target anything btw, it just puts a mark on their head. You'd still have to actually target them manually. There's nothing that will currently auto target for you in WoW. You have to specifically have a macro with that specific name in it ie. /target DaxRendar or /targetexact DaxRendar Yeah people don't realize that automation doesn't lead to better gameplay. Everyone citing cast sequence macros as simplifying or dumbing down the game...clueless.

What addon is that?

You could always estimate speed. You could estimate how much fuel you have based on how much you put in and how far you traveled or for how long. You could tell how hot the oven is by the time it's been warming up for. This is no different than the mentality of some who are against things like damage meters...how often is the argument "just time how long it takes and divide the health by that time for your DPS!" brought up as some sort of half-assed debasement? People need to stop being prohibitive. If you don't like it, don't use it.

I'm guessing you have some dual core system from like 5 years ago. SWTOR isn't truly multi-thread/multi-core capable, if your task manager is showing 50% CPU usage...it's likely that TOR is exceeding that CPU's capabilities on that single core right now. All in all it sounds as if your computer is being taxed trying to play the game, regardless of inherent issues with Ilum etc.

I like when I get free mail from overseas in my TOR inbox.

This is true if you're going in like John *********** Wayne and trying to kill everything in sight. Use the shadows...play it like an operative. Deception is the ganking spec.

Every time someone compares Rift macros to what is actually being discussed I want to throw up a little bit. Just because one awful game couldn't get it right doesn't mean they all are like that. Macros in WoW for example are utilitarian at best and mostly a quality of life "nice-to-have"...not a one-button-plays-the-game-for-me crutch.

Yesterdays patch is part 1 of 3 for addressing the issue. 1.1.1 introduces more changes meant to correct it.

You're not going to get "zomg huge crits!" like some other classes, so if your expectations are to see 8k crits on discharge and maul, you're in for a massive let down. We do however still have a good deal of burst, especially out of stealth. Thrashing Blades is a better option than Charge Mastery as against light/medium targets the benefit of Armor Penetration decreases considerably as their DR on physical attacks is already quite low. With chain shock you're going to be using voltaic strike x2 and shock+discharge when it's ideal. Otherwise it's pretty much Maul for the other physical strike. Most of chain shock's damage will come from energy attacks.

Consonants and grammar are a crutch.

w/e, ignorance is bliss.

..... I don't even know what to say to that...where did I even mention supporting linux? Viral media caused Vista to be a horrible OS? Do you even know what ASLR or DEP are and why they caused so many issues for Vista because they were disabled just to get backwards compatibility to work?

Did you know there's a perfectly reasonable explanation why Microsoft has completely canned Vista support? It's terrible. Did you just compare it to the equally (if not more) terrible XP Pro x64? There are so many driver inconsistencies and issues at the heart of Vista that it is nearly impossible to determine what is causing your problems. Driver issues made worse by the lack of signed 64-bit drivers because at the time microsoft were ***** and wanted companies to pay for them to be signed. Add to that ASLR overrun bugs and issues with memory security and code exceptions. Generally speaking, people running Vista shouldn't be allowed to cite "bugs" or "issues." Sorry.

Zoom in, walk up to it...click.

Memory usage != memory leak. Those sizes are normal, a bit lower than what I get in fact. Your problem (if any) is highlighted in bold and underline for you.

Have you run a memtest lately? What are your system specs, including OS. and to clarify you turned it off not just set it to 0MB for max/min correct?