Shattered Kingdoms

There is already ways to prevent circle and lots of people use guards or pets positioned behind them. Hoping this gets fixed with the next update.

We are not specifically saying that we want circle stab to always be able to work, but as it stands right now, you can't use it if some one is engaged in battle with some one else, not in your group. If they are stunned, or recovering from stunned. In any of those situations you should still be able to circle stab them.

Actually, what I am recommending is what makes the most sense: if you can't initiate combat because someone has a racing pulse (i.e. the hyper-alert message that prevents backstab and hamstring alpha strikes), you should be able to circle.

It's simple. Otherwise, it leads to absurd situations where a rogue can literally do nothing. This fix would also bypass the target/group is not fighting bug, which I have shown multiple examples of - both PvE and PvP.

Rogues are far from being incapable of doing anything in any situation. Just because a pulse is racing means, literally, nothing to any competent rogue.

Despite Hamstring being able to start a fight if a pulse is racing, can't use it. The only thing a rogue can do is use a scroll or do a normal attack.

What you mean to say is: The only things a rogue can do are use...

So, literally, a rogue can do somethings. Rather than Finney's claim that nothing is possible.

When a battle is raging and someone is stunned, and the rogue has to take time to either get out of formation, change weapons to other weapons or scrolls, could mean a healing spell will get on that one guy and therefore will mean nothing.

I don't care about the other incidences, but I do want it fixed that if your group is in battle with the other group as long as the other conditions are met. You can circle stab anyone, and you can always circle stab stunned creatures.

^^This. The rogue class is sub par at group PK, IMHO. Even when circle doesn't "bug" out (as shown in my previous log snippets), you still have to deal with pets or guards positioned behind players before you can circle them.

Not a big deal by itself, but when a necromancer positions a wraith behind them and there are six to eight wraiths in the room - you're pretty much screwed. Your character would know which wraith to target, but as a player you're left guessing whether you should circle 1. 2. 3. 4., etc.

This class suffers from some serious quality of life and targeting issues. I'm all for a high skill cap, but when you're in the middle of a battle with 10+ pets/guards/characters and you get a message that something is blocking your circle/stab/hamstring - there should be a better method of determining what is blocking. Rather than having to randomly guess whether it is 1. or 6.wraith or 1. or 3.warhorse that is blocking.

This class could use a review of its mechanics.

Just sayin'.

If a necro goes into the second row because he's scared of a rogue, then anyone with a reaching weapon can 1-2 round the necro, because necros in the second rank get rocked.

If a rogue is really hard up for starting a fight so he can start circling and he's alone, he can still dirt kick and/or use scrolls, or start combat with an order.

The reason that you can't circle stab someone out of combat is because there's nothing distracted them from the fact that you're sneaking around their formation to put a dagger in their back. It makes no sense in balance or in game logic that circle should be allowed to always be used.

Circle stab is one of the most powerful skills in the entire game. It hits like a truck when used properly: The only thing that IMO should be fixed about it is that the message for someone blocking your target should also carry their NPC name and number (IE: The 5.wraith is standing behind your victim, blocking your attack)

Sorry, when is a stunned character aware of anything?