![[DEV] ISFL Forums](http://dev.sim-football.com/forums/images/emerald/logo.png "[DEV] ISFL Forums"){kind=logo}
+- [DEV] ISFL Forums (http://dev.sim-football.com/forums)
+-- Forum: Player Development (http://dev.sim-football.com/forums/forumdisplay.php?fid=8)
+--- Forum: Point Tasks (http://dev.sim-football.com/forums/forumdisplay.php?fid=92)
+---- Forum: Archived Point Tasks (http://dev.sim-football.com/forums/forumdisplay.php?fid=53)
+---- Thread: (S32) PT 5 - Bad Call (/showthread.php?tid=36431)
RE: (S32) PT 5 - Bad Call - Reno - 12-08-2021
PBE PT
RE: (S32) PT 5 - Bad Call - zaynzk - 12-08-2021
PBE PT
RE: (S32) PT 5 - Bad Call - SouljaBoy2007 - 12-08-2021
In Tijuana's recent loss to Portland, a questionable call helped to swing the tides in Portland's favor. On a 3rd and 7 at their own 37, Portland completed an 18 yard pass. While this is not a positive outcome, the Luchadores and their overpowering defense still had a chance to stop Portland from scoring. Tijuana leads the league in sacks, TFLs, and forced fumbles. Any one of these things could've happened to help Tijuana win the field position battle. Instead, when DE George Fantobens got mad at himself for not getting off the block, the referee assumed that the colorful language Fantobens used was directed at him instead of into nothingness. The referee threw a penalty and despite Fantobens' pleas, the Portland Pythons were spotted a free 15 yards which they used to kick a field goal. This let the Pythons stretch their lead to 7 points, before a Tijuana turnover made it into a 24-10 game at the half. Who knows how the game would've played out without that questionable call.
RE: (S32) PT 5 - Bad Call - C9Van - 12-08-2021
SHL Affiliate
RE: (S32) PT 5 - Bad Call - Dagumpa - 12-08-2021
PBE PT
RE: (S32) PT 5 - Bad Call - Trempale - 12-09-2021
This happend fairly recently in this seasons game vs Portland. The game was tied 14-14 in Overtime. We get the ball first for the OT kickoff. We drive down the field with some big plays. Toledo gets the first 1st down with an 11 yard reception. Demonson moves the sticks again with a 19 yard gain. Followed by a first down by our Bus. Momentum is with us, we're not stoppable. Refs call enroachment against Portland which moves the sticks even further for us. Deviny gets us a new first down on a 2nd and 3 run. Too many man penalty for Portland moves us to the 14! Next up is a 12 yard rush by Deviney, which puts as at the 1 yard line! So that was already very close to a TD!
First rush is by Gus who gets stopped for a loss of one. Now this is where it gets interesting. If you check out the picture below, you'll see that our 2nd attempt was clearly over the line. Apparently the refs didn't see that. We end up scoring a Field goal and it honestly feels like a gut punch after such a good drive in OT!
Portland drive down the field and score a TD, we end up losing the game.... Shit happens ^^
https://media.discordapp.net/attachments/552873557345042432/916421998991798332/IMG_2654.png
RE: (S32) PT 5 - Bad Call - Urq660 - 12-09-2021
SHL Affiliate
RE: (S32) PT 5 - Bad Call - Alcott - 12-09-2021
It didn't particularly matter in the end of the game, as the Yeti came out on top 41 to 30 against the Baltimore Hawks in Week 6 this year, but it was just a sloppy game overall by the refs. After calling two previous false starts against the Yeti, all the players were extremely aware of the snap count and not moving until the ball had first, so for receiver Cole Maxwell to be called for a false start with 8 minutes remaining in the fourth quarter was absolute nonsense. It's hard enough for a receiver to get a false start penalty anyway, seeing as how they need to watch the ball because it's almost always too loud in the stadium to hear the quarterback's cadence calls, so for two of such penalties to be called was really unlikely (the first false start was against aging superstar receiver William Lim)
RE: (S32) PT 5 - Bad Call - Memento Mori - 12-09-2021
SHL affiliate
RE: (S32) PT 5 - Bad Call - allbetsonjames - 12-09-2021
PBE Affiliate