SKY6A
Veteran

Motomataru,
First, thanks for this great mod. In my opinion, MB/WB is not worth playing without it--seriously!
That said, I'd like to be able to add it manually to to other mods myself, and so went back to version 3, which you posted back on 24 June 2010. Installing that version was a snap (even though I am new to MB/WB modding) since each of the code snippets was discrete. After following your directions, that version compiled without errors on the first try!
But of course I would also like to take advantage of the features that you have implemented since then, and so have been trying to install the latest version manually as well. In your readme, however, you mention .dds files that need to be put in the appropriate install folder of the module. But there are no .dds files in the package, just the .py files and the one .brf. Is there something missing? It doesn't seem like it, since that package compiled and ran fine using ModMerger. I assume, then, that ModMerger must be doing something that I don't understand.
Of course, you're probably wondering why I don't just use the ModMerger version to play, right? Well, I could...but ultimately I like to be able to do things myself. I have enjoyed writing simple scripts for other games, and am trying to learn to do the same for MB/WB. Installing mods manually is one way to learn how they are structured and what the various module system files do. Also, since I do not really understand what ModMerger is doing, I'm not sure how to merge its output with other non-ModMerger mods (if that makes any sense) and this limits what I can do with it.
So if you can simply explain the reference to .dds files in the readme and how it affects a manual installation, I'd be very grateful.
Cheers, and thanks again for a great mod!
EDIT: Nevermind, after a little bit of tinkering, I got it to compile without errors and running great. Is perhaps the reference to .dds files in the readme just a carry-over from some previous version?
In any case, thanks again!
First, thanks for this great mod. In my opinion, MB/WB is not worth playing without it--seriously!
That said, I'd like to be able to add it manually to to other mods myself, and so went back to version 3, which you posted back on 24 June 2010. Installing that version was a snap (even though I am new to MB/WB modding) since each of the code snippets was discrete. After following your directions, that version compiled without errors on the first try!
But of course I would also like to take advantage of the features that you have implemented since then, and so have been trying to install the latest version manually as well. In your readme, however, you mention .dds files that need to be put in the appropriate install folder of the module. But there are no .dds files in the package, just the .py files and the one .brf. Is there something missing? It doesn't seem like it, since that package compiled and ran fine using ModMerger. I assume, then, that ModMerger must be doing something that I don't understand.
Of course, you're probably wondering why I don't just use the ModMerger version to play, right? Well, I could...but ultimately I like to be able to do things myself. I have enjoyed writing simple scripts for other games, and am trying to learn to do the same for MB/WB. Installing mods manually is one way to learn how they are structured and what the various module system files do. Also, since I do not really understand what ModMerger is doing, I'm not sure how to merge its output with other non-ModMerger mods (if that makes any sense) and this limits what I can do with it.
So if you can simply explain the reference to .dds files in the readme and how it affects a manual installation, I'd be very grateful.
Cheers, and thanks again for a great mod!
EDIT: Nevermind, after a little bit of tinkering, I got it to compile without errors and running great. Is perhaps the reference to .dds files in the readme just a carry-over from some previous version?
In any case, thanks again!




