maybe it's WinXP, maybe it's the Steam version
Definitely not XP. I am using Win 7 64bit

By the way the command "multiple" in my path was in the path that CivIV was using to launch RIFE. (I used Sysinternals Process Explorer to find it)
maybe it's WinXP, maybe it's the Steam version
Does the launcher support /altroot?
My aliases are normally like:
"C:\Program Files\Firaxis Games\Sid Meier's Civilization 4\Beyond the Sword\Civ4BeyondSword.exe" mod="Mods\Rise from Erebus" /altroot="Z:\Documents\My Games\Rise from Erebus"
That way all save files, options, etc are saved to a separate directory than plain Civ, or other mods. (I like to have separate save directories for each mod).
System.IO.IOException: You don't have access to "C:\Program Files (x86)\2K Games\Firaxis Games\Sid Meier's Civilization 4 Complete\Beyond the Sword\Mods\Rise from Erebus1.30\Assets\Modules\NormalModules\FallUnder".
I enabled access for me but it's still not possible to disable the modules (Bannor - Chain of command, Fall Under, Mekara Order).
One odd thing I did see, even though it appears to be working for me correctly, looking in the .config file in the rife directory, it appears it still has not written the correct mod path to that file, not sure why. It still shows this in that file.
Code:<userSettings> <RifELauncher.Properties.Settings> <setting name="PathToCiv" serializeAs="String"> <value>NOTSET</value> </setting> </RifELauncher.Properties.Settings> </userSettings> </configuration>
An interesting and stupid consequence of this is that if you release a new version, because it is keyed by build number, the user's saved settings may not transfer over to the new version. There's a way around this, using Settings.Properties.Default.Upgrade().
well, i don't know ... i'm not _that_ skilled in windows, that i could say how to deactivate protection of one folder in any version of win ... /: ...Tschuggi said:
... some basic conflict check implemented ...
thoughts?
That is excellent.
Although, I would like to know, is this too much information for a typical user. Would someone who does not know what a UNIT_CORGAYLE is understand this message? If it's not too much trouble, I think a standard warning might be better, with either the option to see a more detailed message after that or an option in the launcher to show more detailed warning messages.
And I'm curious, how many lines of code?![]()
[name]
Rogue Module wheeeeeee ( this is name )
[version]
0.1
[rifeversion]
1.3
[author]
anw
[dependency]
Mekara; 9.9
SomeVersionlessMod
Have you thought about adding the capacity for the launcher to install modules?
All you really need to do is unpack a zip file. If you add a [files] section to the info.txt file you could even support upgrading, just by deleting any file not listed.
Bonus point if you add logic that allows both packing the files both with and without a directory.
Downloading modules directly would be good but we'd need either a good referencing of links or our own "rife modules database".
I'm not sure GreyFox domain can hold such a database.
i was thinking the first, but now i think that it could be quite risk virus/*ware-wise, so i guess that installing / downloading won't be implemented. period.