Jellydonut

Because Distracting Shot would generate more threat and no hunter should be using Arcane Shot for dps (imho). Both turn on Auto Shot in any event.

Thanks for the reply Raz. Seems like I'm out of luck for a one-press solution, but I agree the two-press stop casting macro is not a terrible alternative. The purpose of this is a "pull shot" consisting of rank 1 Arcane Shot and nothing further. Instant and thus castable on the move, low aggro generation, low mana use. Good for pulling mobs into traps or for pulling in general when for whatever reason the tank can't (or won't). There may be other reasons for wanting to turn off Auto Shot, but that's what I had in mind. While I've got your attention though, I wonder if you could answer another question. I'm intrigued by your "situational sting" macro, and wonder how it could be modified to behave like this: if the target is a player character who uses mana, fire viper sting; if the target is a player character who does not use mana, fire scorpid sting; but if the target is an NPC, fire serpent sting. I've got some ideas on this I'm going to try - will report results. The purpose behind this of course is that in the PvE setting, with rare exception, I don't think using viper or scorpid is particularly effective and would rather just dot the mob. But in the PvP setting the switch up seems useful. This would provide an "all stings on one button" solution.

Tried the the stop casting script and it doesn't work, at least not in this context. If placed before the shot command, then the shot goes off as normal and initiates auto shot. If placed after the shot command, then it interrupts the whole thing and nothing is fired (get "interrupted" message). As to the second part, appreciate the suggestion but I'd rather just go with ClearTarget under those circumstances. Edit: /script SpellStopCasting() stops ALL spells and shots from being cast. What I basically need is the script that would stop ONLY Auto Shot. I've tried /script SpellStopCasting("Auto Shot") but that doesn't seem to work. Further edit: I understand what you mean now by "toggle" with the stop casting script, but I'm looking for a one-press solution. I have Auto Shot separately bound, so I can always stop it with another key press and not need a macro.

What's the command to turn Auto Shot OFF (or not on to begin with)? For example, I want to cast Arcane Shot rank 1 and NOT have it followed up by Auto Shot. I've done a ton of searching and the only thing that semi-works is: /cast Arcane Shot(rank 1) /script ClearTarget() But I'd rather not lose the target (adding /script TargetLastTarget() basically undoes the ClearTarget and makes Auto Shot shoot, I assume because of the delay). There has to be another way to keep Auto Shot from firing. Edit: In your "General Shots" section you list macros for initiating Auto Shot alongside other shots, which I don't understand because, with the exception of Scatter Shot, using any other shot automatically initiates Auto Shot. What am I missing?

Oops, spoke too soon - server crashes less than 24 hours after last patch. And it crashes when? 2am US EST, 11pm US PST, with like 4.5k people on. But it will be fine in a few hours (in time for the Chinese) and will stay that way through the EU peak of about 7k players before crashing again in US evening tomorrow.

Victim cult? Other than being a white male (and American), I don't fit any of your so-called "stereotypes" (upon which, btw, discriminatory constructs are based). But, it was mostly said in jest anyway (that ":P" is a thing called an emote meaning I was being cheeky or playful - guess you didn't know that ;) ). The main point is that the server is now stable. Coincidence?

Unfortunately it's a lot more complicated than the Ely-ZK merge. You've got different server types and different patch versions involved. You want to force everyone onto a PvP server? You want to roll everyone back to patch 1.6? People would scream bloody murder. There are no good options when it comes to what to do with Anathema and Darrowshire. The people there made their choice, now they live with the consequences (yes the same could be argued of people who rolled on ZK, but again there was a viable solution to that situation).

You realize you're guilty of at least 5 forms of discrimination with that post? :P Anyway, remarkable how stable the server has been since the "theory" of an anti-American conspiracy was raised isn't it? <straightens tinfoil hat>

From my own experience not so sure with NPCS but definitely notice it with players, very annoying when hordes pop practically on top of you :P. Somewhere there is a post from a staff member acknowledging that they reduced view distance in response to performance concerns due to population (which would then explain the PC aspect at least). Just because the game is old doesn't mean it will perform well on the latest hardware/software (assuming that is even being used). Sometimes the opposite is true due to compatibility and other issues.

By the way, notice that the server has been up and stable now for 10 hours. That took it through prime-time in China, and its now prime-time in Russia. I predict that it will make it through prime-time in most of Europe, and then BOOM.

Which is why they don't put anything here - they don't want people to see and/or be able to track the crashes. Using Discord gives them an "out" to say they ARE communicating about it, but it certainly is the least transparent means.

Thanks for helping to make my point.

And when, exactly is this so that we can avoid this time like the plague?

You're the one who is "angry". I said what they are doing is "logical" - no hate. And my "theory" is based on an objective observation of facts as well as a basic understanding of human-nature, which you seem to lack.

You obviously missed my reply to your post were you suggested I thought they were "evil" and "torturing". I don't hate them at all. I'm just not a clueless fanboi.

No, it's the same hat ;). Stick your head in a new patch of sand?

Also, stop being so GD naive. Anybody who honestly believes that they do this purely "for the love of the game" with no personal benefit is just plain stupid.

Thank you for helping to make my point.

You misunderstand. I never said they are "evil" or are doing this to "torture" people. In fact, I think what I suspect they're doing is completely logical (maybe not ethical or honest - but logical). And I'm here because this is the only vanilla wow server worth playing on, despite its faults.

US evenings tbs.

Yea from where?

The majority of crashes happen between like 8pm to 3am US EST, which would be 5pm to 12am US PST. It's the perfect window if you're trying to effect as much of the US as possible. Very few people from eastern areas of the world playing then.

That's the point - they want people (or certain groups of people) to leave. Patterns don't lie, and there are certain patterns to this. Watch closely and you'll see them.

Mornings where? Morning in China = evening in US. The server doesn't start "freezing" like this until most of the people playing would be in the US. They know where their bread is buttered.

It's crashing multiple times per day, and apparently the only way to know (based on GM responses to other forum posts) is to log into their Discord and have a GM/moderator confirm it. Obviously they don't want transparency on just how unstable the server is right now. Either that, or (my suspicion) they are purposely sabotaging the server during US evenings (most of the crashes seem to happen then). Rarely does it crash during what would be prime-time for China, Russia, and most of Europe, despite the peak load being much higher during those times.