Guide Talk:Mod Organizer
This page has become OUT OF Date. In the section "Maintaining a Clean Overwrite" it says "Every time you run the game or a tool through Mod Organizer, check Overwrite. If there are files present, right-click Overwrite and select Create Mod." however the right click menu no longers contains a "Create Mod" entry. The closest menu item is called "Create Backup". Would someone knowledgeable please update this page? -Paul 13Dec2021.
I suggest a brief background and summary of key features of MO on the front page ~z929669
Talk 04:53, 25 June 2012 (UTC)
Under "Third Party Programs" on the Wrye Bash line, the wiki says that the standalone version of Wrye Bash is the recommended choice. Now that Mod Organizer has Python plugins that uses the same Python 2.7 series that Wrye Bash requires, should we change this recommendation? Also when using the Wrye Bash for other games (e.g. Fallout 3) there is no standalone variant, so the Python setup is required. It might be better to recommend the Python setup, or a combination of both. DoubleYou (talk) 08:40, September 27, 2013 (MDT)
- You could just not recommend either version and just say that for Fallout python is required. Treat them as equal options. Essarrbee (talk) 10:46, September 27, 2013 (MDT)
Seeing as we have now moved my sandboxed guide to the main Mod Organizer guide, I recommend we abandon the sandbox and edit the guide directly instead.--DoubleYou (talk) 23:43, October 28, 2013 (EDT)
That's what you should normally do anyway, but you didn't kmow so sandboxed it, which may have been better to start with anyway, No problem with that. wolverine2710 thinks people may be more confident using sandbox to learn on, maybe but mistakes can be edited, by anybody. We don't bite (much) so I'm going to encourage both use and editing of main in post as wolverine2710 asked me to as he thinks I have a persuasion skill, I do it's a big spiked club. --Uhuru N'uru (talk) 11:29, November 7, 2013 (EST)
Note that the wiki css controlling typography and text color has been tweaked recently. It is now best practice to use {{fc|#ddd|}} rather than {{fc|white|}}, because white is just too bright against the new, slightly darker body font without blaring too far past the brightened heading fonts. ~z929669 
Talk 00:54, December 17, 2014 (EST).
