IMPORTANT: Major SVN Update
- Thread starter EmperorFool
- Start date
EmperorFool
Deity
@Caesium - I can point you in the right direction quickly now before I head out, and answer questions when I get home.
1. Create a file in CustomAssets/Config called "Caesium.xml". Use Reminder.xml as a base.
2. Change occurances of "Reminder" to "Caesium".
3. Added <load mod="Caesium"/> to "init.xml" after the last <load> tag.
4. In "Caesium.xml", delete the <options> tags and modify the first <events> tag to look like this:
Code:
<events module="CvModChooserEventManager">
<arg type="string" value="Config.ini"/>
</events>Use this pattern for all the event managers in CvCustomEventManager that require the Config.ini parameter. For those that don't, make them look like this:
Code:
<events module="CvModChooserEventManager"/>5. Delete CvCustomEventManager.py
6. Make sure you use BUG's CvEventInterface.py.
That should do it. Let me know if you get stuck anywhere and I'll help ya out when I get home.
EmperorFool
Deity
You will as you're not alone. Ask any questions you have along the way.
Update to the latest from SVN.
ripple01
Emperor
Does BUG still read the CvEventManager file at all? I had some code in there that enabled movies for National Wonders... do I need to move it to its own seperate event manager or can I leave it in CvEventManager?
Cheers,
ripple01
Cheers,
ripple01
EmperorFool
Deity
Yes, BUG uses the stock CvEventManager and its events.
While I recommend adding event handlers to their own files, Firaxis is unlikely to have another patch, let alone modify this file, so it's pretty moot. BUG has no problem with you modifying that file.
CvCustomEventManager is another story. This module has been replaced with BugEventManager and should not be used with BUG. Also, make sure CvEventInterface uses BugEventManager if you've modified that module.
EmperorFool
Deity
Looking forward to that HOWTO!I want to integrate the BUG into Merged Mod... I've tried with the published 3.0, but it was simply too overwhelming, so I gave up.
I would love some feedback on which parts were tough. I know it will be different for everyone, but it helps to hear first-hand.
The major change is that a lot of the merging can be done in XML instead of Python. The other change is minimizing the number of shared files between mods. My goal is to make it so you don't change any BUG code to merge in your own mods assuming it's possible.
By that I mean that if you have a mod that changes the Main Interface, there's no way around touching BUG code. But if all your changes are in a custom event manager, you won't have to change BUG code. This will greatly ease upgrading BUG in your merged mod.
I don't recall exactly was what hard. But I do recall noticing that there were so many python files in both BUG and MM that needed merging, and on the first attempts I immediately ran into disappearing interface errors (which equals indentation errors, I know).
By the way, is it strictly necessary to install that turtoise thing to get the latest version from sourceforge?
By the way, is it strictly necessary to install that turtoise thing to get the latest version from sourceforge?
EmperorFool
Deity
Well, that's not always the case. No interface simply means that it's not working. The how could include indentation errors, general syntax errors (e.g. "x = 5 * / 3", something has to go between * and /), and bugs, like division by zero.
No, you just need a Subversion client of some kind to access the Subversion repository, in the same way you can use Firefox or Opera or Lynx to access the web rather than IE.
