They are moving in the wrong direction. They squash smaller guilds and beat down non whales. This is just poor business. Would you rather 1 person spend 100 dollars on your game or 100 people spend 10. Not rocket science
This essentially falls into the realm of error trapping in that ET is the most difficult part of software development. You can "What if?" yourself crazy. The devs are out gunned here, trying to out think thousands of players that can think of ways to capitalize on game oversights. My only issue with this debacle is the way the notice is worded seems to suggest players are exploiting the system, when in fact they are playing the game as it was intended based on how the skills are worded. If the update of the hero was flawed, remove it, compensate players for their time and investment, learn from it and takes steps to remove the possibility of it happening again.
Except for the part where they knew about Nute's leader ability being changed for months and failing to stress test the raid, what seems like at all. It's as if they designed a rework for a toon and decided that nobody else would notice that they did it. Also they are absolutely not outgunned here because they have the luxury of knowing what mechanics will be changed before literally anybody else does. They have in theory all of the time in the world to stress test their changes before they make them, but they didn't,
I would not want to be in the monday morning meeting. I'd like to watch it, but not be those involved in explaining how this happened.
Testers have a thankless job. It's probably already been a rough day.
This essentially falls into the realm of error trapping in that ET is the most difficult part of software development. You can "What if?" yourself crazy. The devs are out gunned here, trying to out think thousands of players that can think of ways to capitalize on game oversights. My only issue with this debacle is the way the notice is worded seems to suggest players are exploiting the system, when in fact they are playing the game as it was intended based on how the skills are worded. If the update of the hero was flawed, remove it, compensate players for their time and investment, learn from it and takes steps to remove the possibility of it happening again.
Except for the part where they knew about Nute's leader ability being changed for months and failing to stress test the raid, what seems like at all. It's as if they designed a rework for a toon and decided that nobody else would notice that they did it. Also they are absolutely not outgunned here because they have the luxury of knowing what mechanics will be changed before literally anybody else does. They have in theory all of the time in the world to stress test their changes before they make them, but they didn't,
I would not want to be in the monday morning meeting. I'd like to watch it, but not be those involved in explaining how this happened.
We need that meme of the boss asking how do we "fix" Lugo. P1: "Lets say it was "unintended behaviour"." P2: "Lets say because it wasn't WAI!" P3 "Why do we even need to fix Lugo, it wasn't broken"
This essentially falls into the realm of error trapping in that ET is the most difficult part of software development. You can "What if?" yourself crazy. The devs are out gunned here, trying to out think thousands of players that can think of ways to capitalize on game oversights. My only issue with this debacle is the way the notice is worded seems to suggest players are exploiting the system, when in fact they are playing the game as it was intended based on how the skills are worded. If the update of the hero was flawed, remove it, compensate players for their time and investment, learn from it and takes steps to remove the possibility of it happening again.
Except for the part where they knew about Nute's leader ability being changed for months and failing to stress test the raid, what seems like at all. It's as if they designed a rework for a toon and decided that nobody else would notice that they did it. Also they are absolutely not outgunned here because they have the luxury of knowing what mechanics will be changed before literally anybody else does. They have in theory all of the time in the world to stress test their changes before they make them, but they didn't,
I would not want to be in the monday morning meeting. I'd like to watch it, but not be those involved in explaining how this happened.
We need that meme of the boss asking how do we "fix" Lugo. P1: "Lets say it was "unintended behaviour"." P2: "Lets say because it wasn't WAI!" P3 "Why do we even need to fix Lugo, it wasn't broken"
Remember guys, don't try to think outside the box. Get on with the program to farm your clones and resistance like every other good player has done. Please stop causing waves, it's bad for business.
Remember guys, don't try to think outside the box. Get on with the program to farm your clones and resistance like every other good player has done. Please stop causing waves, it's bad for business.
Exactly, keep taking the red pill guys, it's a really good simulation after all
This essentially falls into the realm of error trapping in that ET is the most difficult part of software development. You can "What if?" yourself crazy. The devs are out gunned here, trying to out think thousands of players that can think of ways to capitalize on game oversights. My only issue with this debacle is the way the notice is worded seems to suggest players are exploiting the system, when in fact they are playing the game as it was intended based on how the skills are worded. If the update of the hero was flawed, remove it, compensate players for their time and investment, learn from it and takes steps to remove the possibility of it happening again.
Except for the part where they knew about Nute's leader ability being changed for months and failing to stress test the raid, what seems like at all. It's as if they designed a rework for a toon and decided that nobody else would notice that they did it. Also they are absolutely not outgunned here because they have the luxury of knowing what mechanics will be changed before literally anybody else does. They have in theory all of the time in the world to stress test their changes before they make them, but they didn't,
I would not want to be in the monday morning meeting. I'd like to watch it, but not be those involved in explaining how this happened.
We need that meme of the boss asking how do we "fix" Lugo. P1: "Lets say it was "unintended behaviour"." P2: "Lets say because it wasn't WAI!" P3 "Why do we even need to fix Lugo, it wasn't broken"
Just as the title suggests, this is aimed at the developers and this thread will most likely get taken down but it still needs to be said. Why is this Nute Jawa squad getting "fixed" this quickly when all of those abilities have been in the game for months. We all know it's a nerf at this point and there is absolutely no reason to nerf them. The mechanic isn't breaking anything, it's WAI based on what the description says it will do, and you are being petty because somebody yesterday figured out a way to use the mechanics you made for this game to play the game. Somebody figured out that Nute can make Jawas deal a lot of damage to only half of the Tank Raid, and they are already being nerfed because you failed to stress test every character in this game in every part of this game. This is unwarranted and unprecedented. There is no reason to do so and we all know it. If you are nerfing Nute and the Jawas then you better nerf Teebo in the Rancor Raid. You better nerf Zylo in the tank raid and you better start nerfing these squads the can solo entire phases of both raids because it is unfair to nerf one and none of the others. This "unintended behavior" is also applicable to so many other squads so you've got a lot of nerve to pull this so fast. At least you didn't wait until people farmed them up to nerf them, so thank you for that at least. Get to nerfing guys.
You can put the games key game mode on auto and solo it, of course they were not going to let that fly.
For 2 out of 4 of the raid phases and even then you have to rely on RNG to get results. Plus to top it all off, nothing about what they could do was broken or mislabeled like Zarris and Zader, it was WAI but the devs didn't like how well it was working so they decided to nerf the already terrible toon back into the graveyard.
You could Solo a whole phase of the games key mode with the game on auto. We all know that's not WAI.
So Teebo isn't WAI then? That's been around for about a year now right. He's able to solo **** near the entire raid, and now that Jyn is available, the Rancor Raid is 100% able to be fully autoed. This latest "fix" stopped people from being able to do only 2 of the 4 phases of the raid, and not even the hardest phases of the raid either.
You couldn't put Teebo on auto.
What are you going to do if this stays as is? You'll put it on auto and go back to having nothing to play but a few arena battles and Galactic war. Look at the big picture. If you want the game to still exist they have to have is actively playing it.
I still have to worry about the hardest half the raid you ****. How is that so lost with you. This was an option to beat the two easiest phases of the raid. You still have to worry about GG in phase 1, and the army of Droids in phase 3. They changed it for absolutely no reason. And yes Teebo can still auto the Rancor raid, and with Bistan and Jyn the Rancor will never have a turn with Teebo
Name calling? Classy.
We all know this isn't WAI.
Who is "we" here? Nearly 80% of the playerbase voted and said that they didn't need a nerf. You are in the minority here by a lot. It was working as intended because they were the ones that changed the ability in the first place to give 50% TM. They knew that it would do that when they released R2 but they didn't do a thing about it until Fugo discovered it and went public with the info.
Just because you want it doesn't mean it's WAI. We all knew as soon as the video came out that this wasn't going to last.
If you care about having new content in this game 6 months from now this has to be fixed.
As an aside, I didn't realize you speak for 80% of the player base.
Who do you think you are? If you can speak for all of "we" I can certainly speak for the 80% of the playerbase that share my view. You're starting to go off on a tangent here with the 6 months garbage, so let's try and stick to the topic, ok buddy. I didn't want Nute because he wasn't up long enough for me to be able to want him. From the videos I watched it was 100% WAI and the devs were the ones who changed his leader ability in the first place so of course it was WAI, they made it that way.
You watched that video and thought "wow that's cool, the devs definitely aren't going to nerf this"?
No because I actually realized what the guy did and looked into it. Funny thing when you realize how game mechanics work like that. Also no because they re made Nute's leader ability when they released R2 so they knew full and well what it would do on the tank raid, and they had plenty of time to have at least one beta tester use this leader ability in the Tank raid
Being a software tester is tough. It's easy to miss one edge case like using Nute and 2 random Jawas in the tank raid.
They can't give us all cheat codes to the tank raid. It was cool to see it happen and kudos to the guy who figured it out.
It's not software testing. This could have been completely avoided it they just told one of their workers to use a Nute Lead in every part of the game and to try out different squad comps. They would have had a head start on Lugo and would have been able to "fix" it before Lugo ever even thought about looking for it.
If you've done any software development you would know that what you're saying is much more time consuming than it seems.
EA makes $316,000 a day. You're telling me that they couldn't hire a team of beta testers to stress test this 1 leader ability with squad comps in the amount of time between Nute's leader update and now? Hell I could have done that for a grilled cheese a coke.
It's easy to see this issue after it's already been discovered.
It shouldn't be up to the players of the game to "discover" these "issues" as you put it, the only thing that was discovered was yet another squad that could get high scores in P2 and P4 of hAAT. Every mechanic in this squad is working as intended, and yet CG decides on a whim to shut it down in record time. Honestly, when was the last time something that was WAI was shut down this fast?
It's an incredibly complex application with an infinite number of scenarios to test and a finite number of testers.
It's not working as intended for 3 toons requiring little investment to Solo the most difficult game modes.
That doesn't matter when you are talking about stress testing anyway. When you stress test your tester go in with only 1 or 2 game modes in mind and they try their hardest to break the game if at all possible and they try to see if there are any ways to make those game modes negligible in difficulty. A good tester can do this in their own within a week. A team of them would be able to do this entire game in that amount of time which is plenty considering the devs had planned a Nute's change most likely months ago.
Stress testing is about load balancing/performance/volume of requests, not finding every edge scenario.
Is context a lost concept with you or something because stress testing in this situation mean the same as beta testing. Just to clarify with you, it means utilizing a character or reworked character in modes of a game to see if the rework or the new character is not game breaking or causes the game to crash in some unexpected way.
This essentially falls into the realm of error trapping in that ET is the most difficult part of software development. You can "What if?" yourself crazy. The devs are out gunned here, trying to out think thousands of players that can think of ways to capitalize on game oversights. My only issue with this debacle is the way the notice is worded seems to suggest players are exploiting the system, when in fact they are playing the game as it was intended based on how the skills are worded. If the update of the hero was flawed, remove it, compensate players for their time and investment, learn from it and takes steps to remove the possibility of it happening again.
Except for the part where they knew about Nute's leader ability being changed for months and failing to stress test the raid, what seems like at all. It's as if they designed a rework for a toon and decided that nobody else would notice that they did it. Also they are absolutely not outgunned here because they have the luxury of knowing what mechanics will be changed before literally anybody else does. They have in theory all of the time in the world to stress test their changes before they make them, but they didn't,
I would not want to be in the monday morning meeting. I'd like to watch it, but not be those involved in explaining how this happened.
We need that meme of the boss asking how do we "fix" Lugo. P1: "Lets say it was "unintended behaviour"." P2: "Lets say because it wasn't WAI!" P3 "Why do we even need to fix Lugo, it wasn't broken"
"Wait, let's blame Microsoft!" "Ummm it's a mobile game, Android/iOs remember?" "Right, right I keep forgetting".
It's obvious now that the players are the ones testing all the 'content' (new toons) that comes out, so when can we stop being beta testers for this game?
You may think this is a sarcastic post, but I'm dead serious.
We've been playing this game for what, 18 months now? Yet we're still waiting weeks and even months for bug fixes and QoL updates that may not even come.
Meanwhile, we get punished with toon nerfs using the gear that takes months to farm. Oh, and remember all those bugs that persist for months and months while they get 'looked at' and 'tested'? Well if the Nutinni fiasco has taught us anything, it's that 'bugs' can actually get addressed and fixed within 24-48 hrs...which begs the question as to why things like Teebo take 6 months (to come up with another PTP toon that uses the same stealth mechanic so it has to get fixed to keep up profits) before it gets fixed.
Constant nerfs, lack of actual content, and the continual release of drastically unbalanced toons is seriously taking its toll on the players, and this is just getting ridiculous.
Generally, it has not been displayed to the playerbase that we are anything more than Beta-testers for this game, and that needs to change if there are any hopes of this game continuing through the end of this year (at best).
Please stop treating the players like Beta-testers.
This essentially falls into the realm of error trapping in that ET is the most difficult part of software development. You can "What if?" yourself crazy. The devs are out gunned here, trying to out think thousands of players that can think of ways to capitalize on game oversights. My only issue with this debacle is the way the notice is worded seems to suggest players are exploiting the system, when in fact they are playing the game as it was intended based on how the skills are worded. If the update of the hero was flawed, remove it, compensate players for their time and investment, learn from it and takes steps to remove the possibility of it happening again.
Except for the part where they knew about Nute's leader ability being changed for months and failing to stress test the raid, what seems like at all. It's as if they designed a rework for a toon and decided that nobody else would notice that they did it. Also they are absolutely not outgunned here because they have the luxury of knowing what mechanics will be changed before literally anybody else does. They have in theory all of the time in the world to stress test their changes before they make them, but they didn't,
I would not want to be in the monday morning meeting. I'd like to watch it, but not be those involved in explaining how this happened.
While we're at it, let's also be real on the Zader "fix". It was most likely fixed due to the fact they probably couldn't come up with another way to fix raid tiebreakers. Almost everyone had Zader, but not Jyn yet. The Rancor is over a year old now and it's still being tweaked?
I can't support this impending nerf. There are too many gates, too many bugs, terrible raid rewards, terrible guild management tools, too much of a rift between the top 1% and everyone else and just a drought of anything resembling enjoyable content. They continue to ignore toons that have bugs which make them unusable, but have to drop an immediate nerf on toons working as intended because it might hurt the whales? C'mon. Then feed a line that this about working as a team, while allowing zylo and zavage to continue soloing p1. Not to mention the THREE players who beat the entire haat raid by themselves? This is just utter garbage.
But at least we might get clone helmets right? (Probably have to farm them at a rate of 1 shard a day and need 700 shards + stun guns, cuffs and carbantis to even equip them)
Also, are we discouraged from spending time experimenting? Spending time getting to know the toons so well that we can come up with fantastic strategies? What, we are to stick to cookie cutter options and not search for unique solutions? Talk about a grey world without hope.
Replies
Please also give credit to the individual for the first known idea of this combo.
https://forums.galaxy-of-heroes.starwars.ea.com/discussion/comment/959387#Comment_959387
@SiranthaAxus
Testers have a thankless job. It's probably already been a rough day.
We need that meme of the boss asking how do we "fix" Lugo. P1: "Lets say it was "unintended behaviour"." P2: "Lets say because it wasn't WAI!" P3 "Why do we even need to fix Lugo, it wasn't broken"
It's done fam and charge your phone
And then out the window.... Lol!
Exactly, keep taking the red pill guys, it's a really good simulation after all
Yes I would like to see that dank meme as well.
https://media0.giphy.com/media/aNtt9T8SqGNK8/giphy.gif?response_id=59226f733aa38499dcaf36aa
That was earlier! I'm at 50% now.
"Wait, let's blame Microsoft!" "Ummm it's a mobile game, Android/iOs remember?" "Right, right I keep forgetting".
You may think this is a sarcastic post, but I'm dead serious.
We've been playing this game for what, 18 months now? Yet we're still waiting weeks and even months for bug fixes and QoL updates that may not even come.
Meanwhile, we get punished with toon nerfs using the gear that takes months to farm. Oh, and remember all those bugs that persist for months and months while they get 'looked at' and 'tested'? Well if the Nutinni fiasco has taught us anything, it's that 'bugs' can actually get addressed and fixed within 24-48 hrs...which begs the question as to why things like Teebo take 6 months (to come up with another PTP toon that uses the same stealth mechanic so it has to get fixed to keep up profits) before it gets fixed.
Constant nerfs, lack of actual content, and the continual release of drastically unbalanced toons is seriously taking its toll on the players, and this is just getting ridiculous.
Generally, it has not been displayed to the playerbase that we are anything more than Beta-testers for this game, and that needs to change if there are any hopes of this game continuing through the end of this year (at best).
Please stop treating the players like Beta-testers.
I would love to be there monday
While we're at it, let's also be real on the Zader "fix". It was most likely fixed due to the fact they probably couldn't come up with another way to fix raid tiebreakers. Almost everyone had Zader, but not Jyn yet. The Rancor is over a year old now and it's still being tweaked?
Where is the guild tickets fix?
Hello Darkness my old friend.
But at least we might get clone helmets right? (Probably have to farm them at a rate of 1 shard a day and need 700 shards + stun guns, cuffs and carbantis to even equip them)
Not surprising honestly.......