GibsonGate
![[Image: XSfVUgo.png]](https://i.imgur.com/XSfVUgo.png)
Hank Winchester (S25 - Current) - Scrub
Angus Winchester (S1-S12) - 4x Ultimus Champ - #2 Career Sacks - Hall of Fame
Cooter Bigsby (S14-S23) - S23 Ultimus Champ - #4 Career Yards - #4 Career TDs - 2x MVP - Hall of Fame
I think the player should be suspended for the remainder of the season/playoffs and not be eligible for any season awards/pro bowl. He should also obviously be reset to 50 TPE for S3.
I do not think the team should be punished unless there is definitive proof that they were involved in this (which I strongly doubt is the case). It would set a crazy precedent where the team is responsible to check all of their players update pages prior to Saturday updates to make sure no one slipped in some extra TPE. Even Paul said he accidentally slipped 2 TPE into an update, should the Liberty be punished for that too? (08-18-2017, 01:07 PM)Kristy95 Wrote:To add to what the others said, there is also a huge benefit for the Hawks even if it was an error. That doesn't change the fact that a player played for 11 weeks, 5 of which he ended up in the team of the week, so clearly he helped the team win and that is irreversible now.ROIDS (08-18-2017, 06:10 AM)adam2552 Wrote:I think the player should be suspended for the remainder of the season/playoffs and not be eligible for any season awards/pro bowl. He should also obviously be reset to 50 TPE for S3. There is a difference between 2 TPE for a week and 120 TPE for 11 weeks.
The worst part, is, who's fault is it? There's no one to punish. IMO Gibson needs to be removed from the game after he plays another game. But how can we be sure this didn't happen with other players? Or won't happen again?
(08-18-2017, 03:00 PM)To12143 Wrote:It's hard to see such a sizable mistake just slipping by everyone involved with the team.In the absence of evidence to the contrary, it appears as though that is exactly what happened, though. Meaning the solution is to put tighter controls and checks in place to prevent it happening again. Why is there any call to "punish" anyone? It makes no sense. There's nobody to punish. If there was some suggestion that it was a deliberate attempt to circumvent the rules, or unfairly benefit a team then sure, there should be a punishment... But that's not the case here as far as I can see. (08-18-2017, 03:07 PM)Kristy95 Wrote:To add to what the others said, there is also a huge benefit for the Hawks even if it was an error. That doesn't change the fact that a player played for 11 weeks, 5 of which he ended up in the team of the week, so clearly he helped the team win and that is irreversible now.Yeah, the Hawks benefited, nobody is denying that... but unless you're saying we should re-sim the entire season so far (lol) there's nothing we can do about that. Any other action against the Hawks would be to punish them for something outside their control... Which is, frankly, bullshit. (08-18-2017, 03:10 PM)adam2552 Wrote:I do not think the team should be punished unless there is definitive proof that they were involved in this (which I strongly doubt is the case). It would set a crazy precedent where the team is responsible to check all of their players update pages prior to Saturday updates to make sure no one slipped in some extra TPE. Even Paul said he accidentally slipped 2 TPE into an update, should the Liberty be punished for that too?This is the point I'm trying to make. I impersonate a programmer for a living
Father of the League Wiki • Friendly Neighbourhood Angry Black Guy™ • NOT British
Originator of the Sim League Cinematic Universe (SLCU)
Super capitalists are parasites. Fite me.
Alternatively, if you agree, you can support a grassroots movement dedicated to educating and organising the working class by buying a digital newspaper subscription. Your support would be greatly appreciated. (08-18-2017, 09:18 AM)37thchamber Wrote:In the absence of evidence to the contrary, it appears as though that is exactly what happened, though. Meaning the solution is to put tighter controls and checks in place to prevent it happening again. The thing is this is obviously something that got by at least the updater who originally updated, and at worst this is a moment to make sure the updaters know how to do their job properly and what to look out for in false TPE claims. I'm not saying there should be any sort of punishment, it's just weird that a mistake like that passes through unnoticed. [div align=center]
![]() ![]() [div align=center] (08-18-2017, 10:15 AM)Kristy95 Wrote:There is a difference between 2 TPE for a week and 120 TPE for 11 weeks. I just think the burden of update accuracy shouldn't be a GM responsibility. If it's not the team's responsibility how could they be punished for it. This, to me, is more akin to a player taking steroids in baseball. Teams don't get punished for a player's bad decision. You could make the argument that the Hawks should have seen his attributes and stat output known it wasn't right. But the same goes for when scrawny guys in baseball suddenly start hitting 50 homers a season...
So weird that this has slipped through; I think I screwed up my update the first 3 times I did it (often to my own detriment) and the updaters did a great job of catching it.
This really isn't on the Hawks, even if I selfishly want it to be. Only thing that you could do beyond dropping him to 50TPE would be to "suspend" him for the rest of the year and make the Hawks pick someone else up, but I'm not sure that would really make any difference. (08-18-2017, 07:54 AM)37thchamber Wrote:Considering this appears to be a clerical error, who are the FO supposed to be coming down hard on? I meant the player, not the Hawks as a team. My belief is that the player should be removed immediately. |
|