Wattson's skin "Kupo Power" and its "issue"
Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number RX Vega
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? ModernVerse
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible. - - -
Are you using any software with an overlay? No
Which Legend were you playing (if applicable)? Wattson
Which Legends were your squad mates using (if applicable)? - - -
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. - - -
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Wacky model. Using a certain banner frame (Static Overload) & performing a specific Wattson animation emotion titled "Static discharge"
Did your squad mates also experience the issue? Yes
How many matches had you played in a row before the issue occurred? Plenty
When did this happen? (dd.mm.yy hh:mm) Upon releasing the "Kupo Power" Iconic skin.
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? See the attachment.
What should be happening instead? If a skin is used, those frames & emotion animations must be prohibited to execute\use by the game itself.
Steps: How can we find the bug ourselves? 1. Use the "Static Overload" frame on Wattson with "Kupo Power" skin equipped. 2. Use the "Static Discharge" emotion animation on Wattson with "Kupo Power" skin equipped.
Hello. I've bought the "Kupo Power" Skin for Wattson. It looked cute, but there was a thing I was afraid of: There were NO skins with a dress in Apex Legends before. Therefore, some wacky moves from players can be done. In short, you can look under the dress. As a player, I see this unacceptable, and I hope it will be fixed.
[CM - Edited to remove attached images]
Hey @ModernVerse,
This is something that's been brought to the team's attention from a few others as well, and the feedback has absolutely been passed along.
Thank you for the post making sure we were aware of this situation!