(09-26-2022 09:00 AM)SkullyMaroo Wrote:  Every time I refresh the page this thread has new replies. When will this game end?

MAYBE after next year's game, but probably never.

(09-26-2022 09:00 AM)SkullyMaroo Wrote:  Every time I refresh the page this thread has new replies. When will this game end?

This is football fan purgatory

(09-26-2022 09:04 AM)2Buck Wrote:  

(09-26-2022 08:57 AM)Saint3333 Wrote:  

(09-26-2022 08:51 AM)2Buck Wrote:  

(09-26-2022 08:39 AM)Saint3333 Wrote:  We've moved on from the result, it's the lack of understanding of basic rules that is troubling. Even after watching the review and not recognizing that #0 clearly pulled up 3 yards in front of the PR is bias that can't be underestimated for any future discussions of this nature.

App has won and lost games in which I can admit we've been on the good end of a bad call, the SBC refs are known to have a few per game. There were a ton of them in SoCon era.

From the stands at least, there were some suspect PI calls/non-calls against JMU. I'm sure there's video out there that could be scrutinized.

But even if App got that fumble call. There is NO WAY you can project that App would still win the game. Could have been a pick 6 or sack/fumble right after that. Not like there wasn't a demonstrated history of JMU getting to Brice and wreaking havoc.

Again, I get the loss was a tough pill to swallow. I sat there distraught in the first half because I KNEW that wasn't reflective of this JMU team. Like I said on another post, the script got flipped from one half to the other, but no one can say with any certainty that that one play was the cause or catalyst. It may have come on the next play or the next series. But it was coming.

Looking forward to this type of game every year. Would hate to see it turned into a b!tchfest, which by the way many JMU fans are great at so be prepared

You seem to be struggling with the concept of separating a comment that it was a bad call and it costing App the game. You can admit the former without conceding the latter.

True. And I haven't been reading through every post. The issue is, the way this has generally been served up by some is this is the only impactful blown call and App likely suffered the loss as a result. JMU fans are trying to enjoy the victory and some are seeing this constant point as a slight. We're a touchy bunch (not in a pervy way like ODU fans).

If this deflection (referencing other calls) is your admission of a bad call I guess that's as good as it gets.

Hburg's admission of a "grey area" was a step in the right direction as well I guess.

(09-26-2022 08:00 AM)Saint3333 Wrote:  

(09-26-2022 07:48 AM)Longhorn Wrote:  

(09-26-2022 07:40 AM)Meathead Wrote:  Lot of chirping on here from a team that would have almost certainly lost had they not benefited from the worst fair catch interference call in history. The video is very clear what happened there. App would have had the ball at midfield and the game would have been completely different. Look, you guys played fine, you have a good defense and App always struggles against mobile QBs... you get the Dub this time around but win with class.

Call the waaambulance.

Yes, the video is clear. The penalty was not for running into the receiver. It was because the App player did not provide the punt receiver room to make the fair catch unimpeded. It was the right call. Read the rule book.

Please don't. Many here are congratulating JMU on the win.

But in no world can two players get blocked in the back and pushed into the PR (by the returning team).

We can debate how important or not that call was to the outcome of the game, but anyone that understands football would agree that was a bad call. In fact I bet we get an email from the league office today acknowledging that.

He understands how to be snarky and pursues it like it's some kind of coveted, prized award. His understanding of football - not so much. If he did (or had a little bit of common sense) he would reasonably understand that the penalty was the JMU player running full speed blocking the App State player (who was coming to a stop comfortably away from the JMU receiver) in the back forcing both of them into the receiver. The App player was only too close because the was knocked into him from behind. Blocking in the back is still a penalty, right?

Would it have changed the outcome of the game? Nobody knows the answer to that. All we do know is that it was the wrong call on a play that would have resulted in a turnover. Saint3333 is right on this one.

(09-26-2022 09:27 AM)Saint3333 Wrote:  

(09-26-2022 09:04 AM)2Buck Wrote:  

(09-26-2022 08:57 AM)Saint3333 Wrote:  

(09-26-2022 08:51 AM)2Buck Wrote:  

(09-26-2022 08:39 AM)Saint3333 Wrote:  We've moved on from the result, it's the lack of understanding of basic rules that is troubling. Even after watching the review and not recognizing that #0 clearly pulled up 3 yards in front of the PR is bias that can't be underestimated for any future discussions of this nature.

App has won and lost games in which I can admit we've been on the good end of a bad call, the SBC refs are known to have a few per game. There were a ton of them in SoCon era.

From the stands at least, there were some suspect PI calls/non-calls against JMU. I'm sure there's video out there that could be scrutinized.

But even if App got that fumble call. There is NO WAY you can project that App would still win the game. Could have been a pick 6 or sack/fumble right after that. Not like there wasn't a demonstrated history of JMU getting to Brice and wreaking havoc.

Again, I get the loss was a tough pill to swallow. I sat there distraught in the first half because I KNEW that wasn't reflective of this JMU team. Like I said on another post, the script got flipped from one half to the other, but no one can say with any certainty that that one play was the cause or catalyst. It may have come on the next play or the next series. But it was coming.

Looking forward to this type of game every year. Would hate to see it turned into a b!tchfest, which by the way many JMU fans are great at so be prepared

You seem to be struggling with the concept of separating a comment that it was a bad call and it costing App the game. You can admit the former without conceding the latter.

True. And I haven't been reading through every post. The issue is, the way this has generally been served up by some is this is the only impactful blown call and App likely suffered the loss as a result. JMU fans are trying to enjoy the victory and some are seeing this constant point as a slight. We're a touchy bunch (not in a pervy way like ODU fans).

If this deflection (referencing other calls) is your admission of a bad call I guess that's as good as it gets.

Hburg's admission of a "grey area" was a step in the right direction as well I guess.

I'm not going to pretend to know enough about the rule to make a judgement. To me it looked like your guy got pushed into the returner. Did the refs (more than one?) not review the replays? If so, I'd have to assume there's more to it than what we're seeing.

Both sides were gifted by varying degrees of screwups, bad calls, bad luck, poor decisions and poor execution. You guys had home field advantage that resulted in at least 2 JMU drive-killing false starts. This could ping pong back and forth in perpetuity.

There are just some App fans that will always see it as this...

It was a terrible call, which I said from the moment it happened and if I remember correctly without going back I don't think I was the only JMU fan to say so. Blaming the game on that is crazy though. We'll never know what exactly would've happened obviously.

We do know it was 28-10 at the time and JMU, especially on defense, controlled the game the entire second half. We also know JMU took the lead with over ten minutes remaining so it's a major stretch to think we would've run out of time.

The best part of this thread is the idiotic and immature ODU fans trying to talk smack to JMU fans in a thread about their win over App State.

"HEY GUYS, LOOK AT US! WE'RE HERE TOO!"

Almost as pathetic as asking for a game to end early - must be a Norfolk thing?

2Buck, a penalty call like that is not reviewable unfortunately so that option wasn’t available.

(09-26-2022 11:05 AM)Saint3333 Wrote:  2Buck, a penalty call like that is not reviewable unfortunately so that option wasn’t available.

Oof, then that's a tough call real-time with the way bodies are flying around. I could understand a ref from their positioning seeing a defender flying into the returner and thinking it was of their own accord. Should allow replay review on stuff like that. In a case where the returner seemed to otherwise have avoided fumbling, maybe they err on that side. Sucks.

I have to chuckle at the "insufferable JMU fans" lines that Oduh fans continue to push. They get on every JMU thread to talk crap (even after we win!) and want to call us insufferable?! The lack of quality education really shows.

Can't wait to take away the "beat us first" line. Oduh fans are only going to be left with "Truckstop University" lines and I'm fine with that given the irony that truck drivers and lot lizards are about the only jobs an Oduh degree will get you.

(09-26-2022 11:03 AM)DirtyDukes Wrote:  The best part of this thread is the idiotic and immature ODU fans trying to talk smack to JMU fans in a thread about their win over App State.

"HEY GUYS, LOOK AT US! WE'RE HERE TOO!"

Almost as pathetic as asking for a game to end early - must be a Norfolk thing?

Who pissed in your dog chow? I get you y'all are excited about appy screwing this one up but don't go making stupid statements. Its one guy stating the obvious. Calm down mutts.

(09-25-2022 07:29 AM)Duke Dawg Wrote:  

(09-25-2022 06:50 AM)AppManDG Wrote:  

(09-25-2022 12:38 AM)Longhorn Wrote:  

(09-24-2022 11:13 PM)ah59396 Wrote:  

(09-24-2022 11:06 PM)hburg Wrote:  App State was held to just 63 yards rushing.

Sent from my SM-G988U using Tapatalk

Seeing Peoples only get 4 carries really hurt

Yep. Rather like JMU missing its top rusher.

App was basically missing (6 carries yesterday) it's top rusher from a year ago as well. 2000+ yards from '21 had 10 carries yesterday. Not saying that's why we lost, but it sure didn't help. Yesterday's starter is playing with two serious knee surgeries that cost him both seasons. The next guy has 39 career carries (23 at WF) and the 3rd guy had 1 carry going into this game. Simply stating facts, not making excuses.

Fact: jmu was also missing its top running back, who didn’t even suit up
Fact: jmus top rb yesterday, kaelon black, had a severe knee injury in week 2 last season and didn’t play the rest of the year

Sounds like our rb rooms were the same. You are making excuses.

Same RB room....except one only ran for 63 yards.

What about all that talk about JMU lacking the FBS depth, seems "odd" (to put it nicely) that those same fan bases would then use starters being out as an excuse for losing.

Lol....remember the love fest going on when we were getting band together. Thread after thread shows that is done...lol..love it. Now let an outsider come in and boom...

(09-26-2022 11:26 AM)OsageJ Wrote:  Lol....remember the love fest going on when we were getting band together. Thread after thread shows that is done...lol..love it. Now let an outsider come in and boom...

haha. absolutely !

14 teenage brothers fighting every day.

But some stranger comes in the house talking **** and he's going to get a beatdown by those 14 brothers.

love this league! only going to get better as time goes on too.

On a side note has anyone ever confused the Duke Dog with a rat? To add insult to injury my youngest daughter engaged in a 30 minute debate about what the mascot was as we drove down the mountain. At the end she said I'll give you a bear, but that was not a dog. She'll make a "good" lawyer, oxymoron I know.

(09-26-2022 11:23 AM)12thmonarch Wrote:  

(09-26-2022 11:03 AM)DirtyDukes Wrote:  The best part of this thread is the idiotic and immature ODU fans trying to talk smack to JMU fans in a thread about their win over App State.

"HEY GUYS, LOOK AT US! WE'RE HERE TOO!"

Almost as pathetic as asking for a game to end early - must be a Norfolk thing?

Who pissed in your dog chow? I get you y'all are excited about appy screwing this one up but don't go making stupid statements. Its one guy stating the obvious. Calm down mutts.

Proved my point!

(09-26-2022 11:29 AM)Saint3333 Wrote:  On a side note has anyone ever confused the Duke Dog with a rat? To add insult to injury my youngest daughter engaged in a 30 minute debate about what the mascot was as we drove down the mountain. At the end she said I'll give you a bear, but that was not a dog. She'll make a "good" lawyer, oxymoron I know.

oh man, good thing you didn't see the "changes" they tried to make a while back. It was hideous. you see a mouse now, if you saw that one you'd think Mickey Mouse (not Mickey Matthews, but the real MM) was our mascot.

i'm sure some JMU fan on here still has a picture of it. Thankfully, the backlash was so strong and negative they changed it back.

(09-26-2022 11:30 AM)Duke Dawg Wrote:  

(09-26-2022 11:29 AM)Saint3333 Wrote:  On a side note has anyone ever confused the Duke Dog with a rat? To add insult to injury my youngest daughter engaged in a 30 minute debate about what the mascot was as we drove down the mountain. At the end she said I'll give you a bear, but that was not a dog. She'll make a "good" lawyer, oxymoron I know.

oh man, good thing you didn't see the "changes" they tried to make a while back. It was hideous. you see a mouse now, if you saw that one you'd think Mickey Mouse (not Mickey Matthews, but the real MM) was our mascot.

i'm sure some JMU fan on here still has a picture of it. Thankfully, the backlash was so strong and negative they changed it back.

here is the WaPost article on it:

https://www.washingtonpost.com/blogs/dc-..._blog.html

was in 2011

Duke Dog needs his floppy ears back but yeah, at least they didn't keep that hideousness.

(09-26-2022 11:30 AM)DirtyDukes Wrote:  

(09-26-2022 11:23 AM)12thmonarch Wrote:  

(09-26-2022 11:03 AM)DirtyDukes Wrote:  The best part of this thread is the idiotic and immature ODU fans trying to talk smack to JMU fans in a thread about their win over App State.

"HEY GUYS, LOOK AT US! WE'RE HERE TOO!"

Almost as pathetic as asking for a game to end early - must be a Norfolk thing?

Who pissed in your dog chow? I get you y'all are excited about appy screwing this one up but don't go making stupid statements. Its one guy stating the obvious. Calm down mutts.

Proved my point!

So did you.