(08-18-2017, 11:24 AM)7hawk77 Wrote:My proposal.

For every time a team played the hawks while this was happening. They get to increase their TE attributes by 160 TPE the next time they play the hawks until the number of games the hawks did this against said team equals the number of times the said team increases their own TE attributes.

(08-18-2017, 10:17 AM)37thchamber Wrote:I'm not so sure...

If this was the case, then wouldn't his player page have been updated by an updater since, and therefore have the "last edited by..." line?

Or are we suggesting that in the brief window between being someone approving the build, and the thread actually being locked, he went back and edited the initial post? I mean, that's entirely possible, but I dunno if there's any way to prove it. And without any proof, I don't think it would be right to call this cheating. If we do, then ANY mistake like this will have to be treated the same way, and that's madness.

Again, not saying you're wrong. I just think we should be careful about how we react to this.

(08-18-2017, 09:17 AM)37thchamber Wrote:I'm not so sure...

If this was the case, then wouldn't his player page have been updated by an updater since, and therefore have the "last edited by..." line?

Or are we suggesting that in the brief window between being someone approving the build, and the thread actually being locked, he went back and edited the initial post? I mean, that's entirely possible, but I dunno if there's any way to prove it. And without any proof, I don't think it would be right to call this cheating. If we do, then ANY mistake like this will have to be treated the same way, and that's madness.

Again, not saying you're wrong. I just think we should be careful about how we react to this.


Uhhh... I never suggested keeping him around. I actually said suspension, reduction of TPE and even retirement would all be fair. Calm down.

I'm mostly concerned about the idea that this looks like an error which should have been caught at multiple stages, but wasn't ... and yet people are talking about this being deliberate cheating without any proof, and talking about punishing people for something we don't know was actually a violation of site rules.

(08-18-2017, 09:28 AM)124715 Wrote:That's pretty extreme (although it would be 110 TPE) although it makes perfect sense. The problem is, me plus 110 TPE is 340 and Maddox plus 110 TPE is 430. Both of those are higher than our #1 WR, so what's to stop us from lining up at WR?

Unless this is what you had in mind.

(08-18-2017, 11:31 AM)7hawk77 Wrote:Honestly that was my point in pointing it out. It feels incredibly imbalanced to do something like that, yet it's completely "fair". I'm unsure how this should be handled but this situation definitely gave the hawks an edge and so again, the player needs to be corrected but the team also benefited from it... therefore they need to have some kind of punishment.

An easier solution is to make them start a TE with subtracting the TPE worth of attributes from their TE, but that might be even more imbalanced.

Not really my call, or my problem... just figured I'd point out stuff that makes for interesting discussion.

Also, I have maddox in fantasy. Lets go with my first suggestion and then start him at WR#1. Kthx

(08-18-2017, 11:17 AM)37thchamber Wrote:I'm not so sure...

If this was the case, then wouldn't his player page have been updated by an updater since, and therefore have the "last edited by..." line?

Or are we suggesting that in the brief window between being someone approving the build, and the thread actually being locked, he went back and edited the initial post? I mean, that's entirely possible, but I dunno if there's any way to prove it. And without any proof, I don't think it would be right to call this cheating. If we do, then ANY mistake like this will have to be treated the same way, and that's madness.

Again, not saying you're wrong. I just think we should be careful about how we react to this.

(08-18-2017, 04:30 PM)To12143 Wrote:there is no way to know how long it took for the thread to be locked

(08-18-2017, 04:40 PM)124715 Wrote:his player page wasn't edited because he did not claim any TPE in his updates.

(08-18-2017, 11:40 AM)37thchamber Wrote:Well, the thread lock is in the moderation log, right? So the window is the time between his "fixed it" comment, and the lock action in the moderation log... right?

If there was a way to see when he edited the post, that would put all of this beyond doubt, but I don't think that's stored anywhere that's easily accessible... it's possibly in the forum dbase (it's been a long time since I used invision, tbh) but I have no idea if anyone has access to it ... though I'm guessing no, since this appears to be on a 3rd party host site rather than server space owned by someone in the community.

I'm seriously trying to understand how this happened too. Can't suggest solutions or preventative measures if I don't know what caused the problem in the first place :/

(08-18-2017, 11:42 AM)124715 Wrote:The window is the time between the post Noble made "Approved Welcome to the league" and the moderation log entry. It's incredibly likely that it's zero, as there is an option to close the thread immediately after posting.

I'll check it now.