COL Punishment
|
GCool
Registered RIP Lefty 01-23-2019, 10:00 AMMyLittleHexx Wrote:01-23-2019, 01:31 AMSlashACM Wrote: WhAt AbOuT uPdAtErS Yeah, they should be checking the math every time they add TPE to a player page. Ideally, if you pay attention each week, it shouldn't be difficult to spot the error. There seems to be nothing wrong with how he added shit to his player in his update thread (or at least I can't see it on a quick glance). Could there have been a typo in updating that gave him an extra 1 in a 70-80 stat, resulting in 4 extra TPE?
GCool
Registered RIP Lefty
Sorry for the double post but ... @BadWolf
So I just put the TPE from his first update into the Create a Player tab and it came up as 225 (if you add the 1/4 in scoring after the fact). That's 4 TPE more than 221, which is what he [correctly] claimed on his update thread (155 + 66 -> 221). The error he's being punished for is 4 TPE. So honestly, the only way this 4-point error could have happened is if he was approved at 159 TPE. ...Right?
.bojo
Site Management Just Monika 01-23-2019, 10:24 AMGCool Wrote: Sorry for the double post but ... @BadWolf Based only on your post and looking at your post you linked, that sounds like the case. First update was fine. Possibly approved over the cap.
FlappyGiraffe
Registered nice guy tries hard loves the game
So that's an smjhl ho error then right?
GCool
Registered RIP Lefty 01-23-2019, 10:29 AM.bojo Wrote:01-23-2019, 10:24 AMGCool Wrote: Sorry for the double post but ... @BadWolf And I checked all the other math and it's fine (small caveat: did not check very closely that the TPE was added correctly). So 1. Where's my $5M for completing the updater job? 2. Should COL really be punished if Incite updated correctly for his whole career and it wasn't determined until he hit the cap that he had added 4 extra TPE?
spooked
Registered Posting Freak
Seems weird to suspend a player for an updater issue if that is true.
Should punish GM/Team if they failed to get it fixed while knowing about it though. Why not take their third? Like always ?
.bojo
Site Management Just Monika 01-23-2019, 10:36 AMGCool Wrote:01-23-2019, 10:29 AM.bojo Wrote: Based only on your post and looking at your post you linked, that sounds like the case. First update was fine. Possibly approved over the cap. The updater did point out the error, and either the player or the gm could have made the fix. But it wasn't fixed until today, as the last two posts in the update thread show. But is it really incite's fault? Debatable, but I'd lean towards no since his updates were correct. Probably more the GM's fault. Idk it's tricky.
.bojo
Site Management Just Monika
grok
Registered Posting Freak 01-23-2019, 10:36 AMGCool Wrote:01-23-2019, 10:29 AM.bojo Wrote: Based only on your post and looking at your post you linked, that sounds like the case. First update was fine. Possibly approved over the cap. The punishment isn't just because he had 4 extra TPE. It's because COL GMs were informed Incite had 4 extra TPE, were given permission to fix the error on Incite's behalf, and failed to do that correction. HO and Updater teams are to blame for it getting this far, but they took all the appropriate corrective actions when the error was discovered. COL failed to take their step in correcting the issue, so they should be punished. Whether it was intentional or not, COL's inaction gave them an unfair competitive advantage. I'm confident COL would not have been punished if they would have appropriately corrected the audited player in a timely manner.
GCool
Registered RIP Lefty 01-23-2019, 10:50 AM.bojo Wrote:01-23-2019, 10:36 AMGCool Wrote: And I checked all the other math and it's fine (small caveat: did not check very closely that the TPE was added correctly). While it is an issue that the updater pointed it out on like the 13th and the GM didn't post there for a whole week, this issue has existed since the player was created. Updaters are supposed to audit their teams once a season (I'm going from S25 rules when I was updating still). That means whoever approved the player missed it, and whoever audited Colorado at the end of S44 also missed it. So yeah, my main point is everything was correct from what Incite and the GMs could see -- until it suddenly wasn't. If you backtrack through each update, it's not obvious that a mistake was made. If the updaters were diligent up front, this would have been a non-issue. That's why I don't think they should be punished at all. Also it's FOUR TPE my goodness
GCool
Registered RIP Lefty 01-23-2019, 10:54 AMgrok Wrote: Whether it was intentional or not, COL's inaction gave them an unfair competitive advantage. I'm confident COL would not have been punished if they would have appropriately corrected the audited player in a timely manner. Well he was approved 10/12/18, and the error was spotted 01/13/19; that's 93 days. So I'd say they have til April 16th to respond.
Dangles13
Registered AKA: Dangies
GCool
Registered RIP Lefty 01-23-2019, 10:58 AMDangles13 Wrote: Someone should hire this GCool fella to be an updater or something. Nah, I can't pick this up. I'd rather do podcasts and have my activity level ebb and flow. Also I'm bored as fuck at work right now, so opportunity is here. But honestly if you're getting paid to do this you should be investigating like I did. This took maybe 15 minutes. Sad that we'll pay people enough to not write 5000 words of media a season and make other people wonder why it's not completely automated lmao
.bojo
Site Management Just Monika
How did you reach out to incite and Alaska? I know sometimes people don't know when they've been tagged, like if it was just through the update thread. If you reached out directly I'd understand why this was punished.
BadWolf
SMJHL GM Posting Freak 01-23-2019, 10:50 AMspooked Wrote: Seems weird to suspend a player for an updater issue if that is true. We based our decision on the lumbardi case when he was over cap, trying to stick with what was done in the past. |
« Next Oldest | Next Newest »
|
Users browsing this thread: |
1 Guest(s) |