GrantSP

I have just spent a half-hour making a VERY cursory look through the options available to give mod authors payment and come to this painful conclusion: There is no current system available that allows users to make minuscule, though appreciated, payments without the 3rd party(ies) that handles those payments coming out the better for it. ie. every micro-transaction incurs some fees or payments, either to the 3rd party (PayPal or Patreon) or to the financial institutions (MasterCard, Visa, your local bank). End result we will substitute Valve/Bethesda for the financial option of your choice. The big difference of course is the split is greatly reduced. Anywhere from 0.5% to 5% on every transaction to set fees all the way up to $30. This is where I imagine Robin Scott/DarkOne has looked and rightly shied away. The logistics of managing an all-embracing fund system for all the games that eventually will be using a scheme like this, and keeping track of the users that donate and the authors that are recipients, will need a full-time staff at least of 5 or 6 people. It doesn't even consider the legalities of setting up and running said funding system. What is needed is some way to make pledges, that don't involve the actual transfer of funds, that accrue and when they reach a critical limit where the fees are negligible, payment is called in. How? Beats me. This all boils down to a school of little fish trying to help each other when the big fish are holding all the options. I think I will leave this alone now, my Utopian dreams of fair pay for work are never going to cut it.

Perhaps Nexus should just allow for other types of money exchange systems to be implemented on the mod pages? PayPal or Patreon or anything else that is solely under the purview of the author and can be dis/enabled at their will, not Nexus. Clearly the biggest uproar, from sane mod users, wasn't the payment to authors but rather the measly amount they were getting. Remove the slice to Valve/Bethesda and the constraints on reaching a minimum $100 before receipt and then the author is solely responsible for the payment. If the 'big boys' want to come back in later and "ask nicely" for a cut then that can be figured out, maybe some sort of licencing scheme where you, the author, pay back to Valve/Bethesda, a slice of the revenue AFTER a certain figure is met. That way the benefits are given to those with priority: author then commercial entity. Something along those lines doesn't have to be initiated or even maintained by either Steam, Nexus or any other site. Each mod could simply have the same link to the same account accessed from anywhere. A Steam user clicks the button and sends funds in exactly the same way a Nexus user does. As far as the author is concerned it is the product that is being funded, not the distribution system.

Sort of shows the level of intelligence of a modder like that if they want to say: "I suport(sic) paid-for mods on Steam". Perhaps they had some time before attending 2nd Grade English class today. EDIT: That sounds a little too snarky. Sorry about that.

The logs are found in the folder under the MO root folder called: 'logs' Also I wouldn't call this a solution in the same way I wouldn't call removing your leg 'solves' your aching feet. As much as I would like to offer further help, you haven't actually provided anything in the way of diagnostic information. If you wish to provide the information I asked for, feel free to do so.

No need to apologise, just a friendly reminder.

Perhaps all of us here in STEP should be actively thinking of ways to promote support for modders? It's all well and good for us to feel vindicated in our stance, but we don't really amount to a 'hill of beans'. What about promoting donations to the author/mod on the guides? I think the collective knowledge of all of us is pretty sizeable, certainly it seems to be compared to the childish antics on other fora, is it possible we can formulate a structure that can be presented to Nexus, one that actively encourages support of the right people? The current Nexus donation scheme I think is flawed because it is too easy to ignore, the recent change to the download message is a good start, can that be improved upon? @Sheson makes a good point about the mod managers having a chance to promote donations. Not sure how that could be implemented but even a popup reminder or an icon similar to MO's 'Endorse' would be good. Two things are going to happen now as I see it. The 'community' will rally and devise an equitable way to compensate mod authors or... they will fall back and feel like the victory has happened. Victory has not been gained, the first battle was won, but business interests are much more pressing than sentimental opinions of 'right and wrong'. Could someone correct me if I'm wrong on this? The way Nexus has donations structured is to the author, not the mod? ie. the mod author has many mods listed but the donations are tied to their account/user name, not the mod page, or even a specific mod on that page? If that is the case, it probably needs to be more refined. Do the authors even know which mod is prompting donations from users? That would be a motivating factor in maintaining support for that mod or improving the less-than-supported mods.

Can you post the MO logs from the last run? Also the versions of TesLODGen and MO, what are they? If you have a version of xEdit (tes4edit) installed, can you run that from MO without error?

The Imgur gallery image you posted here and the one posted by a user (totalwar13) in the MO nexus forum is exactly the same: same detail, same URL, same everything! I logically concluded that he and you are one and the same. That user's question was answered correctly by @AaronofMpls, a long-time Nexus member and knowledgeable MO user, so I didn't feel the need to repeat his answer, there or here. If you post the same questions in multiple locations you should expect to see the support offered is probably given by the same individuals and even if you don't, you should check all the locations you ask for those answers.

Unless these mods are actually the first wave of content made by anti-Steam extremists designed to undermine the entire Workshop before it takes root! :O_o: Returning to the safety of my tinfoil lined bunker now.

I believe @AaronofMpls in the Nexus answered your query about the localization files.

On reflection, the question in the OP should probably be answered with a resounding NO! Moving them means there would be no plugins in the Data folder and I'm pretty sure the game engine would have a heart-attack if it was started with that empty, even if MO provides them in a modded VFS.

11:15 AM Monday 27th April 2015 Australian Eastern Standard Time I just now have checked all my MO installs and there is no issue with this. Any error anyone sees will be specific to the server assigned to you currently by Nexus and has nothing to do with MO.

Welcome to STEP by the way! Easiest way to update your 'very old' install is to do this: Grab the 1.2.18 full archive installation file from the MO downloads page In your current MO install folder delete everything except your 'mods', 'downloads' and 'profiles' folders and the ModOrganizer.ini Open the MO archive and copy into the now empty MO install folder everythingThis will ensure all of your current installation is completely removed, thus avoiding any potential mismatch of support files AND maintaining your mods in the same condition as they currently are. Keeping the ModOrganizer.ini is done to maintain the settings you have put in place and if you are still experiencing issues you can delete that and generate a fresh one after installation. Every install of MO maintains your settings in either these folders or that file and anytime you wish to purge your system of it but keep your stuff, just make backups of those.

If you are following the STEP method of cleaning plugins, or you have watched the GamerPoets videos on doing this, what should happen is the file in question: Update.esm, will be cleaned and that original file will be renamed as the backup and the new clean version will REPLACE the existing file. Is that what you are seeing? If so there is no problem. If, on the other hand, you see the backup file AND a cleaned file in your overwrite folder then that is something that needs to be checked.

Hmm... could you provide versions of both your MO and Windows system? That message shouldn't appear, as all the helper.exe file does is change the date of the *.bsa files to 1/1/2000. From the way you describe the message it is coming from Windows and not MO so there must be a conflict with the installed system files on your computer and those expected by the helper.exe. This isn't your fault, just one of those things that happens.

There is actually one good reason to move them into a MO managed mod. If you followed GamerPoet's videos on cleaning the *.esms you will notice he makes new clean versions and places them into a mod and that leaves the original 'dirty' plugins in the Data folder. Why is that a good thing? Anytime you use Steam to verify your installation the original files are checked and nothing is replaced, keeping you clean plugins safe in their own folders. However, the steps to clean them are easy and you shouldn't have too many reasons to verify your install so just keeping them in the Data folder is just as good. 'Six of one, half a dozen of the other'.

UIO is supposed to handle those font changes but for me at least it never has. I still add an 'INI Tweak' to the DarnUI mod in MO and assign the font changes there. Unless I do so I never have the correct menu display, it either shows the vanilla or at worse, nothing.

Can these acronyms be made case-sensitive? Just noticed a post over in the VIP Chat where AFK Mods was referenced but of course the AFK shows as "away from keyboard". In the context of the comment about a supposed debate over a 'STEP hit squad' I found that mildly amusing. If 'afk' could mean that and perhaps AFK could point to that other site? Then again, there probably isn't that many times where this sort of thing occurs. Just a thought.

I'm fairly certain those messages have something to do with the Qt libraries used by MO finding a mismatched DLL used by some OpenSSL software installed on your system. @Tannin added some info to the MO description page's FAQ (3rd last item) based on an issue we looked at here. Althought the specifics of how the error was generated are different, based on a search through the Qt forum, it is somewhat linked. My advice would be to examine your system for any software that uses the OpenSSL software and see if you can get that updated. EDIT: Link changed to point to the current issues page on GitHub.

That 'unresolved error' issue is nothing to do with MO, it is something happening on the Nexus and I would advise just waiting a day or so. As for the error messages about missing *.dll files. Those a re 1.3.x specific files and since you state you have gone back to 1.2.18 you haven't done a clean install of your MO installation. In your MO root folder, in your case "E:/SteamLibrary2/steamapps/common/Skyrim/Mod Organizer", delete everything except your ModOrganizer.ini and the 'mods', 'downloads' and 'profiles' folders. Then copy back in to the MO root folder everything from the MO 1.2.18 archive. This will restore your MO installation with all your mods and downloads but removes all 1.3.x version files. Any mods you downloaded manually that aren't in that 'downloads' folder caan safely be moved in and later you can 'Query Info' them from the MO UI so this way ALL your mods are managed in the same way.

I think you may have found a very specific and curious bug. I too can replicate what you are seeing and it makes no sense as far as I can see. Best option is to make a report in the Bug Genie and let @Tannin sort it out.

Must be specific to certain servers also because my MO called queries to Nexus all fail but any activity in Nexus, like manual downloads, still work fine. Give it a day or so and check again. It may also be related to work on the server side of things with regard to Nexus' addition of a 'Donate' button on the downloads, perhaps some extra code switching isn't being parsed correctly yet.

Which version of LOOT also? Keep in mind it isn't recommended to run both the internal SORT and the external LOOT together, especially if the versions are different. 1.2.x series of MO uses the LOOT 0.5 version and it will mess up your masterlist.yaml used by LOOT if you also run LOOT as an external program called from MO's executables list. This issue lessens if you use the MO 1.3.x series and the LOOT 0.7 version but it is still good practice to use either the internal SORT or the external LOOT.

Firstly I'd look at installing it in a more user-friendly location than the one you currently are using, but that's not at issue, just a personal preference. Regardless of where you have it there should be a 'logs' folder under the MO root folder. Are there any logs generated and what do they say?

I'm not implying anything as to your motives, just wondering how a Google search will reveal this. I wanted it to be clear to anyone that finds it the position STEP holds.