I am of the understanding that we are not allowed to use wide receivers at running back in this league
Please correct me if I am wrong.
The reason I ask is because Miami is using wide receivers at running back.

It's not because I lost the game that I'm asking because there's no way I can beat that single defensive play they use 97% of the time (238x over the 4 prior games before we played) and pretty much as their only play .

There is a way to beat that defense, barely. It should not be allowed along with several other defenses that do not get the overuse penalty, hopefully that will be corrected in the game engine in near future, I have been posting about it in the TEST league, MFN1. The play overuse is broken and needs to be eliminated. Instead there should be a minimum active play selection and max number of times a play can be used in a game, as a league admin control, same as injury level. Instead of a "penalty" for play overuse, plays are called up to a max and game rules are overidden if they are causing the overuse, then its the next best play based on the algorithm logic.
As to the issue of WR at RB, that is based on the league admins setting for the position matrix, as long as it is open to use a WR at RB , FB, or TE, it will happen.

I'd like to add some things.
I totally blew my D rule vs Miami's primary pass set.
That's on Me 100%.
Miami's got a great team, a great owner, and the loss is mine.

Focusing on specific D plays, as most of us know, is a result of the game environment and not a detriment towards any human owner.
If we as players do not break stuff, the broken stuff does not get fixed, lol :)

@ GDB: honestly - i am still catching up on all the homework i got to catch up in in MFN-1.

I just want folks to know i know it's not a player issue, and that I blew my d rule against my opponents most used set.

I definitely want to know if I can use wr at rb and te, rb at wr and te, and basically - if the position matrix allows it, is it allowed here in paydirt to used that player at any position within that player's matrix.

Back to the OG post:
It used to be that WR's were not allowed at RB.
If that has changed, I will take advantage of - no bones about it.

If it has not.... MIami is using WRs at rb in overrides.

Position matrix covers override slots as well, so if they are using WRs at Rb, then matrix allows it.

You could of course just look at the position matrix.

I have established the "Deebo" rule to allow one wide receiver at the RB position. I have noticed that whenever I am online and can focus on this league for more than 5 minutes that for some reason I do have more receivers lined up as RBs. I'm not why as during the preseason, I actually sat down for about an hour and deleted all my overrides and re-wrote them to update my rosters. IDK why that's the case and I've looked through my overrides and there is only ONE receiver that I have set at the RB position for specific situations.

As to the why WRs are used more than expected at RB in MFN. One reason would be fatigue setting and whether or not a WR is in the RB1-3 rotation on the depth chart. A WR in RB4 or 5 would not get many, if any carries, unless the position fatigue was set very low.

The other would simply be overides. Looking at the Dolphin player stats, the player with the 2nd most rushing attempts is a WR, avg 3.8 ypc, which is the same as the RB1, not that much of an impact other than WRs, even Deebo, do not carry the ball more or near as much as an NFL RB1. And, I dont think WRs get converted much, if at all, in the the RL NFL. I would guess that the WR in question in this case, had been in the RB2 position during most if not all of the games so far this season, based on the # of carries.

Where the Dolphin run stats get interesting is with a WR who has carried the ball 14 times with an avg per carry of 8.7 and long run of 45 yds, the only run further than 20 yds by the entire RB rotation. The speed advantage or "exploit" is demonstrated by that stat and why, in other leagues, the WR is not allowed at RB by the Position Matrix setting. My own opinion, I would prefer that WRs be converted to RB to use in the RB1-4 rotation, but I dont think the position matrix separates conversion from being able to put a WR at RB in the depth chart.

Here are the facts about WR at RB in the NFL, according to G search..........

"Permanent position conversions from wide receiver (WR) to running back (RB) are extremely rare in the NFL, though using a WR as a occasional rushing weapon happens in about 1 to 2 plays per team game. Full-time position changes usually happen before the pro level in college, not during an NFL career"

"6.0 yards per carry on rush attempts, with most non-specialist wideouts getting only 2 to 5 total rushing attempts per season.:

Most, if not all, of the running plays that a WR is used in are reverses and miss-direction plays, which we do not have in the MFN playbooks. If you favor more of a simulation to RL NFL in the current MFN game version, then WR should not be allowed at RB and at least 3 RBs must be active per game. The Position Matrix would need to be changed to prevent it in Paydirt. NFL league is the other league closest in participation to Paydirt, and the position matrix there does not allow WR at RB, TE, or FB. CB is allowed at SS & FS, but no DB is allowed at LB or to be converted to LB, and LBs are not allowed at DE.