Spiral Knights - Recon cloak bugs (post-Black Kat update)

Recon cloak bugs (post-Black Kat update)

10 replies [Last post]

Sat, 02/09/2013 - 14:49

Tenkii

Recon animations are glitched for enemy recons. After extensive testing with a friend, we came up with this:

1- Enemy recons disappear instantly when entering cloak (no post-effect nor fade)
2- Sometimes, an attack out of cloak (cloak--attack--cloak) will leave an after-image that isn't representative of the player's position.
3- Uncloak glitches
3a- After taking damage, uncloaking will play back the red 'hurt' flash: so constantly tapping shield will keep replaying the red flash.
3b- When the enemy recon has a status (stun/freeze/curse/fire/shock), uncloaking also replays the text graphic (the one detailing the status on the enemy recon)
3c- If an enemy recon buffers a charge attack out of cloak (ex: hold shield--hold attack--release shield) the charge attack animation will not play, so the recon will seem to just be standing there. I've heard feedback for this using both gun and sword charge attacks, but have not yet heard about bomb charge attacks, though I assume they work the same way.

I love recon and all, but I'd rather not be burdened with the feeling of playing unfairly when I'm playing the same way I normally do.
I believe the original cloak animation might have taken too long (enemies could see the direction you move as you enter cloak), but removing the feedback completely just seems like a bug.

[edit]
-renamed title from Recon glitches (post-Black Kat update) to Recon cloak bugs (post-Black Kat update) for semantics' sake.

Sat, 02/09/2013 - 19:37

Zaffy-Laffy

1. People are suggesting it's not a glitch. A glitch will most likely be unintended, especially if it is new content. Sadly, LD has been here for quite some time, so it is not a glitch.
2. I'm unsure, but I might check it.
3a. I realized that, and perhaps it should be fixed. Now this is a glitch because it follows the recon patch.
3b. I haven't seen that, sadly.
3c. I should do some testing to that...

Sat, 02/09/2013 - 22:01

Shycoboy

*sigh*

Don't think the first one is a glitch, i've been having that too.

Sun, 02/10/2013 - 01:33

Tenkii

I'd love instant no-feedback disappearance and all, but if it weren't a glitch, then things like spectator mode would reflect that as well, right?

Correct me if I'm wrong, but if you watch enemy recons in spectator mode, don't they still fade as intended?

Sun, 02/10/2013 - 01:34

Tenkii

double post

welp, double post.

Anyway, my hunch as a programmer still hints at instant-cloak being a bug.

Sun, 02/10/2013 - 02:10

Zaffy-Laffy

Nope. If it were a glitch, it should have existed since LD first came around.

Sun, 02/10/2013 - 11:43

Tenkii

objection

???
Seiran: Enemy recons disappear instantly when entering cloak (no post-effect nor fade)

Zaffy-Laffy: 1. People are suggesting it's not a glitch. A glitch will most likely be unintended, especially if it is new content. Sadly, LD has been here for quite some time, so it is not a glitch.
If it were a glitch, it should have existed since LD first came around.

...How do you come to the conclusion that glitches only exist from inception of a feature? Prior to the last patch, recons didn't instantly disappear. Recons used to fade from their visible to their transparent states over the course of about half a second. From a recon standpoint, it was borderline infuriating because people would be able to pretty much track your movement as you entered cloak and cut you off with an attack.

However, with all the other things that happened to cloak this last patch, it makes me feel like an in-progress cloak tweak was pushed up. There's absolutely NO feedback when a recon goes into cloak anymore (one frame, they're walking, and the next frame, they're gone), and it's visually jarring enough that it affects other people's gameplay. If instant-disappearance is an intended behavior, then it better be present in all situations in-game where things cloak.

In spectator mode, recons that enter cloak both get a quick fade and leave behind a sparkle animation at the location they cloaked. Why the lack of convention? Obviously, one is bugged.

Sun, 02/10/2013 - 17:35

Zaffy-Laffy

How do I come to the conlusion that a glitch will most likely succeeds a feature? Duhh, will a glitch come out when you do nothing? NO!

No.1 It is different from the original recon cloaking
No.2 It happens to everyone since the patch
No.3 It keeps happening
No.4 It only started to happen since the last patch

Common sense tells me OOO stealth patched the recons, though it'd be more helpful that OOO disclose to us what they changed. Anyway recons disappearing even in spectator mode, I don't know.

Mon, 02/11/2013 - 14:57

Mohandar

#1 doesn't seem like a

#1 doesn't seem like a glitch, and if it is, it should be retained. The aftereffect really neuters recons' ability to disappear.
#2 is likely an unintended glitch, but it seems to add flavor- a recon's forte is misdirection, after all. I say leave this.
#3 are glitches that should be fixed. 3a & b don't affect gameplay too much, but 3c does give recons an unfair advantage. When you are charging a weapon, you should appear to be charging a weapon.

As always, I advocate fixing the max health on Lockdown classes- make the health bonuses +0/+1/+2 multiplied by tier for Striker/Recon/Guardian, and eliminate heart pendant bonuses. The majority of these balance problems stem from Strikers being lightning bruisers rather than glass cannons/fragile speedsters.

Fri, 02/15/2013 - 05:00

Mtax

I've seen that recon cloaking have some changes.
But in real look - it's good. At last recon can chances to do something in fight vs striker.

Mon, 02/25/2013 - 14:56

#10

Autofire

You are experiencing a PICNIC ERROR!

How do I come to the conlusion that a glitch will most likely succeeds a feature? Duhh, will a glitch come out when you do nothing? NO!

You aren't a programmer...I can tell that. When you have a big program like *cough* a game *cough* you have many interlinked functions and parts. Some code for PvE effects PvP and vise versa. You can change one thing in file X, and then it will change stuff controlled by Y. We have no clue because we have no access to the source code. Don't use reasoning like this without having atleast an idea what game makers go through.

Search

Recon cloak bugs (post-Black Kat update)