I mean, if we don't want teams to have multiple EEs then we should probably not let them. We can all choose to battle for these players. If they're still getting them well then that's on us I guess.

admin should implement the update they said was in the works or announce that there will be no update

Maybe. I still think its bad for the game with the EE thing. I've never had an EE but I still think it sucks the way its set up.

I get the design. It's better for gameplay/competition purposes for the vast majority of the users. And it sucks for those who get hit with multiple EE. As a compromise, I'd leave it as is except for 1 per season. If that's not enough, tough luck.

Posted by fd343ny on 3/9/2017 10:53:00 AM (view original):
admin should implement the update they said was in the works or announce that there will be no update

I generally agree, but from what seble told us, it's not as simple as it sounds. To have them announce early, you have to change the formula, because post-season success is part of the decision. I'd want them to do a lot of testing before implementing this.

Most likely, this is tied into the next big update, including hiring changes and preference adjustments.

As the guy who started this thread, other than a fix (which is what I really want), HOW ABOUT SOME FREAKING INFORMATION?

I know most of us think public questioning is better, and it may be in some cases, but I've found a well-worded ticket to CS gets a quicker, and usually better, response. Pure speculation on my part but I imagine a change, even as simple as earlier notification without additional resources, is a coding nightmare. They may not be ready to commit the manhours or, maybe, they're just letting it play a little longer if it's working somewhat as intended.

Posted by MikeT23 on 3/10/2017 9:09:00 AM (view original):
I know most of us think public questioning is better, and it may be in some cases, but I've found a well-worded ticket to CS gets a quicker, and usually better, response. Pure speculation on my part but I imagine a change, even as simple as earlier notification without additional resources, is a coding nightmare. They may not be ready to commit the manhours or, maybe, they're just letting it play a little longer if it's working somewhat as intended.

I've found exactly the opposite -- pretty much every ticket I've ever sent gets the brush-off "we're working on it." Maybe I need to work on the wording of my tickets. Or maybe the OP's public shaming of WIS is the way to go -- it's tremendously frustrating to me that there are several relatively small fixes that could/should be made, and that there appears to be at least a forum consensus behind, and WIS has done nothing and given no information. That is atrocious customer service.

Often it needs to be bumped up the ladder. If you get a canned response, follow up. I don't like to speak ill of people until they deserve but 1st level support is really bad. I equate it to calling a big corp and getting some dude crammed into a shoebox in India reading from a script.

CS is a terrible job, every ticket is probably a complaint, so I imagine turnover is big at the first level. They just don't know the answers.

OTOH, happy people don't come to the forums to congratulate them on a job well-done. So the forums is the group that are unhappy. As best I can tell, there are maybe a dozen or so that hate EE as is. That's not a big percentage. Maybe many suffer silently but, unless they're sending tickets, CS doesn't know about them. And, IMO, you can't react to 14 people complaining if you have hundreds who are not.

bump