Rifleman Archive

Suddenly, tonight, my bleeds are not working. I shoot and the combat spam sayes 'you shoot x for xxx points of damage' I'm only a novice rifleman so I still use the mindshot bleed. At first I thought it was my T21, but then it happened with the laser rifle also. It only works sometimes now. I tested it with only having the one shot in the queue and sometimes it would mindshot and sometimes it would just do a regular shot.

Has this happened to anyone else?

Shoshin Agatsu

MindShot1 and MindShot2 are DoT attacks, and even though you fire a shot and it hits the target, the first tick of damage will not occur for 20 seconds. After the initial hit, you will see damage to the Mind pool every 20 seconds for 6 - 9 ticks (depending on which of the two MindShot specials you used).

It's easy to become confused with these specials, if you're not familiar with how they work. I always thought the initial damage should occur when you use the special and not 20 seconds later, but the developers think otherwise. If you are familiar with how they work, and they seem broken, then I don't know what to say. I didn't use either of these specials at all today, so I cannot confirm or deny them being changed/broken.

Yes, I am familiar with the bleeds. I first noticed it because the bleed wasn't happening after I waited. I then noticed the bleed icon was not on the creature and then checked the combat window and saw that it wasn't even being listed as the correct shot type. For example, mindShot1 shows up in the combat window as Distracting Shot. But the window was just showing what I quoted above. It has never happened before. At least, not that I noticed.

Shoshin Agatsu

Mindshot1 is Distracting shot in combat log terms...

Yes, I know Distracting Shot is MindShot1 in the combat log. That's what I was trying to say above. But that was not what my combat window was showing last night. I was trying to say that [i]normally][/i] when mindshot1 works, the combat log shows "Distracting Shot," but that it was NOT showing up that way last night.

Reading my post I see it may not have been clear. So anyway, I know DOT takes time to kick in, I know that Distracting Shot is what shows up in the combat log for MindShot1.

Let me list the sequence of what happened again.
-I shot mindShot1
-Hit peace.
-Combat log says "You shoot savage quenker for 444 points of damage."
-Creature took damage right away.
-Bleed icon did not show up on creatures.
-Creature did not bleed.


IF mindshot1 had worked, the combat log would have said "You use Distracting Shot on savage quenker for 444 points of damage." and the creature would not have taken damage until the bleed kicked in.
If the mindshot had missed it would have said that my mindshot missed, it would not have done regular damage since the peace command comes immediately after the mindshot command.

So, I was wondering what is going on, and will this continue to happen?
Based on the responses so far, I'm guessing this is not happening to anyone else.

Shoshin Agatsu

I haven't used bleeds in some time, but the only time remember thishappening is when i switched targets in combat with a bleed queued up.

on the target switch, it substitutes a regular attack vs the bleed i intended.

i'm sorry, i didn't really quantify when and how this exactly happened at the time; i only remember that i got used to doubling bleed shots when i changed targets.

It has happened to me before, it usually occurs when I change my posture during combat or if I change my target during combat. If I want to make sure it doesn't happen, I don't stack my specials, this way i don't accidentally stand or kneel at the same time my special goes off.

There could be a couple of reasons for this.

If you use a macro they sometimes mess up. If your macro is /attack /mindShot1 / peace you will get the result you had on a slower weapon. If that is the case remove the /attack from the macro.

If you are at peace, the first shot will sometimes not work correctly as a special. This sounds like what you had. I have only seen this if I was moving, or changing targets rapidly. If you pause for a couple of seconds before you engage, everything usually works fine.

I hope this helps some.