Okay... Like many, I think that the number of radiant quests between major missions is significantly short; you just meteorically rise to the top with so few little jobs between.

I think I have identified what controls it, but I need help altering it. Being completely uninitiated to Papyrus (just now getting over the "pensively poke it and recoil quickly in case it bites me" stage), I'm not quite sure what to do. The script in question is "CompanionsHousekeepingScript" appended to quest C00.

Lines 1003 thru 1023 look like they control it:

	; check to see if it's time to start the next story quest	bool startedStory = False	if	 (C01.GetStage() < 1)		; count		if (RadiantQuestsDoneInCurrentSegment >= RadiantQuestsUntilC01)			StartStoryQuest(C01)			startedStory = True		endif	elseif (C03.GetStage() < 1)		; count		if (RadiantQuestsDoneInCurrentSegment >= RadiantQuestsUntilC03)			StartStoryQuest(C03)			startedStory = True		endif	elseif (C04.GetStage() < 1)		; count, also min level		if ( (RadiantQuestsDoneInCurrentSegment >= RadiantQuestsUntilC04) && (Game.GetPlayer().GetLevel() >= C04MinLevel) )			StartStoryQuest(C04)			startedStory = True		endif	endif

However, the only other instances of the text string "RadiantQuestsUntil" (shared between all three "Until" vars) are up higher, in lines 168-170 where I assume is where all the vars get declared:

int property RadiantQuestsUntilC01 autoint property RadiantQuestsUntilC03 autoint property RadiantQuestsUntilC04 auto

Soooo... where are these variables assigned a value?

Okay, I figured out how to fiddle with the quest vars' default values... but it seems that I am past the point of being able to alter it on the plugin level. Are there any console commands that I can use to set quest vars? I tried "set c00.RadiantQuestsUntilC01 to 2", and it spat back that it didn't recognize the command.

If you click the "Properties" button with the script highlighted, you'll see a list--scroll down until you reach the three in question, click them, and their values will be in an editable field to the right.

Note that changing those may only impact a new game--this is what the existing mod on the Nexus does, and I see you've commented there.

To have something work reliably that can be installed mid-game, you'd need to create a new quest, run once and start game enabled, and do a small bit of Papyrus scripting--attach a new script to that quest, and oninit script a change to those properties.

I actually have a script that adds skill/level/more radiant quest requirements to the Companions in this manner...it's part of a larger WIP guild overhaul, but if there's demand I could release it as an pre-alpha in a day or three.

Or, to console a change:

http://www.creationkit.com/SetPapyrusQuestVariable C00 RadiantQuestsUntilC01 10

and similarly for the other two.

Ahhh, SetPQV.

EDIT: That did not work, it spat out the error "Syntax error. Reference not allowed in this context. Missing parameter Quest".

Gonna try to dig up the FormID for C00...

Aaaand that worked. Odd... ShowQuestVars in the console works with quest EditorIDs and FormIDs, but SetPQV in the console only works with quest FormIDs.

It seems that an error in the Proving Honor quest involving the Silver Hand cornering scene not playing right has manifested. Instead of the scene playing, Farkas immediately aggros on them, and apparently they're set to Ghost mode because none of his hits connect. So I'm stuck in there and the scene doesn't play.

I am not sure exactly of the cause, I just frantically did multiple things I thought might fix it. Interesting NPCs was deactivated (as it had a history of dirty edits before), several recently DL'd Sounds of Skyrim modules were deactivated, the Bashed Patch SkyProc module was deactivated, and I restarted from before even joining the Companions. What's pertinent here is that I saw a few bits in the script that looked like it picked up who you went to for the first radiant quest, and that may have been the cause. In effect, it may not be wise to make the RadiantQuestsUntilC01 var go over 1.

Like I said, I'm not certain, but it's possible. I just wanted to fix the questline-crippling bug ASAP, so I didn't meticulously and empirically determine the cause.

UESP says that's a common bug with Proving Honor, so it's likely unrelated, although of course more testing would be indicated.