They only pick questions they know the answers to. Like "Will the hatch patch come back?" or "What was the idea behind the legion?" Stuff that either the entire community asks for or makes them seem smarter. I can't blame them for this tho.

@White_Owl said:

@Bug_Reporter said:

@sorrowen said:
Wraith can't break the event lamps while cloaked....

They are too laze to make a new animation for killers, they did one for survivors tho.

Killers use same atack animation, it isnt a surprise that Wraith cant atack while cloaked.

Sometimes I wonder if you guys made of complaining a job. Where have you seen the "new" survivor animation? The animation is the unhooking one.

Because anything that seems like they do more for survivors is more ammo the killers mains on this forum think they can use, it's ridiculous.

White_Owl said:

@Bug_Reporter said:

@sorrowen said:
Wraith can't break the event lamps while cloaked....

They are too laze to make a new animation for killers, they did one for survivors tho.

Killers use same atack animation, it isnt a surprise that Wraith cant atack while cloaked.

Sometimes I wonder if you guys made of complaining a job. Where have you seen the "new" survivor animation? The animation is the unhooking one.

I doubt it, they just throw out updates and expects us to test it and deal with the bull****.

@CaptainCastle said:
not_Queen said:

This is not on the QA team at all. An update to the backend services was the cause of the issue.

QA team would not have been able to test it.

Do they not have an automation suite that engages the microservices? It might not be on the QA team, but if they aren't equipped then msybe the answer is more appropriately "we don't have a proper QA team", right?

I think their point is, that the backend service update wasn't pushed on the QA testbuild, as it probably didn't have much to do with the event update.

I mean the fact that this event alone.
- Dc prevents you from getting the lantern
- It instant respawns and even when red survivors can pick it up.
- They kill themselves lantern goes back to white.
- If the survivors cannot leave with them killer is not rewarded.
- They added nothing to survivor side however the killer side has multiple objectives to try and watch over locate and find. (Gens, Hooks, Actual Moving Live Players, Lanterns, which lantern did which person get from)
- Survivors intentionally booking it across the map to prevent you from being able to break the lantern after hook. (Distance too far they unhook no longer red)

Things simply slipped past.

@Lagoni said:
I think their point is, that the backend service update wasn't pushed on the QA testbuild, as it probably didn't have much to do with the event update.

As someone who is a professional in tech/QA--I'm really confused as to why they think a back-end service update is an excuse? All updates should always be tested before going live, even if they aren't expected to be customer-facing.

Maybe they're right and it's not QA's fault--but in that case, it's an overall team issue and it sounds like there's a massive hole in their process that they need to examine and fix.

@mintchapstick said:

@Lagoni said:
I think their point is, that the backend service update wasn't pushed on the QA testbuild, as it probably didn't have much to do with the event update.

As someone who is a professional in tech/QA--I'm really confused as to why they think a back-end service update is an excuse? All updates should always be tested before going live, even if they aren't expected to be customer-facing.

Maybe they're right and it's not QA's fault--but in that case, it's an overall team issue and it sounds like there's a massive hole in their process that they need to examine and fix.

Sure, we can agree that pushing an update that causes progression loss is never acceptable (especially during a temporary event), but this was about blaming the QA team for something they couldn't have tested for.

@Jdsgames said:

• Dc prevents you from getting the lantern

It clearly states, that you have to escape with the lantern to get the points. If a DC happens (either Killer or you, you don't escape, hence you don't get the lantern points for an escape. Sounds logical, does it? Also, imagine if you got the points even though a DC happened. It could be abused. And it would be, you know it. People would collect laterns and pull the cable.

@Jdsgames said:

• It instant respawns and even when red survivors can pick it up

Why shouldn't it be possible to pick it up, when it's red. Red only indicates that now the killer is able to destroy the lantern. Nothing else was ever communicated.

@Jdsgames said:

• They kill themselves lantern goes back to white.

Lanterns are red, as long as a survivor is hooked. So, it's logical that however the hook is free'd up (unhook, or struggle stage ende) the Lanters go back to glowing white.

@Jdsgames said:

• If the survivors cannot leave with them killer is not rewarded.

The Killer is rewarded for hooking survivors, which is is main objective. What's the problem here? If you want more points, you should raise this issue and ask for more points by hooking survivors.

@Jdsgames said:

• They added nothing to survivor side however the killer side has multiple objectives to try and watch over locate and find. (Gens, Hooks, Actual Moving Live Players, Lanterns, which lantern did which person get from)

It sounds like you're making this up (btw. you forgot to add "keeping track of landing crows and opened chests"). Of course the lanterns were added for both parties (and everybody needs to locate them, not just killers. And if you get hooked, you again have to locate a latern that wasn't already taken or destroyed). Both sides have one more optional objective. Nobody has to do them.

@Jdsgames said:

• Survivors intentionally booking it across the map to prevent you from being able to break the lantern after hook. (Distance too far they unhook no longer red)

Not sure what you're talking about here. Are you saying that survivors are strategically getting lanterns from specific locations that are intentionally spread far away? lul pls.

@mintchapstick said:
Mmm, see. The thing is that I'm not buying that excuse. 'An update to the back-end services' is something that QA can, in fact, test for. I test updates to backend services on staging environments all of the time in my own work. What should be done is that the update is first done on a test build so that QA can do regression testing. If they're not doing updates, even backend updates, on test builds and letting QA at them first, then their development process is broken and needs to be reexamined so that they don't keep breaking the game.

Ye, I work in this sector too, in defining and refining the development process of various projects of my company. And I agree that this should never ever happen, otherwise their development process needs to be reexamined asap: not only you spend time to fix these bugs that should never exists in production environment, you also loose a lot of time in your internal development, and you do not even realize it! Because time = money, this should be the top priority task to address.

@sorrowen said:
Rumor is Freddy can't break them as well

False. Freddy breaks just fine.