Jump to content

Weird Wrye Bash behaviour


BlueGunk

Recommended Posts

I honestly do not see what is unconventionable about building your own mod! I gave you an example when Wrye, dysfunctions and that is not misleading, it is fact, whether you want to believe it or not, well that is up to you as an individual! I can only say to you that Wrye is like any other software, it has it's limits, and for you to suggest it is infallible, well that is defying the trade description act. hey sometimes your not always right!
Link to comment
Share on other sites

  On 11/2/2012 at 9:46 PM, Zapata935 said:

I honestly do not see what is unconventionable about building your own mod! I gave you an example when Wrye, dysfunctions and that is not misleading, it is fact, whether you want to believe it or not, well that is up to you as an individual! I can only say to you that Wrye is like any other software, it has it's limits, and for you to suggest it is infallible, well that is defying the trade description act. hey sometimes your not always right!

 

This is what is unconventional:

If you want certain stuff created from favourite modder a, then fav  modder b, etc etc, to incorporate in your own mod. (Not for  re-publication or
re-uploading to Nexus, may I add! Strictly Taboo!).  You have to make the mod your copying stuff from and bashing a temporary  master to your
own mod, save, delete that mod from the list then  re-save.

 

What I was referring to as being misleading is your claim:

Hi BlueGunk,  don't be alarmed, this is quite common in wrye bash, your patch has lost contact with it's header file.

 

To be honest, I still don't know what you mean by that last part, since you never explained it.

 

I also never claimed that Wrye Bash is infallible, and where on earth does the Trade Descriptions Act come into this?! :psyduck:

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...