Roaming has become a popular addition to the metagame strategy, wherein one player does not lane nor jungle, but rather simply moves through the jungle/river to initiate ganks on lanes from level 1 and onward, until the teamfight portion of the game begins.
A roamer essentially guarantees that you're either running a solo lane, or two solo lanes if you have a roamer and a jungler. I've also seen a double roamer game played, though this tends to be less effective as enemies who are wise start playing defensively and reduce the effectiveness of your roamers, which put them behind in both CS and levels.
The qualities of a roamer can vary, but the general requirements are that they are mobile, can do burst damage, and have a strong stun or position altering (push, throw, etc.) ability. Taric, Evelynn and Alistar are all very popular choices for roaming. I've also seen Sion and Blitz play roaming effectively, but they were both out of a lack of a jungle spot on the team and normally suit better in a lane.
This strategy is similar to the "double jungle" mindset in that you get three solo lanes, with the exception that there is extra pressure on getting early kills to succeed. A definite risk vs. reward tossup, as successful roamers will quickly catapult your laners ahead in level / CS as well as demoralize your opponents, but unsuccessful roamers will fall just as far behind due to the lack of their presence in the laning phase.
If the mod is still active, that is most likely causing the issue. They did a few UI improvements in this last patch which may have caused the mod to go out of date and isn't compatible with this new version.
Waiting for that mod to be updated to support the new UI updates, or disabling the mod seem to be your only options since you mention you tried repairing the client already.
Best Answer
This is a Bug that has been reported several times in the League forums. Some of the players claim it's a hack although it is most likely related to some form of connectivity issue.
While I haven't experienced the bug myself, closing and reopening the game seems to solve the problem for all players.
One player got a response to the bug and posted a screenshot of the ticket on Imgur.