Sure, it’s nice to take two of three from the White Sox, but the last thing you want to see is Danny Duffy exiting just three batters into the game.

Not good. Not good at all.

According to the Royals website, Duffy felt a “twinge” in his elbow on his second pitch of the game. He lasted 11 more pitches before he was pulled.

The warning signs have been there… He had a start skipped at the end of April and in his return against the Yankees on May 3, Ned Yost said Duffy, “couldn’t command his curveball at all, but he was overpowering with his fastball.” This jives with an elbow problem… The pitcher with a sore elbow has issues with location. Velocity isn’t usually affected. Indeed, much has been made of Duffy’s velocity this season. According to PITCH f/x data collected by FanGraphs, Duffy’s fastball is averaging 95.3 mph this season. That’s second only to Stephen Strasburg. (Impressive, although we have to note prior to Sunday, four of Duffy’s five starts have been at home, where the radar gun runs a little on the warm side.)

Anyway, after having difficulty commanding the curve in his first start since being skipped, Duffy really struggled in his next outing. Against the Red Sox on May 8, he walked five and consistently missed his spots up in the zone. He threw 102 pitches, but couldn’t get out of the fifth inning.

Then Sunday happened.

Now Duffy is back in Kansas City where he will get an MRI on the elbow. We hope for the best, but it’s likely he’s been dealing with this issue since his start against the Blue Jays on April 22. That start was like his outing against the Red Sox… Duffy walked five and couldn’t get out of the fifth inning while throwing 113 pitches.

I hope I’m wrong, but I don’t think the MRI is going to bring good news. Best case scenario is a DL stint where rest is the prescription. Worst case… I’m not going to go there right now.

— The Duffy issue overshadows a late inning outburst where the Royal bats went berzerk hanging nine runs on the Sox in the final third of the game. Is it weird that the Royals have yet to have a double digit scoring game this year? Seems so. On Sunday, a ninth inning explosion where the Royals scored six runs and pushed their game total to nine, matched their previous high scoring game – a 9-11 loss against Cleveland. That was in the season opening homestand we no longer discuss.

The Royals didn’t have much life before Johnny Giavotella pinch hit for Chris Getz in the with two on and two out in the seventh.

For the record: I would much rather see Gio in the lineup instead of Getz. However, Getz has provided some value at the plate this year. He’s not a long term answer, but why not let him play everyday – even against the lefties. On the other hand, it doesn’t make any sense to call Gio up and not play him at least five or six times a week. But this is the Royals we’re talking about. Hardly any of their roster moves make sense. You already have Irving Falu up as your utility infielder, so why bring up another second baseman? It seems you either play Giavotella or find another platoon partner for Getz.

(Meanwhile, doesn’t all of this render The Yunigma irrelevant? Just a dreadful signing by GMDM and company. Actually, to call it dreadful doesn’t do it justice.)

— Yosty finally got around to shoving Eric Hosmer down in the batting order. About time. Hosmer got the day off in the finale of the Red Sox series to allow for two consecutive days away (the off day between Sox series) which made sense. Give him a mental break and a chance to simply think about getting in some work. Just like it makes sense to drop him in the order. Give him a few days with a different kind of look in the lineup and see what happens.

I know there’s a growing set of the fan base that advocates a trip to Omaha for Hosmer. I disagree. He showed last summer he’s a major league first baseman. Yes, this is a painful slump, but he needs to figure out how to work himself out of it at the major league level. He scorched Triple-A pitching last year for a month or so and more than held his own in the bigs.

Besides, don’t forget the guy still has a .171 BABIP. That number hasn’t moved in the last week. His strikeout rate is down. His walk rate is up. He just needs to have some of these hits fall in. They will.

— Jeff Francoeur hit his first home run of the year. Our long, national nightmare is over.

— Naturally, Luke Hochevar went out on Saturday and tossed seven innings of three-hit ball, walking a single batter while striking out five.

In my post from Friday, I noted that Hochevar’s issues were with his slider and how his release point shifted from the second half of last year. In the game on Saturday, his release point was fairly consistent with where it has been all season. And according to PITCH f/x, that was a relatively flat pitch. In fact, of the 21 sliders he threw, seven were put in play and five were fouled off. Hochevar didn’t get a single swing and miss with this pitch.

In this start, he recorded nine ground ball outs against seven fly balls. Hochevar lived around the plate and the Sox were up there hacking. On Saturday, it was a perfect storm of location, aggressive plate appearances and the damp, rainy afternoon.

— The Royals are 10-6 since that losing streak we don’t discuss.