When deciding between adding more features and keeping an up-to-date list of features, I chose the former. The wiki and online help list many of the features. The best way to find everything that's in BUG is to go through the BUG Options Screen in the game (CTRL + ALT + O).
ACO is in BULL which I am releasing 1.0 for this weekend. It's a DLL-based mod and so cannot be included in BUG. BUG and BULL are designed to work together or separately as you like.
I kept better track of the changes I made to BULL. Here's where it gets annoying. I think of an idea and add it to the code. This can sometimes take 5-15 minutes. I test it out in another 5 minutes. Now, I can spend a half hour writing up the description, how to configure it, and adding a screenshot, and putting this in the Wiki and in the help file . . . or I can go on to the next feature.
I'm looking forward to the BULL release as I'll be hoping to merge it with PIG in short time.
A request:
EF, would it be possible to make sure ACO v2.0 is the one that makes it into the release of BULL? I don't intend to make any changes to that mod for a while now (if at all).
EF, would it be possible to make sure ACO v2.0 is the one that makes it into the release of BULL? I don't intend to make any changes to that mod for a while now (if at all).
Now, I can spend a half hour writing up the description, how to configure it, and adding a screenshot, and putting this in the Wiki and in the help file . . . or I can go on to the next feature.
... why do all that? A simple line like: Advanced Combat Odds by: PieceOfMind - <link tio thread> for each imported feature would do. And your own custom features have no need for documenting, just the external ones so that we know what you have already aded and what to try and merge our self.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.