TechAngel85

That one worked without any quotes. Is the other error anything to worry about?

That argument also didn't work. I'm still getting the same error message popping up.

Well add it man! I'm also getting an error from Flashlight NVSE in the MCM. Error says... Title: Flashlight Version Error Message: There seems to be a problem with the HUD files. If you are using iHUD, make sure you re-install FlashlightNVSE after activating iHUD.

I know nothing about this program so I'm forced to post a support thread. When I run the 4GB loader, I receive an error message: "Failed to write to memory of child process", Access is denied. Clues? Hints? I have been going very slow and have followed instructions to a tee (i believe) so far.

I fixed the sidebox for you after Unified HUD Project so the text off to the left of it cleared the box and started afterwards. Also, are you aware within that sidebox you instruct users to go ahead and start up the game to test the menu; however, there is a missing master for Afterschool Special.esm at this point in the install (Sortomatic.esm).

Tales of the Burning Sands no longer requires the update file as you instruct (according to the nexus page).

That would make more sense when things are changed. Like we do with the STEP changelog, clicking on a mod takes you to the mod page on the wiki. From there users can do what is necessary. Linking to the mod on your guide would be the equivalent of that.

Thanks. Got it

MO 1.2.6 didn't auto check the Fallout - Invalidation.bsa. I don't recall this file. Is it created by MO for archive validation? Should it be checked?

I picked it up for that cheap but have never played it.

I'm considering picking up Alan Wake. Opinions?

Dropped from testing.

STEP 2.2.9 will be released shortly after MO 1.2.7 releases. We are awaiting some changes which are coming in that version. Also, 2.2.9 will likely recommend SKSE 1.7 Alpha with the memory fixes. I think just about the entire staff has been using it without any issues at all (I know I have been for testing.)

If it's only happening with mods installed that aren't in STEP, then this is a simple "no" for STEP and let Pack authors include it in their Packs that use these other mods.

I agree. I've never had or seen this issue until this mod was posted here.

That's not bad. I just know when I look at the sun I most definitely do not see rainbows. Maybe if I was on something... Haha!

Procedure: https://forum.step-project.com/topic/1912-update-procedure/ (probably needs some updating with the new forum and all) Only if we're done with them completely and they've been decided to not be put in STEP. I think we've left mods in testing for just about every release I've been a part of.

I say leave this one up for after 2.2.9 as well. Just leave it in testing and we'll revisit it after we've pushed out the next release.

That's what I meant as well. If we're just going to come back to it there is no need to remove the testing tag. It'll just at as a reminder that we're not finish with it yet. It's not going to hurt anything to keep the testing tags on mods through a release and into a new one. We do it all the time.

I see this one as the same as Rustic Windows was. It's too split to call so just drop it and let users decide on their own. We might revisit it in the future but for now I'd rather just move on to other things.

No need to drop it if we're going to come back to it. Just leave it in testing for us to return to after 2.2.9.

I thought I dropped this a while back...oh well. I don't really care for the persist rainbow in all the shots with the one DY posted.

I currently run everything from a WD Black so I'm on a HDD. As for STEP, the BSA non-extraction is a non-issue at the moment which is why we're not worried about recommending user to not extract their BSAs for this point on. There are no mods in STEP which we have specific conflict resolution instructions for (aka hiding files) that are in BSAs. All mods that we have these instructions for are available as loose files for downloading. That check was done about a month ago so STEP is good to go.

The same thing happened to me. I've fixed some old mods that are dead and the authors are MIA. I asked if I could upload them giving full credit to the authors of the mods. DarkOne basically told me that it sucks but was against policy unless I had permission. So Nexus rules allows old mods to sit and rot when the authors abandon them rather than allowing someone to take up the mantel until the author returns. Sad thing is, there are probably hundreds of mods on Nexus that do this very thing, but since I asked the staff, I was told no. As for the White Phial being Core, I'm still going to have to say no due to the very large style change; however, if the other staff agree that we make an exception then that is fine.

Can ofc (of course) be added in! This has been confusing the heck out of me because when I read it, I read something different due to me real life job.